European Accessibility Act 2026 — The Complete Website Compliance Checklist
The European Accessibility Act (EAA) has been fully enforceable since June 28, 2025. If your website serves customers in any EU country, you are legally required to meet WCAG 2.1 Level AA accessibility standards. This practical, developer-focused compliance checklist covers everything you need to know — not a sales pitch, just actionable steps.
⚠️ Quick compliance check
Color contrast is the most common accessibility failure on the web (found on 83% of homepages). Start with our free Color Contrast Checker to verify your text meets WCAG AA standards — no signup required.
What Is the European Accessibility Act (EAA)?
The European Accessibility Act is EU Directive 2019/882, adopted into law in June 2019. Its fundamental purpose: extend legal accessibility requirements from the public sector (which was already covered by the 2016 Web Accessibility Directive) to private sector businesses serving EU customers.
After a six-year transition period, the EAA became fully enforceable on June 28, 2025. All 27 EU member states transposed it into national law during this period, meaning each country now has its own enforcement mechanism — though all reference the same technical standard.
2019
Directive Adopted
EU Directive 2019/882
Jun 2025
Enforceable
Business compliance deadline
27
EU Member States
All must comply
WCAG 2.1 AA
Required Standard
Via EN 301 549
The technical standard referenced by the EAA is EN 301 549 — a European standard for ICT accessibility. EN 301 549 incorporates WCAG 2.1 Level AA for web content, which means meeting WCAG 2.1 AA is the practical path to EAA compliance for websites and web apps.
A critical distinction from the US ADA: the EAA provides explicit technical standards, not court-interpreted requirements. This removes the ambiguity that characterizes US accessibility law — in the EU, the bar is clear.
| Aspect | Web Accessibility Directive | European Accessibility Act |
|---|---|---|
| Year | 2016 | 2019 (enforceable 2025) |
| Scope | Public sector only | Private sector + public |
| Who must comply | Government websites & apps | Businesses serving EU customers |
| Standard | EN 301 549 / WCAG 2.1 AA | EN 301 549 / WCAG 2.1 AA |
| Penalties | Varies by member state | Fines up to €100,000+ per country |
| Exemptions | None defined | Micro-enterprises (<10 employees, <€2M revenue) |
Does the European Accessibility Act Apply to Your Business?
❌ YES — You must comply if:
- •You sell products or services to customers in any EU country
- •You operate an e-commerce website accessible in the EU
- •You provide banking, telecom, transport, or media services in the EU
- •You are based outside the EU but serve EU customers (includes US, UK, Asian companies)
- •You publish e-books, digital documents, or streaming media in the EU
✅ POSSIBLY EXEMPT if:
- •Fewer than 10 employees AND annual turnover under €2 million (micro-enterprise)
- •Note: micro-enterprise exemption applies to services only, not physical products
- •"Disproportionate burden" claim — available case-by-case with documented evidence
⚠️ Even if exempt today, compliant websites perform better for all users. Accessibility is good UX.
Industries specifically and explicitly covered by the EAA:
The Complete Website Accessibility Checklist — WCAG 2.1 AA
WCAG organizes all requirements around four principles known as POUR: Perceivable, Operable, Understandable, Robust. Every WCAG success criterion maps to one of these principles. Here is the actionable checklist for each:
1. Perceivable — Users Must Be Able to See and Hear Content
| # | Requirement | What to Check |
|---|---|---|
| 1.1 | Images have meaningful alt text | Every <img> has an alt attribute. Decorative images use alt="" |
| 1.2 | Videos have synchronized captions | Pre-recorded video includes closed captions — auto-generated captions must be reviewed for accuracy |
| 1.3 | Audio content has text transcripts | Pre-recorded audio-only content (podcasts, voice recordings) has a full text transcript |
| 1.4 | Heading hierarchy is logical | H1 → H2 → H3 hierarchy with no skipped levels. Page has exactly one H1 |
| 1.5 | Color contrast meets minimum ratios | Normal text: 4.5:1 minimum. Large text (18pt+ / 14pt+ bold): 3:1 minimum |
| 1.6 | Text resizes to 200% without loss | Zoom to 200% in browser — no content is hidden, clipped, or overlapping |
| 1.7 | Color is not the only indicator | Errors use text + icon, not just color. Links distinguishable from body text without color |
| 1.8 | UI components meet contrast | Button borders, form inputs, icons: 3:1 contrast against adjacent background color |
🎨 Check requirement 1.5 instantly: Color Contrast Checker — paste your HEX colors and get immediate AA/AAA pass-fail results with auto-fix suggestions.
2. Operable — Users Must Be Able to Navigate and Interact
| # | Requirement | What to Check |
|---|---|---|
| 2.1 | All functionality works with keyboard only | Tab through entire page — every link, button, form, dropdown, and modal is reachable and operable |
| 2.2 | No keyboard traps exist | Focus never gets permanently stuck in modals, carousels, or embedded widgets — Esc always exits |
| 2.3 | Skip navigation link exists | "Skip to main content" link at the very top of the page — may be visually hidden but must be focusable |
| 2.4 | Focus indicator is visible | Tab through page and confirm every focused element has a visible, high-contrast outline |
| 2.5 | Page titles are descriptive and unique | Each page has a unique <title> tag that describes both the page and the site |
| 2.6 | Link text is descriptive | No "click here," "read more," or "learn more" links without context — text must describe the destination |
| 2.7 | No content flashes more than 3×/second | No strobing animations, rapid flickering, or auto-playing video with flash effects |
| 2.8 | Touch targets are adequate size | Buttons and links are at minimum 44×44 CSS pixels for touch interaction on mobile |
3. Understandable — Content Must Be Clear
| # | Requirement | What to Check |
|---|---|---|
| 3.1 | Page language is declared | <html lang="en"> (or correct language code) is set on every page |
| 3.2 | Form inputs have visible labels | Every input has a visible <label> with a for= attribute. Placeholder text alone does NOT satisfy this |
| 3.3 | Error messages identify the problem | Form errors explain what went wrong specifically ("Email is invalid" not just "Error") |
| 3.4 | Navigation is consistent across pages | Navigation menu, logo, and footer appear in the same position on every page |
| 3.5 | Form validation provides corrective suggestions | When input is rejected, suggest the correct format (e.g., "Use format DD/MM/YYYY") |
4. Robust — Content Must Work with Assistive Technology
| # | Requirement | What to Check |
|---|---|---|
| 4.1 | HTML is valid and well-formed | Run through W3C validator — no duplicate IDs, no unclosed tags, no improper nesting |
| 4.2 | ARIA roles used correctly | Custom components have appropriate ARIA labels and roles. No ARIA is better than wrong ARIA |
| 4.3 | Status messages are announced | Success/error messages use role="alert" or aria-live so screen readers announce them automatically |
Top 5 EAA Compliance Failures on European Websites
These five issues account for the majority of accessibility failures found in automated audits. Fix these first and you will address roughly 80% of the most critical issues.
Color Contrast (83% of websites fail this)
CriticalThe single most common WCAG violation globally. Typically: light gray text on white backgrounds, white text on light-colored buttons, low-contrast placeholder text. Even minor color choices can fail the 4.5:1 ratio requirement.
Fix:
Test every text/background pair with our Color Contrast Checker. Darken text colors or darken button backgrounds to reach 4.5:1.
Missing Alt Text on Images (58% of websites)
CriticalEvery informative image requires descriptive alt text. Decorative images need alt="". Product images on e-commerce sites must describe the product. Images of text must have the same text in the alt attribute.
Fix:
Audit all <img> tags. Write descriptive alt text (not "image" or "photo"). Add alt="" to decorative images. Use axe DevTools to find all missing alt attributes.
Missing Form Labels (54% of websites)
HighPlaceholder text is NOT a label. Screen readers cannot reliably announce form purpose from placeholder text alone. Every input needs a visible <label> element with a for attribute matching the input's id.
Fix:
Add <label for="inputId">Email address</label> before every input. If visual labels are not desired, use aria-label or visually-hidden CSS class.
Empty Links and Buttons (49% of websites)
HighIcon-only buttons (hamburger menus, social icons, close buttons, shopping cart icons) without text labels are invisible to screen readers. The screen reader user hears "button" with no indication of its function.
Fix:
Add aria-label="Open navigation menu" to icon buttons. Or add visually hidden text using CSS class sr-only (Tailwind) or visually-hidden. Never use an empty <a> tag.
Missing Page Language Declaration (28% of websites)
MediumThe <html> tag must have a lang attribute matching the page's primary language. Screen readers use this to select the correct pronunciation engine. A French screen reader reading an English page sounds completely garbled without this declaration.
Fix:
Add lang="en" to <html> (or the ISO 639-1 code for your language: lang="fr", lang="de", lang="es", etc.). Five minutes of work that fixes a critical issue.
EAA Penalties — What Happens If You Do Not Comply?
Each EU member state sets its own penalties — the Directive requires that they be "effective, proportionate, and dissuasive." Penalties vary significantly by country and severity of violation:
| Country | Enforcement Authority | Penalty Type |
|---|---|---|
| Germany | Market surveillance authorities | Fines + product market withdrawal |
| France | ARCOM (audiovisual), DINUM (digital) | Fines up to €50,000 + public naming |
| Netherlands | ACM (Authority for Consumers & Markets) | Administrative fines + withdrawal orders |
| Ireland | National Disability Authority | Complaints process + enforcement orders |
| Sweden | DIGG (Agency for Digital Government) | Fines + compliance orders |
Beyond fines, enforcement authorities can order market withdrawal — requiring you to cease selling products or services in the EU until compliance is achieved. For businesses reliant on EU revenue, this is far more disruptive than any fine.
Practical Enforcement Reality
Most enforcement authorities as of 2026 prioritize remediation over punishment. Companies making good-faith efforts to comply are typically given time to fix issues before fines are imposed. Companies that ignore accessibility entirely — especially in consumer-facing industries like e-commerce and banking — face the strictest enforcement. Document your compliance efforts even if you have not yet reached full WCAG 2.1 AA.
Free Tools to Test Your Website's Accessibility
You do not need expensive accessibility testing software to get started. These six free tools cover the full range of automated and manual testing:
| Tool | What It Tests | Cost |
|---|---|---|
| ToolForge Color Contrast Checker | WCAG AA/AAA color contrast ratios with auto-fix | Free, no signup |
| Google Lighthouse | Automated accessibility scan (50+ checks) | Free (Chrome DevTools) |
| axe DevTools | Comprehensive WCAG violation detection | Free browser extension |
| WAVE (WebAIM) | Visual accessibility evaluation overlay | Free (wave.webaim.org) |
| W3C HTML Validator | HTML validity, duplicate IDs, structure | Free (validator.w3.org) |
| NVDA Screen Reader | Manual screen reader testing (Windows) | Free (Windows only) |
Recommended Workflow
Run Lighthouse first for a quick automated scan. Fix all flagged issues, then manually test with keyboard navigation and a screen reader. Use our Color Contrast Checker specifically to verify every color pair on your site — Lighthouse misses some contrast issues on complex backgrounds.
How to Become EAA Compliant — Step-by-Step Roadmap
Estimated total time for a small-to-medium website: 2–4 days. For large e-commerce sites with thousands of product pages, plan for 2–4 weeks of focused effort followed by ongoing maintenance.
| Step | Action | Est. Time |
|---|---|---|
| 1 | Run a Lighthouse accessibility audit on homepage, top 5 pages, and checkout/contact flow | 1 hour |
| 2 | Fix color contrast failures using the Color Contrast Checker | 2–4 hours |
| 3 | Add alt text to all informative images (audit with axe DevTools) | 2–8 hours (site-dependent) |
| 4 | Add visible <label> elements to all form inputs | 1–3 hours |
| 5 | Test full keyboard navigation — fix any traps, unreachable elements, or missing focus indicators | 2–4 hours |
| 6 | Add lang attribute to <html> tag on all pages | 5–15 minutes |
| 7 | Add a "Skip to main content" link at the top of each page template | 30 minutes |
| 8 | Add aria-label to all icon-only buttons | 1–2 hours |
| 9 | Test with NVDA (Windows) or VoiceOver (macOS) screen reader | 2–4 hours |
| 10 | Write and publish an accessibility statement | 1 hour |
After initial compliance: ongoing maintenance
Schedule quarterly accessibility re-audits using Lighthouse and axe. Run the contrast checker on every new design component before shipping. Add accessibility checks to your PR review process — preventing regressions is far cheaper than fixing them later.
Accessibility Statement — What to Include
The EAA requires businesses to publish an accessibility statement on their website. This serves two purposes: demonstrating good-faith compliance effort and providing users with a way to report issues. Include all five elements below:
Conformance Level Claimed
State which WCAG version and level you claim: "This website aims to conform to WCAG 2.1 Level AA."
Known Limitations
Be honest about areas not yet compliant and describe alternatives: "Our PDF documents are not fully accessible. An accessible HTML version is available on request."
Contact for Feedback
Provide an email address or contact form specifically for accessibility issues: "Report accessibility issues to accessibility@example.com."
Date of Last Review
State when the statement was last reviewed and updated. Update this date after each quarterly audit.
Enforcement Authority Link
Include a link to the relevant national enforcement authority so users know how to escalate complaints if needed.
Example Accessibility Statement
This website aims to conform to WCAG 2.1 Level AA standards. We test our pages regularly using Google Lighthouse and axe DevTools, supplemented by manual keyboard and screen reader testing. Known limitations: Our legacy PDF catalog documents are not yet fully accessible. An accessible HTML version is available on request by emailing accessibility@example.com. We welcome feedback about accessibility. Contact us at: accessibility@example.com Last accessibility review: June 2026.
For a deeper dive on color contrast requirements referenced in Section 1.5 of the checklist above, see our WCAG Color Contrast Guide.
Frequently Asked Questions
When did the European Accessibility Act come into effect?▼
Does the EAA apply to businesses outside the EU?▼
What is the difference between the EAA and the Web Accessibility Directive?▼
Are small businesses exempt from the EAA?▼
What are the penalties for non-compliance?▼
Which WCAG version does the EAA require?▼
Does the EAA apply to mobile apps?▼
What is EN 301 549?▼
How do I test my website for EAA compliance?▼
Do I need to hire an accessibility consultant?▼
Start Your Compliance Check Now
The most common accessibility failure is color contrast — and it is the easiest to fix. Use our free Color Contrast Checker to verify every text and background combination on your site meets WCAG AA standards. Instant results, auto-fix suggestions for failing pairs, no signup required.
Related Tools & Guides
Color Contrast Checker
Test WCAG AA/AAA compliance with auto-fix suggestions — the #1 accessibility tool
Color Picker
Explore colors in HEX, RGB, HSL before checking contrast
Image Compressor
Optimize images for faster load times — improving accessibility and Core Web Vitals
WCAG Color Contrast Guide
In-depth guide to AA/AAA standards, dark mode, and EAA requirements