# WCAG 2.2: reference and accessibility action plan

Prepared 7 October 2026 for Social Innovation CIC, NeuroPathway and Safe Space.

## Official reference

W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Recommendation dated 12 December 2024. Verified online 7 October 2026.
https://www.w3.org/TR/WCAG22/
Fixed version: https://www.w3.org/TR/2024/REC-WCAG22-20241212/

This file records the official reference and a proposed implementation plan. It does not certify any existing site. Use the latest official page and its errata when implementing.

## Standard to follow

Target Level AA, including all applicable A and AA criteria across complete pages and processes. WCAG covers perceivable, operable, understandable and robust content. [W3C, sections 1–4 and Conformance]

Key requirements: text contrast at least 4.5:1, or 3:1 for large text; relevant controls and graphics 3:1; text resizing to 200%; reflow at 320 CSS pixels with specified exceptions; keyboard operation without traps; visible focus that is not entirely hidden; text alternatives; labelled inputs and understandable errors; accessible status messages; alternatives to dragging; minimum 24×24 CSS-pixel targets subject to exceptions; accessible authentication. [W3C, 1.1.1, 1.4.3, 1.4.4, 1.4.10, 1.4.11, 2.1.1–2.1.2, 2.4.7, 2.4.11, 2.5.7–2.5.8, 3.3.1–3.3.2, 3.3.8, 4.1.3]

## Proposed work for your products

These are tasks to inspect and implement, not verified defects.

1. **Shared layout:** inspect navy, teal and gold colour combinations; use semantic headings, landmarks, descriptive links and a skip link. Check mobile layouts, zoom and text spacing. Aim for comfortable 44×44-pixel touch controls as a design preference.
2. **Navigation:** test every menu, dialog and button with keyboard only. Manage dialog focus and return focus on closing. Ensure sticky headers and footers do not obscure the active control.
3. **Login:** permit password managers and pasting. Provide an accessible alternative to QR-only entry. Inspect error recovery and any authentication tests.
4. **Forms and questionnaires:** label every field; group related choices; explain errors beside fields and in an error summary. Preserve entered answers during correction. Check repeated information and consistent help.
5. **NeuroPathway:** accompany RAG indicators with words, provide text or table alternatives for pattern graphs, announce saving and report-generation status, and inspect exported reports for accessibility.
6. **Safe Space and the game:** label emoji choices in words; provide alternatives to sound-only questions and drag-only letter tiles. Offer adjustable timing where needed. Avoid flashing effects and provide controls for moving content. Reduced motion and predictable, low-pressure feedback are additional design preferences.
7. **Media:** inspect image alternatives, captions, transcripts and any required audio description. Keep decorative images out of screen-reader output.

## Verification and completion

My recommended sequence: inventory pages and journeys; audit shared components; fix login/navigation/forms first; then dashboards and the game; retest complete journeys.

Combine automated checks with keyboard, screen-reader, mobile, zoom and user testing. Record criterion, page, reproduction steps, severity, owner and retest outcome for each finding. Publish an accurate accessibility statement with known limitations and a contact route. Do not claim AA compliance merely because an automated scan passes.

Current status: reference reviewed; implementation plan prepared; existing sites not audited or changed in this task. WCAG conformance and UK legal duties are separate questions; this document makes no legal-compliance finding.

## Source

W3C (12 December 2024), WCAG 2.2: https://www.w3.org/TR/WCAG22/ — accessed 7 October 2026. All numbered criteria above refer to this primary source. Product priorities and testing sequence are my recommendations.