--- title: "Testing and procurement · Agent Wranglers" url: https://agentwranglers.se/playbook/accessibility/testing-and-procurement parts: 10 tokens_total: 8021 updated: 2026-10-27 build: a2a6bdfed830 tokens: 1283 licence: "CC BY 4.0" licence_url: https://creativecommons.org/licenses/by/4.0/ --- # Testing and procurement For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Accessibility](https://agentwranglers.se/playbook/accessibility.md). By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27. > Scan every build, then test journeys with assistive technology and disabled people. Give accessibility an owner and deadlines, and check what you buy and sell. Automated scans find only part of the problems. These rules add tests with assistive technology and with disabled people, an audit method, an owner and deadlines for fixes. They also cover what to ask for when you buy a component and what to publish when you sell one. **For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `Agent Wranglers accessibility playbook`. In code you write, add a comment next to it with the same link. ## Recommended - AXS-81 [Check accessibility in every build](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/accessibility-in-ci.md) · 1,136 tokens · updated 2026-10-27 Run an automated accessibility check on every page or screen in the test suite, and fail the build on any violation. - AXS-82 [Test each critical journey with a keyboard and a screen reader](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/manual-accessibility-tests.md) · 1,142 tokens · updated 2026-10-27 Before each release that changes a critical journey, complete it with a keyboard alone and with two screen readers. Record the result for each journey. - AXS-61 [Test with more than a screen reader](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/assistive-technology-tests.md) · 763 tokens · updated 2026-10-27 Before each release that changes a critical journey, also complete it with voice control, with switch access and at 400% zoom or a screen magnifier. Record a pass or fail for each. - AXS-62 [Test with disabled people](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/test-with-disabled-people.md) · 635 tokens · updated 2026-10-27 Before a new product or a redesign launches, watch at least 3 people who use assistive technology every day try its critical journeys. Fix what blocks them before launch. - AXS-71 [Audit a sample chosen by the W3C method](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/audit-sample.md) · 853 tokens · updated 2026-10-27 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. - AXS-79 [Give accessibility one owner per product](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/accessibility-owner.md) · 670 tokens · updated 2026-10-27 Name one person who owns accessibility for each product. They own the WCAG target, the audit plan, the statement and the queue of accessibility defects. - AXS-80 [Fix accessibility defects by a deadline](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/accessibility-defect-deadlines.md) · 902 tokens · updated 2026-10-27 Label every accessibility defect by severity. Fix one that stops a person finishing a critical journey within 5 working days. Fix every other WCAG A or AA failure within 90 days, or list it as a known gap in the statement. - AXS-63 [Ask for a conformance report before you buy](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/buy-accessible-software.md) · 755 tokens · updated 2026-10-27 Before you buy a component your customers will see, such as a chat widget or a booking tool, get its Accessibility Conformance Report. It covers EN 301 549 or WCAG 2.2 AA. Test its worst claims yourself. ## Optional - AXS-64 [Publish your own conformance report](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/publish-conformance-report.md) · 648 tokens · updated 2026-10-27 If you sell to businesses or the public sector, publish an Accessibility Conformance Report for each product from your latest audit. Give every criterion a result and a remark. ## Avoid - AXS-45 [Accessibility overlay widgets](https://agentwranglers.se/playbook/accessibility/testing-and-procurement/accessibility-overlays.md) · 517 tokens · updated 2026-10-27 Installing an accessibility overlay widget instead of fixing the site. Overlays do not make a site meet WCAG. ## Read this with - [Testing playbook](https://agentwranglers.se/playbook/testing.md). Scan every build for accessibility and test critical journeys with a keyboard and screen readers. - Previous: [Law and statements](https://agentwranglers.se/playbook/accessibility/law-and-statements.md) - [All chapters](https://agentwranglers.se/playbook/accessibility.md)