Skip to main content

Compliance Page

What is the Compliance Page?​

The Compliance page is where you can see in detail how well your website complies with EAA (European Accessibility Act) and WCAG 2.1 accessibility standards. It shows you scores, detailed statistics, and suggestions to improve your site's accessibility.

What you'll find on the Compliance Page​

The page is organized into several sections that help you understand your site's compliance status:

  1. Overall Score - The general compliance score of your site
  2. WCAG Levels - Detailed analysis for levels A and AA
  3. Issues Distribution - How issues are distributed by severity
  4. EAA Compliance - EAA requirements and compliance status
  5. Priority Actions - What to do to improve
  6. Scan Controls - Complete list of checks performed

Overall Score​

At the top of the page you see a large circle with the overall compliance score of your site.

How to read the score​

The score is a percentage from 0 to 100%:

  • 90-100%: Excellent - Your site is very accessible
  • 80-89%: Good - The site is accessible, with small room for improvement
  • 60-79%: Sufficient - The site has several issues to fix
  • Below 60%: Critical - Many issues to fix urgently

The circle color changes based on the score:

  • Green: Excellent or Good
  • Blue: Sufficient
  • Yellow: Sufficient (low)
  • Red: Critical

Below the score you also see:

  • The compliance level (Excellent, Good, Sufficient, Critical)
  • How many issues were found in total
  • How many pages the calculation is based on

WCAG Levels​

WCAG (Web Content Accessibility Guidelines) has two main levels that are analyzed:

Level A​

Level A is the basic level of accessibility. It includes the fundamental requirements that all sites must meet.

What you see:

  • Score: The percentage of Level A compliance
  • Total issues: How many Level A issues were found
  • Critical issues: How many critical Level A issues there are
  • Compliance level: Excellent, Good, Sufficient, or Critical

Level AA​

Level AA is the standard level required by EAA law. It includes more advanced requirements to ensure better accessibility.

What you see:

  • Score: The percentage of Level AA compliance
  • Total issues: How many Level AA issues were found
  • Critical issues: How many critical Level AA issues there are
  • Compliance level: Excellent, Good, Sufficient, or Critical

Important: To be compliant with EAA law, your site must meet at least Level AA.

Issues Distribution by Severity​

This section shows you how the issues found on your site are distributed, divided by severity.

Critical Issues (Red)​

Critical issues are those that prevent or make it very difficult to access content for users with disabilities.

Examples:

  • Images without alternative text
  • Links without text
  • Forms without labels
  • Content that flashes too quickly

What to do: Fix these issues as soon as possible, they are the most important.

Warning Issues (Yellow)​

Warning issues are those that make using the site more difficult but don't completely block it.

Examples:

  • Alternative texts that are too long
  • Links with generic text ("click here")
  • Links opening in new windows without warning
  • Required fields not clearly marked

What to do: Fix these issues when possible to improve user experience.

Info Issues (Blue)​

Info issues are suggestions and best practices that can improve accessibility.

Examples:

  • Decorative images that could be marked as decorative
  • Suggestions to improve page structure
  • Tips to optimize navigation

What to do: These are useful suggestions but not urgent. You can fix them when you have time.

EAA Compliance​

EAA (European Accessibility Act) is the European law that requires all websites to be accessible starting in 2025.

EAA Requirements​

EAA is based on four fundamental principles:

  1. Perceivability: Information must be presented so users can perceive it
  2. Operability: Interface components must be usable by everyone
  3. Understandability: Information and interface use must be understandable
  4. Robustness: Content must be robust enough to work with various assistive technologies

Compliance Status​

In this section you see:

  • Compliant Pages: How many pages meet EAA requirements (without critical issues)
  • Compliance Percentage: The percentage of compliant pages out of the total
  • Pages to Fix: How many pages still have critical issues to resolve

Goal: Have 100% of pages compliant, meaning all pages without critical issues.

Priority Actions​

This section tells you what to do to improve your site's compliance.

High Priority Actions​

These are the most important actions to take immediately:

Fix Critical Issues

  • If there are critical issues, this action reminds you to fix them
  • Shows how many critical issues you still need to fix

Improve Score

  • If your score is below 80%, this action suggests working to improve it
  • A higher score means a more accessible site

