EAA Compliance Checklist for Websites
EAA compliance checklist for websites: the WCAG 2.1 AA checks that matter most, journeys to test, documents and media, Annex V information and upkeep.
Short answer
A website in scope of the European Accessibility Act needs four things: an interface that meets WCAG 2.1 Level AA (the web chapter of EN 301 549), accessible key journeys — sign-up, checkout, payment and support — including third-party parts, published information on how the service meets the requirements (Article 13 and Annex V), and a written assessment wherever you claim a requirement would be a disproportionate burden. Test with automated tools, then by hand, and keep records.
- Interface standard today
- EN 301 549 v3.2.1 · WCAG 2.1 AA
- WCAG 2.1 A + AA criteria
- 50
- Public information
- Article 13 · Annex V
- Most common barrier on EU homepages
- Empty links · 57.1%
- Applies since
- 28.06.2025
EAA Compliance Checklist for Websites
This checklist turns the European Accessibility Act into work items for a website or web app. It assumes the Act applies to you — usually because you sell to consumers online; our guide "What is the European Accessibility Act?" covers scope and exemptions. It is not legal advice: the law that applies is your country's national act.
Start with the five most common barriers
In September 2026 we checked 3,754 homepages of popular national websites across the EU. 81.3% had at least one of five basic barriers, and they are the cheapest place to start:
| Barrier | Share of homepages | WCAG 2.1 |
|---|---|---|
| Links with no accessible text (icon-only links, empty anchors) | 57.1% | 2.4.4, 4.1.2 |
| Form fields without a label | 48.8% | 1.3.1, 3.3.2 |
| Images without alt text | 34.9% | 1.1.1 |
| Buttons without an accessible name | 33.3% | 4.1.2 |
| No page language declared | 8.1% | 3.1.1 |
1. Interface checks (WCAG 2.1 Level AA)
The Act asks for websites and apps that are perceivable, operable, understandable and robust (Annex I, Section III). EN 301 549 v3.2.1 tests that with the 50 WCAG 2.1 A and AA success criteria. The ones that fail most often in practice:
Perceivable
- Every informative image has alt text that says what it shows or does; decorative images have empty alt (1.1.1).
- Pre-recorded video has captions; audio-only content has a transcript (1.2.1, 1.2.2).
- Headings, lists, tables and form labels are real markup, not just styling (1.3.1).
- Text contrast is at least 4.5:1, or 3:1 for large text (1.4.3); icons, input borders and focus indicators reach 3:1 (1.4.11).
- The page works at 200% zoom and in a 320 px wide window without horizontal scrolling (1.4.4, 1.4.10).
- Information is not given by colour alone, such as red-only error fields (1.4.1).
Operable
- Everything works with the keyboard alone, with no keyboard trap (2.1.1, 2.1.2).
- A skip link or landmarks let users bypass repeated blocks (2.4.1).
- Each page has a descriptive title (2.4.2); focus order follows the visual order (2.4.3); the focus is always visible (2.4.7).
- Link text makes sense in context — no bare "click here" (2.4.4).
- Time limits, such as session timeouts in checkout, can be extended (2.2.1).
- Nothing flashes more than three times a second (2.3.1).
Understandable
- The page language is declared, and changes of language are marked (3.1.1, 3.1.2).
- Choosing an option or typing in a field does not unexpectedly submit or move the user (3.2.2).
- Errors are identified in text, with a suggestion how to fix them (3.3.1, 3.3.3); every field has a visible label or instruction (3.3.2).
Robust
- Custom controls — menus, tabs, dialogs, toggles — expose name, role and state to assistive technology (4.1.2).
- Status messages such as "added to basket" are announced without moving focus (4.1.3).
2. Test whole journeys, not just pages
A page can pass while the task fails. Walk through each key journey with the keyboard only and with a screen reader (NVDA or VoiceOver are free): finding a product, adding it to the basket, signing up or in, checkout, payment, and contacting support.
For e-commerce the Act asks specifically (Annex I, Section IV) for accessible identification, security and payment, and for passing on the accessibility information of the products you sell when the manufacturer provides it. Third-party parts count: your payment provider's form, the consent banner, the chat widget, embedded maps and video players are part of your service. Test them, and ask the vendor for their conformance information.
3. Documents and media
- PDFs and other office files published from 28 June 2025 must be accessible; older ones are excluded.
- Pre-recorded video and audio published from 28 June 2025 need captions and, where the picture carries information, audio description or an alternative.
- Content you neither fund, develop nor control (such as user posts) is outside the requirements.
4. Information and support
- Publish how the service meets the requirements (Article 13, Annex V): a general description of the service, how it works, and how it meets the Annex I requirements — in the terms and conditions or an equivalent document, in written and oral form. Our guide on writing the EAA accessibility statement covers the content.
- Help desks, call centres and chat give information about the service's accessibility in accessible formats (Annex I, Section III).
- Offer a way to report barriers and answer it.
5. Exemptions, recorded
- Microenterprises providing services (fewer than 10 persons and a turnover or balance sheet of no more than €2 million) are exempt from the service requirements. Record the figures that show it.
- If a requirement would be a disproportionate burden or fundamentally change the service, document the assessment against the criteria in Annex VI, inform the competent authority, keep it for five years and renew it at least every five years. Cost alone, without that assessment, is not an exemption.
6. Keep it current
- Test new templates and features before release, with an automated scan in the build or review process.
- Re-test key journeys after any change to checkout, sign-in or third-party widgets.
- Keep a dated record of what was tested, how, what was found and what was fixed — it is the evidence an authority asks for.
- Update the published accessibility information when the service or its known issues change.
Automated and manual testing
Automated rules find a useful share of problems quickly — missing alt attributes, unlabeled fields, low contrast, invalid ARIA — but they cannot judge whether alt text is meaningful, whether the focus order makes sense or whether a journey can be completed. Use both.
RankProof's free tools cover the automated part: the accessibility scanner runs WCAG 2.1 A and AA rules in your browser and links each finding to the WCAG criterion and our EAA checklist; the colour contrast checker tests colour pairs; the alt text checker lists missing alt text; and the statement generator drafts the Annex V information. Our EAA requirements checklist lists the manual checks no tool can do.
Free tools on this topic
Guides on this topic
Research data on this topic
Start with a free check
Run the free audit or pick one of the tools — no account, and every result explains what to fix.
Try Free Scan