Ask for accessibility evidence when buying a website
What to ask a web agency so you know what it tested, what it fixed, and what still needs attention before you sign off.
When a proposal says “accessible website,” ask for an example of what the agency will test. Can someone complete the contact form with a keyboard, correct a mistake, and confirm that it went through? A screenshot with a high score can’t answer that question.
Before hiring, agree on which pages and tasks the agency will check, which criteria it will use, and who will retest the fixes. That helps you compare proposals and review the delivery; it doesn’t determine legal compliance.
Put the target in the proposal
Agree on the WCAG version and conformance level being used for the project. Also identify the website sections, languages, documents, and third-party components included in the work.
A bilingual service site might include navigation, search results, service pages, and a request flow in both languages. If downloadable documents or an external booking tool are excluded, record that openly. An exclusion does not make the user’s difficulty disappear.
Ask who is responsible for evaluating supplied content. An accessible template can still receive a poorly structured article or an image without a useful alternative. Editorial responsibilities need to be part of the operating arrangement.
Request a method, not just a tool name
W3C’s WCAG evaluation methodology overview describes defining scope, exploring the site, selecting a representative sample, evaluating it, and reporting findings. Use that structure to ask what the supplier intends to examine.
The sample should reflect the actual site. A homepage alone cannot represent a multistep application, a document library, or an account area. Ask how shared components and complete user processes enter the evaluation.
For a fictional training provider’s site, a useful sample might cover finding a course, reading its requirements, selecting a session, and submitting an inquiry. Include error and confirmation states where they exist. The provider should explain the sample’s coverage and limits.
Distinguish automated checks from human evaluation
Automated tools can identify some issues efficiently. They cannot establish accessibility on their own. W3C’s guidance on selecting evaluation tools explains that knowledgeable human evaluation is needed alongside tools.
Request the planned manual checks, including keyboard interaction and relevant assistive technology testing. Ask which browser and technology combinations will be used. A generic promise to “test screen readers” leaves too much unspecified.
User research with disabled participants can reveal practical barriers, but it should not be presented as a substitute for evaluating the agreed criteria. The methods answer related questions and can inform each other.
Make findings actionable
A useful finding identifies the affected page or component, observed behavior, relevant criterion, reproduction steps, and expected correction. It should be possible for a developer to reproduce it without attending the original review.
Require status tracking. Separate fixed and retested issues from issues merely marked fixed. Record remaining failures and their impact so the buyer can make an informed acceptance decision.
Place this evidence in the web development deliverables. When several suppliers contribute, name who coordinates corrections across templates, content, and external tools. Otherwise each party may assume the problem belongs elsewhere.
Plan what happens after the review
Accessibility can change when editors publish new content or developers alter shared controls. Ask which checks will repeat after significant changes and who maintains the remaining-issues list.
For a small site, that may mean a documented content review and regression checks on important interactions. For a larger product, the process may be broader. Match the arrangement to the site’s actual change patterns.
When it’s time to sign off, start with what the report leaves out. Then pick one task that matters, such as submitting the contact form, and ask the team to show you how it retested the fix.
Have a project in mind?
Get in TouchMore Articles
Set Q4 digital priorities from the work people cannot finish
Build a short Q4 roadmap from blocked customer and staff tasks, with evidence, dependencies, acceptance checks, and explicit reasons to defer work.
Read
How to review a web agency portfolio before choosing a partner
Use an agency portfolio to examine relevant work, precise project scope, live user tasks, and evidence limits instead of judging only presentation.
Read
E-commerce product content: useful detail and accessible choices
Make product details and variant choices understandable with specific descriptions, meaningful images, named options, and visible availability states.
Read