Next Steps​

These are actions you can take after fixing priority issues:

Continuous Monitoring

  • Run regular scans to monitor progress
  • Verify that new content is accessible

Team Training

  • Ensure the team knows accessibility best practices
  • Train new team members on WCAG guidelines

Scan Controls​

This section shows all the checks that Axessibly performs during your site scan. It's divided into three main parts:

Native EAA Engine​

This is the scanning engine developed specifically for EAA requirements. It checks:

Image Controls:

  • Images without alternative text (critical)
  • Alternative texts that are too long (warning)
  • Decorative images not marked (info)

Link Controls:

  • Links without text (critical)
  • Links with generic text like "click here" (warning)
  • Links opening in new windows without warning (warning)

Form Controls:

  • Fields without labels (critical)
  • Required fields not marked (warning)

Heading Controls:

  • Empty headings (critical)
  • Heading level skips (warning)
  • More than one H1 per page (warning)

ARIA Controls:

  • Interactive elements without name (critical)
  • Missing ARIA landmarks (warning)

Keyboard Controls:

  • Negative tabindex (warning)
  • Positive tabindex (warning)

Axe-core Engine​

This is a standard industry scanning engine that verifies:

WCAG Controls:

  • Color contrast (critical)
  • Keyboard navigation (critical)
  • Visible focus (warning)

Structural Controls:

  • Page language (warning)
  • Document title (warning)
  • Main landmarks (warning)

Advanced EAA Controls​

These are additional controls for specific EAA requirements:

Table Controls:

  • Missing captions (warning)
  • Missing headers (critical)
  • Missing scope (warning)

Media Controls:

  • Videos without controls (critical)
  • Videos with autoplay (warning)
  • Audio without controls (critical)

Page Structure Controls:

  • Missing language attribute (critical)
  • Invalid language code (warning)
  • Missing title (critical)
  • Missing meta description (info)

And many other controls to ensure maximum compliance.

Scoring System​

Axessibly calculates compliance scores automatically. Here's how it works:

Issue Severity​

Issues are classified into three levels:

  • Critical (Red): Issues that violate WCAG Level A requirements
  • Warning (Yellow): Issues that violate WCAG Level AA requirements
  • Info (Blue): Best practices and suggestions

Score Calculation​

Level A: Based on critical issues that violate Level A requirements Level AA: Based on warning issues that violate Level AA requirements Total: Combined calculation of all issues

The score is calculated considering:

  • How many checks were passed
  • How many checks found issues
  • The severity of issues found

EAA Compliance Levels​

  • Excellent: ≥90% - The site is very accessible
  • Good: ≥80% - The site is accessible
  • Sufficient: ≥60% - The site has room for improvement
  • Critical: <60% - The site has many issues to fix

What to do if you don't see data?​

If this is your first time accessing the Compliance page, you might see a message saying no data is available.

What to do:

  1. Go to the Dashboard and scan your site
  2. Or upload a sitemap and start a batch scan
  3. After scanning, return to the Compliance page to see the results

Tips for using the Compliance Page​

  1. Check regularly: After each site modification, run a new scan to see improvements
  2. Priority to critical issues: Always start by fixing critical issues, they are the most important
  3. Aim for 100%: The goal is to have all pages compliant without critical issues
  4. Use priority actions: Follow the suggestions in the "Priority Actions" section to know where to start
  5. Consult controls: The "Scan Controls" section explains what is checked, useful for understanding issues

Frequently Asked Questions​

What's the difference between Level A and Level AA?​

  • Level A: Basic accessibility requirements (minimum necessary)
  • Level AA: Standard requirements required by EAA law (recommended)

Do I need to fix all issues?​

Not necessarily. Always start with critical issues, then move to warnings, and finally to info suggestions when you have time.

How long does it take to become compliant?​

It depends on how many issues you have and the complexity of the site. Start by fixing critical issues, which are the most important.

Can the score improve?​

Yes! Every time you fix an issue and run a new scan, the score improves. Keep working on issues to reach 100%.

Conclusion​

The Compliance page is your main tool to understand how accessible your site is and what you need to do to improve it. Use it regularly to monitor progress and ensure your site meets EAA and WCAG 2.1 standards.