What to Ask for in a Website Accessibility Review
A website review can produce a long list of warnings without making the next step clear. For the team commissioning the work, the useful questions are practical: which people and tasks were considered, what prevents them from progressing, who can correct it, and how will we know the correction works?
Agree the review before comparing the score
Two reports may cover different pages, states and methods. Ask for a defined scope and an evidence record before treating their results as comparable. Accessibility work becomes more manageable when each finding connects a user difficulty to a reproducible test and an owner.
A current framework, not a new compliance badge
The Accessibility Guidelines Working Group published WCAG-EM 2.0 as a W3C Group Note on 23 July 2026. It provides an evaluation method for digital products, building on the earlier website-focused methodology. It does not replace WCAG or add new WCAG requirements. For a buyer, its value is a clearer discussion of scope, sampling, evaluation and reporting.
1. Say what the review is meant to answer
A quick review to identify obvious obstacles, a focused check of an enquiry form and a formal conformance evaluation are different assignments. Name the purpose in the brief. Agree the standard and target level where relevant, the site version, included languages and the technologies or user environments to consider. Ask which expertise is needed and which conclusions the chosen scope can support.
For example, “review our Japanese and English contact journeys before release” is more actionable than “check accessibility”. It gives the team a shared starting point while leaving room to define the detailed tests.
2. Include the states people actually encounter
A list of URLs is a useful start, but the same page can behave differently after a menu opens, a form fails validation or a message appears. W3C’s methodology includes representative samples and complete processes. A visitor needs to finish the task, not only reach a correctly structured first screen.
| Journey | States worth including |
|---|---|
| Finding a service | Desktop and mobile navigation, expanded menus, keyboard focus and the destination page. |
| Sending an enquiry | Labels, instructions, errors, corrected input and the confirmation state, using an agreed test route. |
| Reading in another language | Language selection, headings, links and any downloadable or embedded information needed for the task. |
| Using different display settings | Text enlargement, narrow layouts, light/dark themes and motion preferences where the site offers them. |
Include third-party booking, payment or application steps when they are part of the agreed journey. Identify which provider controls them. A handoff outside the main domain should be visible in the scope rather than quietly disappearing from the report.
3. Ask how automated and human checks fit together
Automated tools can help find repeatable issues, but a clean result is not a complete accessibility assessment. W3C’s evaluation overview explicitly calls for knowledgeable human evaluation. Ask what will be tested manually, how keyboard use and assistive technology will be considered, and how uncertain findings will be resolved.
Where user evaluation is included, agree suitable participants and tasks. W3C explains that involving people with disabilities adds an important perspective alongside standards-based evaluation. One participant’s successful experience should not be presented as representing everyone.
4. Request findings the implementation team can use
A useful finding should make the problem reproducible. Ask for the page and state, the steps taken, expected and observed behaviour, and the user impact. Screenshots or a short recording may help, but text should explain the issue too. Include the relevant criterion when the finding is part of a standards-based assessment.
Then separate the decisions. A missing label in a shared form component may need a template fix; an unclear link may need editorial review; an inaccessible external tool may require a supplier conversation. Record both the issue’s significance and the work needed to resolve it, rather than assuming that the longest technical task always matters most.
5. Plan retesting and ongoing ownership
Agree who implements each change and who checks it afterwards. Retest the original steps and any shared components affected by the correction. Keep unresolved findings visible with their reason, owner and next action. A report marked “delivered” does not mean every problem has been resolved.
For a bilingual site, include both language versions when a shared component changes. For ongoing publishing, give editors examples of useful headings, meaningful link labels and image descriptions. That helps keep later updates aligned with the decisions made during the review.
What a usable handover contains
- The scope, dates, site version, languages and methods.
- Tested pages, important states and complete tasks.
- Evidence and steps for each finding.
- Responsibilities across design, development, content and suppliers.
- Retest results and clearly identified unresolved work.
- The limits of any conclusion or conformance statement.
PLAN FOR REAL USE
Make usability part of the website brief from the beginning.
Clickmark can help clarify important visitor journeys and incorporate practical improvements into website design and ongoing work. Where a specialist evaluation is required, its scope, expertise and responsibilities should be agreed explicitly.
For continued work after release, see website support and maintenance.
Review date and scope
Reviewed 16 November 2026. This is guidance for preparing a review brief, not an accessibility certification, legal assessment or claim that a particular website conforms to a standard.