
Download

EAA Digital and Technical Conformance Assessment Toolkit
Download the complete workbook used to audit client websites and apps for European Accessibility Act compliance (EN 301 549 / WCAG 2.2) — FREE.
Perfect for business and technical people who want to know not just whether their digital services are compliant, but "how compliant."
About the Digital and Technical Conformance Assessment Toolkit
You'll get the most out of this toolkit if you are:
-
In-house developer or QA team who has been asked to check a website or app against WCAG 2.2 / EN 301 549 and need a structured way to do it, not just a scanner report to interpret.
-
Digital agency building or maintaining sites for clients who now fall under the EAA, and who want a repeatable audit process rather than starting from scratch each time.
-
Product, design and compliance lead who needs to understand what "accessible" actually requires in practice — and who need evidence to show their board, not just a gut feeling that things are "probably fine."
-
Anyone who's already run an automated scanner (axe DevTools, WAVE, Lighthouse, Siteimprove) and wants to know what it didn't catch — automated tools typically find only 30–40% of real accessibility barriers.
If you're earlier in the process and not sure if the EAA even applies to your organisation, start with our free EAA Organisational Readiness Toolkit instead. This technical workbook is the next step once you know you need to dig into the detail.
​
-
The toolkit is an Excel workbook with eight connected tabs, each doing a specific job:
-
Web Content Checklist: This is the core of the tool. All 55 WCAG 2.2 success criteria (Levels A and AA), each one explained in plain English with a note on how EN 301 549 references it, so you're not left decoding W3C jargon.
-
Software, Apps & Documents Addendum: Covers the extra requirements that apply specifically to native apps and documents (PDFs, Word files) beyond standard web content.
-
Hardware & Support Services Addendum: This is for anyone with self-service terminals (kiosks, ticket machines, ATMs) or who wants to check their customer support channels are accessible too.
-
Automated Scan Import: A simple paste-in tab for your scanner's raw results. It automatically links each finding back to the relevant checklist item, so you can immediately see which criteria already have known issues.
-
Manual & Assistive Technology Test Log: A structured place to record hands-on testing: keyboard-only navigation, screen readers (NVDA, JAWS, VoiceOver), voice control, magnification.
-
Conformance Dashboard: Automatically calculates your overall pass rate, breaks it down by accessibility principle, and flags your highest-priority issues. No manual tallying required.
-
Accessibility Statement Draft: A head start on the public accessibility statement the EAA requires, with key facts and figures pulled in automatically from your results.
​
-
Accessibility testing requires three different techniques, because each one catches things the others misses:
-
Automated scanning: fast and consistent for mechanical checks like colour contrast, missing image descriptions and basic code structure. Good for broad coverage, but it can't judge context or meaning.
-
Manual expert review: a person checking each requirement against the actual page or app, for things a scanner simply can't assess (does this link text make sense out of context? Does this error message actually help?).
-
Assistive technology walkthroughs: physically testing key journeys (like checkout, sign-up, or booking) using a screen reader, keyboard only, voice control or magnification, the way a disabled user actually would.
This is why the toolkit is built in a specific way. an automated import tab capturing what scanning tools find quickly, plus dedicated checklist and testing-log tabs for the manual and assistive-technology work that scanning alone can't do. Relying on a scanner alone isn't enough to defend a compliance claim if it's ever challenged.
​
-
Each item that is tested gets one of five results:
​
Pass: Fully meets the requirement, no known exceptions
Partial: Meets the requirement in some places or journeys, but not others
Fail: Doesn't meet the requirement
Not Applicable: The requirement doesn't apply to this content or service
Not Tested: Testing hasn't been done yet
​
Failed items also get a severity rating, so you know what to fix first:
​
Critical: Blocks a core task entirely for some users (e.g. can't complete checkout with a keyboard)
High: Seriously hinders a core task or affects many users or pages
Medium: Creates friction or confusion, but a workaround usually exists
Low: Minor or cosmetic, with limited impact
​
The Conformance Dashboard tab turns all of this into a single, easy-to-read score — so you can see at a glance where you stand, and where to focus next.
​
This workbook reflects WCAG 2.2 and its expected incorporation into the next EN 301 549 revision. Standards get refined over time, so it's worth checking the current official guidance before relying on this for a final compliance claim. While this tool can support your work, it is not and should not be considered legal advice on your specific EAA obligations.
