Method

How we test

Our audits follow the W3C's evaluation method, WCAG-EM, so results are defensible. Then we add what CI tools can't do: manual checks, testing with screen readers, and full journeys from start to finish.

Process

An audit, step by step.

  1. 01 – Scoping call

    30 to 45 minutes. We agree which journeys make money or carry legal risk, check whether the EAA applies to you, and look at your tech stack and existing CI checks.

  2. 02 – Scope sign-off

    We fix the target (WCAG 2.2 AA through EN 301 549), the pages, browsers and assistive technology, what's out of scope, and the retests included.

  3. 03 – Sample

    Each journey you choose, end to end on desktop and phone, with every page, dialog and state it passes through, such as errors, modals and logged-in views.

  4. 04 – Automated baseline

    We run axe-core and Lighthouse across the sample and log each issue once per component. If you already have CI checks, we review their output so you don't pay for what you already have.

  5. 05 – Manual testing

    Every screen, against the full WCAG 2.2 AA checklist: keyboard, zoom and reflow, contrast, forms, media, and structure and naming in the accessibility tree.

  6. 06 – Screen reader journeys

    Each critical journey with NVDA on Windows and VoiceOver on iPhone, plus TalkBack on Android if mobile matters. We record whether a person could finish the task, not just which criteria failed.

  7. 07 – Triage

    Duplicates merge into issues tied to components. Each gets a severity, an effort estimate, and its WCAG and EN 301 549 reference.

  8. 08 – Report

    A summary for leadership first, then the issue log. Every issue has a screenshot or code snippet, steps to reproduce, the impact on users in one sentence, and a recommended fix with code.

  9. 09 – Walkthrough

    60 minutes: the summary for leadership, then the top 10 issues with your developers. We agree owners and fix order.

  10. 10 – Retest and statement

    We retest fixed issues, update the report, and hand over a draft accessibility statement.

Severity

How we rate severity.

The same four words in every report, so your team can sort the backlog without reading every finding.

Blocker
A group of users can't complete a critical task. For example, the Pay button can't be reached by keyboard.
High
The task is possible only with major effort or a workaround, or a key page has a legal-risk failure. For example, form errors aren't announced to screen readers.
Medium
Causes confusion or slows people down, but a workaround exists. For example, inconsistent heading levels.
Low
Minor, or good practice beyond AA. For example, redundant title attributes.

Standards

Standards we test against.

WCAG 2.2 level AA. 55 success criteria. Automation can settle only 1 of them alone and helps with 17 more. The other 37 need a person.

EN 301 549. The European standard the EAA points to. Its web clause is the WCAG number with a 9 in front, so 2.4.11 becomes 9.2.4.11. Native apps use clause 11.

European Accessibility Act. Applies to e-commerce, banking, transport, e-books and other consumer services. Small businesses with fewer than 10 staff and an annual turnover of 2 million euros or less are exempt from the rules for services.