Skip to main content

Custom audit method

How the custom manual EAA audit works.

This method applies to custom audits. Public-site scans are automated and human-reviewed, but they do not include every manual test described here.

1. Scope around risk

We map the service, target markets, technology, known issues, critical tasks, and representative templates. The result is a written scope before testing begins.

2. Test in layers

We combine automated checks with keyboard-only operation, screen-reader review, zoom and reflow tests, visual inspection, and task-based exploration. Tools support judgement; they do not replace it.

3. Record reproducible evidence

Each confirmed finding identifies where the barrier occurs, how to reproduce it, who is affected, its severity, the relevant technical criterion, and a recommended fix.

4. Prioritise and explain

We distinguish blockers and high-impact barriers from moderate or advisory items, then review systemic patterns that can prevent repeated defects.

5. Verify

Optional retesting checks the agreed fixes in context. Resolved, partially resolved, and outstanding findings are reported clearly.

Reference framework

  • WCAG 2.2 Level AA as the principal web accessibility benchmark
  • EN 301 549 where it is relevant to the product or procurement context
  • Directive (EU) 2019/882 and applicable national implementation context
  • Platform conventions and assistive-technology behaviour

Severity with a user-impact lens

Critical

A core task is blocked for one or more user groups with no reasonable workaround.

High

A major barrier makes a task very difficult or unreliable.

Moderate / advisory

The experience is degraded, inconsistent, or at risk of future failure.