Treat access as a product task
A menu or form that cannot be operated blocks a real customer journey. WCAG provides structured criteria. Identify which tasks the site must make usable before focusing on an automated badge.
Complete a keyboard journey
Navigate menus, services and enquiry forms without a mouse. Check visible focus, logical order and escape from opened panels. Hidden elements should not trap focus. Record where the task becomes impossible.
Make information understandable
Check contrast, text enlargement and heading structure. Do not communicate status through colour alone. Describe meaningful images according to purpose and avoid cluttering assistive output with decorative details.
Review forms and motion
Use clear labels and actionable error messages. Preserve valid inputs after errors. Respect reduced-motion preferences. Test touch targets and on-screen keyboards on phones as part of the actual task.
Go beyond a score
Automated scans detect only a subset of problems. Add keyboard and screen-reader checks. Prioritize issues by blocked user tasks and make accessibility part of acceptance, rather than a cosmetic adjustment after release.
Worked example: make the scope concrete
Illustrative scenario. Adapt these checks to your own workflow.
Complete an inquiry form without a mouse. Labels, help text and errors should stay connected, with more than colour indicating a problem. Decide where focus goes after validation.
A common failure and why it matters
Passing an automated scan does not prove every interaction is accessible. Test menus, consent, chat and language controls with a keyboard and enlarged text.
How to verify the delivered work
Open and close panels, correct an error and follow visible focus. Provide meaningful alternatives for informative images without making decorative artwork unnecessarily repetitive.
Implementation and maintenance checklist
Review difficult content as well as the most attractive example. Long headings, narrow screens and light or dark backgrounds belong to the same design system. Connect each visual choice to the task: what must be understood, and what should the person do next? Documenting the reason allows another team to apply the rule rather than copying the appearance without understanding it. Include real text instead of approving a layout made entirely from placeholders.
- Readability: Check actual wording at several sizes and with sufficient contrast. Information should not depend on colour or a tiny symbol alone. Where an illustration conveys a process, provide a useful textual explanation alongside it.
- States: Prepare empty, failure, loading and disabled examples when relevant. Interactive controls need a visible keyboard focus and an understandable name. Show what happens after a person makes a choice, not just what the screen looks like before interaction.
- Delivery: Share editable sources, usage rules and a version note. Assign responsibility for differences between design and implementation. Keep permitted variants explicit so future content production remains consistent without requiring a designer to approve every routine change.
Further reading
w3.org — WCAG22 / quickrefLet’s bring this idea to your product.
Define your project goals and technical needs with us.
Let’s talk about your project


