WCAG 2.2.

Where WCAG 2.2 fits on a long engagement.

Accessibility is a legal requirement rather than a preference in most markets we serve. The European Accessibility Act applies from June 2025 to a broad range of products and services sold in the EU, and equivalent obligations exist in the UK and elsewhere. Treating conformance as optional is a commercial exposure.

Automated testing catches perhaps a third of issues. Colour contrast, missing alternative text and some structural problems are detectable by tooling; whether alternative text is meaningful, whether focus order makes sense, and whether an interaction works with a screen reader all require manual testing with assistive technology.

What an assigned team does with WCAG 2.2.

Retrofitting accessibility is far more expensive than building it in. A component library built accessibly makes every screen using it compliant by default, while remediation means auditing and fixing every screen individually.

Building it into the component layer from the start is the approach that scales, and it is scoped with outsourced design team capacity alongside frontend.

What we use WCAG 2.2 for.

• Conformance as a legal baseline AA treated as a requirement, given EAA and equivalent obligations.
• Manual testing with assistive technology Screen reader and keyboard verification, which tooling cannot replace.
• Accessibility built into components Compliance by default rather than remediation screen by screen.

How WCAG 2.2 capacity is assigned.

Accessibility work is assigned across design and frontend capacity, built into the component layer rather than audited afterwards.