WCAG vs EAA: Which Accessibility Requirements Apply to Your Website?

WCAG vs EAA: quick answer

WCAG vs EAA is a common question for teams that build websites and apps for EU or UK users. WCAG is a technical set of success criteria for accessible web content. The EAA is EU legislation that creates legal obligations for certain products and services sold in the EU. One is a technical standard, the other is a legal framework. Which one applies depends on your product, your customers and where you operate.

What WCAG is

WCAG stands for Web Content Accessibility Guidelines. It is published by the W3C and describes testable success criteria for web content. WCAG organizes criteria into levels called A, AA and AAA and into grouped principles such as perceivable, operable, understandable and robust. Developers, designers and testers use WCAG to produce measurable accessibility work.

What the EAA is

The European Accessibility Act, usually written EAA, is EU legislation that sets accessibility requirements for certain goods and services placed on the EU market. The EAA creates legal obligations for economic actors rather than technical success criteria by itself. Member states and implementing measures determine how those obligations are checked and enforced.

Key differences — short list

• Nature: WCAG is a technical guidance document. EAA is legal/regulatory.
• Scope: WCAG covers web and digital content. EAA covers a defined set of products and services in the single market.
• Use: Organisations use WCAG to design and test accessibility. Regulators reference legal texts and technical standards when measuring compliance under the EAA.

How to tell which applies to your website or service

1. Identify where you place the product or service on the market. If you sell or target customers in an EU Member State, check whether your product or service type appears in the EAA listing.
2. Check your legal status. Are you an economic operator in the EU, a public body, or a private business based outside the EU that serves EU users? Different rules may reach you in different ways.
3. Find the national implementing rules. The EAA is implemented via Member State measures and may point to technical standards or to specific WCAG versions and levels.
4. Even when EAA does not apply, many buyers, contracts and public rules ask for WCAG conformance as a technical requirement. Use WCAG for design and testing regardless of EAA scope.

Mapping WCAG to EAA obligations (practical view)

The EAA sets functional accessibility obligations. Below is a practical mapping showing how common WCAG work supports those obligations.

Functional obligation (EAA style)	Example WCAG focus
Content must be perceivable	Text alternatives for images, captions for media, text resize and reflow checks
Controls must be operable by people with different input methods	Keyboard focus order, visible focus indicator, no keyboard traps
Information must be understandable	Clear labels, error identification, consistent navigation
Content must be compatible with assistive technologies	Semantic HTML, ARIA used correctly, accessible form markup

Practical decision framework for product owners

Use this minimum process to decide obligations and next actions.

1. List the countries you actively sell or provide services to.
2. Check whether your product or service is listed in the EAA text or national transposition. If it is, treat the EAA as relevant.
3. Set a technical target. Many organisations adopt WCAG as the technical benchmark. Confirm which WCAG version and conformance level your regulator or customer expects.
4. Audit against that WCAG target and create a remediation plan with timelines and owners.
5. Publish an accessibility statement that explains scope, conformance status and contact points for accessibility requests.

Step-by-step checklist to comply with both

• Define scope: pages, apps, documents and third-party components in use.
• Set a WCAG target (version and level) that matches legal or buyer requirements.
• Run automated scans and manual checks against those WCAG success criteria.
• Conduct user testing with people who use assistive technology.
• Fix high-impact issues first: keyboard access, colour contrast, labels, form errors and alternative text.
• Document results and publish an accessibility statement or compliance report.
• Include accessibility requirements in procurement and vendor contracts.
• Monitor and repeat audits after major releases.

Common developer mistakes and how to avoid them

Teams often assume automated testing is enough. Automated tools catch roughly 20 to 40 percent of issues depending on the tool, but they miss keyboard problems and many usability gaps. Manual testing plus user testing is essential.

Avoid these mistakes

• Using ARIA to fix structural HTML problems rather than fixing the HTML itself.
• Relying only on colour to convey information without text or icons.
• Not testing keyboard-only or screen reader workflows for common tasks like checkout or login.
• Shipping inaccessible PDFs and documents without accessible source files.
• Leaving no documented remediation plan or owner for outstanding issues.

Enforcement, complaints and risk

Enforcement approaches and penalties differ across Member States. The EAA provides a legal route for complaints and market surveillance for covered products and services. Even where EAA does not apply, contracts and procurement rules can create enforceable accessibility obligations. Treat accessibility as both a legal and a risk management item.

Where to get authoritative answers

For legal interpretation and final scope, consult the EAA text and your national implementing legislation. For technical conformance the W3C WCAG documents are the normative guidance used by designers and testers. If you need certainty for procurement or litigation, get legal advice from counsel familiar with EU accessibility law.

Quick action plan for teams today

1. Decide whether EAA could apply to your product: check markets and product categories.
2. Set or confirm a WCAG target your team will meet.
3. Run a focused audit on critical user journeys and fix the top 10 issues first.
4. Publish an accessibility statement and a channel for feedback.
5. Plan quarterly accessibility reviews tied to releases.

If you want, tell me where you operate and what type of site or service you run. I can suggest a specific WCAG target and a tailored checklist for the EAA risk areas you face.