News Context: W3C published WCAG 2.2 as a Recommendation on 5 October 2023. This retrospective explainer, prepared on 31 October 2026, examines what the standard means for a website purchasing conversation; it is not breaking news.
What Changed in the Standard
W3C’s publication announcement says WCAG 2.2 adds nine success criteria since WCAG 2.1. Its overview of the additions includes focus visibility, dragging alternatives, target size and accessible authentication.
A standard’s existence does not establish that a particular website conforms. Nor does this article determine which legal requirements apply to your organization. The useful first step for a buyer is to agree the project’s accessibility scope and evidence.
Turn a Broad Promise Into a Testable Brief
Best10Companies Analysis: “Make it accessible” is difficult to price or accept as a deliverable. Ask a supplier to identify the target version and conformance level, the pages and journeys included, the testing method and how findings will be resolved.
Keep the brief focused on the actual website. A company with an online quotation form should include that form in the test scope. A company selling products should include discovery, product selection and the checkout journey rather than checking only the homepage.
Discuss Real Visitor Tasks
| Visitor Task | Question for the Supplier |
|---|---|
| Navigate without a mouse | Can a visitor see and follow keyboard focus? |
| Complete an enquiry | Are labels, errors and correction steps understandable? |
| Use a small screen | Can the key controls be reached and operated? |
| Sign in | How will authentication be tested for accessibility? |
This table is a conversation starter, not a complete WCAG audit or a statement of conformance. A qualified assessment must consider the applicable success criteria and the implemented content.
Agree How Findings Will Be Handled
Request a report that distinguishes the issue, the affected location and the recommended correction. Ask whether the quoted work includes remediation and retesting. If an external booking or payment service is involved, clarify what the developer can change and who will contact that service.
A polished demonstration is useful, but a repeatable test and a documented correction process are more useful during handover. Establish who owns unresolved issues and how they will be reviewed after content changes.
Keep Accessibility in the Handover
Editors will continue adding images, headings and links after launch. Ask for a short content checklist and examples using your own editing system. This makes the project easier to maintain without expecting every editor to become an accessibility specialist.
When you compare companies for Web Development, include testing and handover in the comparison. Source event date: 5 October 2023. Editorial research date: 31 October 2026. The original W3C documents remain the authoritative references.
