Agent Wranglers

AXS-71Recommended

Audit a sample chosen by the W3C method

Base each accessibility audit on a written scope and a sample. The sample holds every common screen, every critical journey from start to end, each page type and each technology. Add random pages that make up at least 10% of that sample.

By Agent Wranglers. Updated .

How to do it

The W3C evaluation methodology, WCAG-EM, has five steps. They are define the scope, explore the product, select a sample, evaluate it and report. Version 2.0 became a W3C Group Note on 23 July 2026, and it covers apps as well as websites. Name the target, usually WCAG 2.2 AA, and the browsers and assistive technology the product must work with. Include states such as errors, empty lists and signed-in views. The random pages catch what the chosen ones miss. The report feeds Publish how each service meets the accessibility rules and Publish your own conformance report. The scan in Check accessibility in every build runs between audits.

How to check

Each audit report names WCAG-EM 2.0 as its method. It also names the WCAG version and level, the scope, the browsers and assistive technology used, and the sample list. Every critical journey appears with all its steps, and the random part is at least 10% of the chosen part.

Sources

For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/accessibility/testing-and-procurement/audit-sample">Agent Wranglers accessibility playbook</a>. In code you write, add a comment next to it with the same link.