AXS-63Recommended
Ask for a conformance report before you buy
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.
How to do it
A widget you embed becomes part of your service, so its barriers become yours. Ask for a report on the current VPAT template, version 2.5Rev from April 2025. Its EU edition covers EN 301 549, and its INT edition covers EN 301 549, Section 508 and WCAG 2.2 in one report. Each criterion says "Supports", "Partially Supports", "Does Not Support" or "Not Applicable", with remarks. Read every "Partially" and "Does Not". Test 3 of them by keyboard and screen reader, and put the right to a fix into the contract. Record the report in the vendor register.
How to check
Every vendor in the register whose interface reaches customers has a conformance report dated after its last major release. It names its VPAT edition and version, such as INT 2.5Rev. It has a note of the 3 claims you tested.
Sources
Related rules
- AXS-76 Make chat screens work with a keyboard and a screen reader in Accessibility
- CMP-13 Keep one register of vendors in Compliance and governance
- AXS-64 Publish your own conformance report in Accessibility
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/buy-accessible-software">Agent Wranglers accessibility playbook</a>. In code you write, add a comment next to it with the same link.