Skip to main content
WOLFITWAY

Wolfitway · Timișoara

European Accessibility Act: A Practical Website Audit Brief

European Accessibility Act: A Practical Website Audit Brief

Begin an accessibility project with two separate questions: which legal requirements apply to your service, and which barriers prevent people using it? A scanner can help find technical problems. It cannot decide your entire legal position or certify the whole service.

Updated November 18, 2026. Photos are AI-generated conceptual scenes, not real clients, staff or documented customer projects.

Begin an accessibility project with two separate questions: which legal requirements apply to your service, and which barriers prevent people using it? A scanner can help find technical problems. It cannot decide your entire legal position or certify the whole service.

Correction, November 18, 2026: the earlier headline implied a uniform €100,000 exposure and the text treated WCAG 2.2 AA as an automatic statement of EAA law. Those shortcuts have been removed. Scope, national rules and applicable standards require their own assessment.

Confirm the legal scope first

The EAA covers specified products and consumer services, including e-commerce, rather than every website or every SaaS product. Its national measures generally apply from June 28, 2025, with relevant transitions and exemptions. Article 30 leaves penalty rules to member states; there is no single EU-wide fine in the directive.

Directive (EU) 2019/882, official text: scope, transitions and penalties

Ask the person reviewing legal scope to identify the service, relevant countries, the applicable provisions and any exemption relied on. Ask the technical assessor to identify the criteria and methods used. Do not let one document silently substitute for the other.

What current accessibility data can tell you

WebAIM's February 2026 automated analysis of one million prominent homepages found detected WCAG failures on 95.9% of them, averaging 56.1 detected errors per page. Its report uses WAVE and explains that automation cannot detect every failure. This is not a percentage of businesses violating the EAA or a test of every page on those sites.

WebAIM Million 2026: sample, method and results

Use findings like these to prioritize investigation, not to frighten a particular owner with an assumed fine. The barriers on their actual customer journey are the things an assessor needs to document.

Colleagues reviewing a website task with a keyboard and monitor.
AI-generated conceptual photo. The people and setting do not depict actual clients, staff or a documented project.

Ask for complete tasks, not only a homepage score

List the important journeys: find a service, submit a request, create an account, sign in, pay, cancel or get support. Include the error and recovery states. Someone who can read the homepage may still be unable to complete checkout.

For each journey, record the pages, third-party tools and documents involved. Identify which parts your team can change and which need a provider's help. That turns a general report into a workable remediation plan.

Check keyboard use and focus

Have the assessor move through each task without a mouse. They should be able to reach the controls, see where focus is, operate menus and dialogs, and leave components without becoming trapped.

Ask for a reproducible description of each failure: starting page, steps, expected behavior, actual behavior and affected component. “Keyboard issue” is not enough detail for a developer to reproduce it reliably.

Check text, labels and errors

Inspect whether text remains readable in the actual design, including backgrounds with photos and gradients. Check field labels and whether error messages explain what went wrong and how to fix it. Test content after zooming and reflowing, not just at the designer's default viewport.

An automated checker can identify some missing names and contrast problems. A person still needs to assess whether the name makes sense and whether the journey is understandable.

Check small controls with the right exceptions

WCAG 2.2 criterion 2.5.8 specifies a 24-by-24 CSS-pixel minimum target or qualifying alternatives and exceptions, including spacing and inline targets. It is inaccurate to say every smaller control necessarily fails. Larger controls may still be a good usability choice.

W3C: understanding Target Size (Minimum)

Ask for a report you can act on

Report itemWhy it matters
Scope and dateShows which pages, states and versions were checked
MethodDistinguishes automated checks, manual review and user testing
Reproduction stepsLets the team verify the reported barrier
Affected criteria and severityExplains the assessment without a vague score alone
Owner and proposed fixTurns the finding into assigned work
Retest resultShows whether the barrier was actually addressed

Ask whether the review includes assistive-technology testing and how users with disabilities can contribute. Record limitations openly. One clean automated run is not proof of full accessibility.

What to do next

Use a free scan as a starting point, then prioritize barriers in real customer tasks and arrange a suitable manual assessment. Try the WCAG checker, or read the separate SaaS scope and procurement guide.

This is a technical planning guide, not a determination of the law applicable to your business. Sources checked November 18, 2026.

Share Insight:
Dan at his desk with Cipi the cat
Written by

Dan-Ioan Drăguța

Founder & Chief Architect of Wolfitway. Building sovereign creator pipelines, autonomous LLM workflows, and direct-to-database commerce systems without third-party vendor lock-in.

Meet the builder and the boss →

Liked this? Get the next one by email

Landing page teardowns, accessibility fixes and what I shipped. One short email, no spam, unsubscribe in one click.

I'll email you a link to confirm. Nothing else arrives until you click it. Stored on my own servers, never sold. How I use your details

Community Discussion

0
Be the first to comment

No community comments yet on this analysis. Share your thoughts above.