SUM VISUM / Practice note
Accessibility belongs in the project brief
A business website must let visitors find information, move through it and take the next step. A polished opening screen is only one part of that experience.
The W3C’s WCAG 2.2 reference organizes accessibility criteria around perceivable information, operable controls, understandable behavior and robust implementation. It includes keyboard access, visible focus and minimum target size. Automated checks cover only part of a review.
What this changes in a project
Our approach is to include key journeys in acceptance: open the menu, find a service, switch language and prepare a project enquiry. Check the same actions with a keyboard and at narrow widths. Record what was actually tested and keep device or assistive-technology gaps visible.
A useful delivery brief names those journeys before visual design begins. It also identifies who will maintain content, so future changes preserve clarity rather than gradually weakening it.
All notes