WCAG 2.2 Level AA,
checked the way buyers check it.

The Web Content Accessibility Guidelines (WCAG) are the W3C's standard for making web content usable by people with disabilities: blind and low-vision users with screen readers and magnifiers, people who cannot use a mouse, people who are deaf or hard of hearing, and people with cognitive and learning disabilities. WCAG 2.2 was published as a W3C Recommendation on 5 October 2023, and the current edition of the Recommendation is dated 12 December 2024.

WCAG is organised under four principles (perceivable, operable, understandable, robust), each broken into guidelines and testable success criteria at Level A, AA or AAA. WCAG 2.2 is backwards compatible: if you meet 2.2 AA, you also meet 2.1 AA and 2.0 AA, apart from the reporting point on 4.1.1 below.

WCAG 2.2 removes success criterion 4.1.1 Parsing, which required well-formed markup. Browsers and assistive technologies now handle markup errors consistently, and the problems that still matter are covered by other criteria such as 4.1.2 Name, Role, Value. The W3C notes that anyone required by policy to follow an earlier version (for example Section 508, which references WCAG 2.0) may still need to test and report 4.1.1.

Accessibility testing has three layers, and you need all three.

1. Automated scanning. Browser extensions and CI checks find missing labels, contrast failures, missing alt text and invalid ARIA quickly. They catch only part of the issues: they cannot judge whether alt text is meaningful, whether focus order makes sense or whether a custom widget works with a screen reader. Put them in CI so regressions are caught on every pull request.
2. Manual testing. Unplug the mouse and complete every core workflow by keyboard. Zoom to 200% and 400%. Check focus visibility around sticky elements. Check every error state.
3. Assistive technology testing. Use a screen reader on the main workflows: NVDA or JAWS with a Windows browser, VoiceOver on macOS and iOS, TalkBack on Android. Include people who use these tools daily where you can; they find what developers miss.

Record what you tested, with which tools and on which version. That record is the "evaluation methods" section of your VPAT.

No law requires WCAG 2.2 of private companies everywhere, but it is the version buyers and newer rules point to. The UK public sector must meet WCAG 2.2 AA. In the EU, the European Accessibility Act relies on harmonised standards, and the September 2026 EN 301 549 V4.1.1 is aligned with WCAG 2.2. In the US, the Section 508 and ADA rules cite 2.0 and 2.1, which 2.2 AA conformance also satisfies.

TryTrustable scans your public pages against the WCAG 2.2 Level A and AA rules with axe-core, the open-source accessibility engine, and maps each failure to its success criterion with the element and how to fix it. It then gives your team a worksheet of all 55 A and AA criteria to set the conformance level and remarks for each, and issues a sealed Accessibility Conformance Report based on the VPAT® 2.5 WCAG edition. Automated rules find only some failures, so the product never marks a criterion "Supports" by itself: that needs manual testing with a keyboard, a screen reader and zoom, by your team or a specialist. It does not yet scan pages behind a login or produce the 508, EU or INT editions. We also help with the rest of the buyer's checklist: security and privacy evidence, a trust center, and frontend performance and API load test evidence. See the enterprise readiness guide.