Accessibility moved into procurement

EN 301 549 v4.1.1 pulls WCAG 2.2 Level AA into the European Accessibility Act's presumption of conformance, and the practical effect is that accessibility stops being a design review item and becomes a contract term.

The dates are already in force. New services were due by 28 June 2025. Existing services have until 28 June 2030. The second date sounds distant and is not, because the work it implies is remediation of a codebase that was built without the requirement, and that is measured in quarters rather than sprints.

Reading the shift as a purchasing change

The important change is not the criteria themselves. WCAG 2.2 adds a modest set over 2.1, mostly around focus appearance, dragging alternatives and target size, and a team already working to AA will find most of it familiar.

The change is where conformance gets checked. Once a standard sits inside a presumption of conformance, procurement can ask for it, and a vendor answering a tender has to say something specific. That moves accessibility from a thing a design team advocates for into a thing a sales team has to be able to evidence.

For an enterprise product, this reverses the usual internal argument. Accessibility work has historically competed with roadmap work for the same quarter. A contract term does not compete. It qualifies the deal.

Writing an accessibility conformance report that survives scrutiny

The artifact procurement asks for is a conformance report, and the failure mode is a document that claims full support on every criterion. A report with no partial support anywhere reads as untested to anyone who has written one.

A useful report is specific about what was tested, on which assistive technology and which browser, and what the known gaps are with a date against each. A stated gap with a remediation date is a commercially normal answer. An unstated gap that a buyer's own audit finds later is a commercial problem.

A report with no partial support anywhere reads as untested to anyone who has written one.

BrilliantUX editorial principle

Sequencing remediation against the deadline

The order that works is by exposure rather than by severity. The flows that appear in every customer demonstration and every trial account are the ones a buyer will check, and they are also usually the flows with the most traffic. Authentication, the primary task, settings and anything that produces a document or an export.

The structural work underneath is the same work that a design system audit produces. Focus order, programmatic labeling, contrast bound to tokens rather than to hex values, and state changes announced rather than merely rendered. Fixed in components, they are fixed everywhere. Fixed per screen, they will be undone by the next screen.

Teams with a 2030 obligation and no current baseline should spend this quarter on the baseline rather than on fixes. It is difficult to argue for a remediation budget without a number, and an audit of the top flows produces one.