Accessibility is often introduced as a compliance checklist. Customers experience it more simply: Can I read this? Can I reach it? Can I understand what will happen? Can I finish the task without fighting the interface? Can I recover from an error or ask a person for help?
Start with the four human outcomes
WCAG 2.2 organizes its guidance around content being perceivable, operable, understandable, and robust. Those principles cover far more than permanent disability. They help a customer using a phone in bright sun, recovering from an injury, navigating with a keyboard, zooming text, using a screen reader, dealing with fatigue, or trying to finish a form under pressure.
I can get the information.
Text has useful contrast, images have meaningful alternatives, video has captions, and the structure survives zoom.
I can reach and use the controls.
Keyboard focus is visible, targets are large enough, motion can be avoided, and nothing traps the visitor.
I know what is expected.
Labels, instructions, navigation, errors, and consequences are clear and consistent.
My tools can interpret the page.
Semantic structure, names, roles, and states work across browsers and assistive technology.
Eight customer-level checks
- Zoom to 200%.Important text and controls should remain readable without disappearing behind fixed panels or forcing two-direction scrolling for ordinary content.
- Use only the keyboard.Move through the page, menus, dialogs, forms, and buttons. The focus indicator should stay visible and follow a sensible order.
- Read the links out of context.Repeated “learn more” links are difficult to distinguish. The link should describe the destination or action.
- Inspect the form.Every field needs a persistent label, clear requirements, a useful error, and a path to correct the mistake without re-entering everything.
- Check touch targets.Small, tightly packed controls are difficult for many hands, especially on a moving phone.
- Turn off sound and reduce motion.Information should not depend on audio alone, and decorative motion should respect user preferences.
- Review alternative text.Describe the information an image contributes; leave purely decorative images empty rather than narrating decoration.
- Try the support route.An accessible experience includes a phone, email, or other human alternative when a digital process still fails.
Automation is a filter, not a verdict
Automated scans can find missing labels, contrast failures, duplicate IDs, and some structural problems. They cannot reliably judge whether the focus order makes sense, an error is understandable, alternative text communicates the right idea, or the whole customer task is usable. Combine automated testing with keyboard review, screen-reader checks, zoom, mobile devices, and people who use the relevant access methods.
What to fix first
Prioritize by customer consequence and frequency. Fix blockers in revenue and service routes first: navigation, contact, booking, checkout, account access, critical documents, and consent. Then address repeated components because one component repair can improve many pages. Finish with content and design-system rules so the same barriers do not return.
Accessibility is also an operating practice. New campaign pages, third-party widgets, PDFs, cookie tools, videos, and form changes can introduce barriers after launch. Give someone ownership, include accessibility in acceptance checks, and publish a truthful accessibility statement with a feedback route.
A better buying question
Instead of asking a supplier to “make it WCAG,” ask which standard and level they use, what they test, what remains outside scope, how third-party tools are handled, what evidence is delivered, and how issues are reported after launch. Conformance is specific; vague accessibility promises are not.
