On October 5, 2023, the World Wide Web Consortium published WCAG 2.2 as a W3C Recommendation. The update added nine accessibility success criteria. For businesses, it offered more specific guidance for designing website tasks that people can complete with different ways of seeing, moving, understanding and interacting.
Look at the obstacles within a real task
The new criteria address issues including keyboard focus hidden by page content, dragging interactions, target size, repeated information entry and accessible authentication. These details can affect an ordinary enquiry or account journey. A control may be present on a page while remaining difficult to locate or operate.
Start with a task that matters to visitors: requesting a quotation, registering for an activity or finding an existing document. Follow the steps from the first page through confirmation. Record the point where someone needs to use a precise pointer movement, remember information unnecessarily or work around a control they cannot reach.
Keep help, forms and sign-in usable
A practical design review can examine whether help remains easy to find, whether information already supplied must be entered again, and whether sign-in works with tools people rely on, such as password managers. Apply the relevant criterion with its conditions and exceptions. The requirements span different conformance levels; a short checklist should not erase those distinctions.
For a bilingual website, repeat the journey in French and English. Check that instructions, field labels, errors and confirmation messages remain understandable in both versions. Longer text can change a layout, and a translated link needs to lead to the appropriate destination. These checks connect accessibility work with the experience your customers actually use.
Use observations to organize improvements
W3C’s preliminary accessibility checks provide a starting point for reviewing keyboard access, focus and forms. They are not a comprehensive evaluation. Combine practical observations with the expertise and testing appropriate to the project, including assistive technologies where relevant.
Describe each issue in terms of the task it prevents, the conditions in which it occurs and the expected result. Agree on priorities with the people responsible for content and development, then repeat the affected journey after a correction. This gives the team a useful way to follow progress beyond a list of visual adjustments.
Nuagerie’s website and application development services can help incorporate these questions into a redesign or a focused improvement project. Scope, evaluation methods and acceptance criteria should be agreed explicitly; an initial review does not establish whole-site conformance.
To discuss a project, identify two or three important visitor tasks, the languages offered and any difficulty already reported. Our team can help turn those examples into a practical development brief with clear verification steps and ownership for future changes.
