What to ask about accessibility before you sign with a web designer
Asking to see a site they built that a keyboard can get through
"I love the mockups, when do we start" is usually said well before anyone brings up accessibility. By the time it comes up later, it's already more expensive to fix than it would have been to build right the first time.
Before signing anything, ask to see a live site the designer has already built. Actually try navigating it with a keyboard. Don't just take their word for it.
Tab through it the same way you'd test your own. Can you reach every link and button? Does a visible focus marker follow you around the page? Does a form make sense without ever touching a mouse? A designer who's done this work before will have an answer ready and a real site to point to. One who hasn't will talk around the question.
Ask which standard they build against, by name. There's a widely used technical standard for this, and a designer who works to it regularly will say so without hesitating. One who's never heard the term is telling you something too.
An accessibility line in the scope versus a promise in an email
A verbal reassurance that "we always build accessible sites" is worth exactly as much as the paper it's not written on. Nice to hear. Not enforceable.
What matters is whether accessibility appears as a specific line item in the written scope of work. Testing standards named. Deliverables described. Not a sentence in a sales email that nobody can point to once the project is underway.
If accessibility isn't in the scope document, it isn't part of what you're paying for. That holds regardless of what got said out loud during the pitch.
This isn't about distrust so much as ordinary project management. Scope documents exist precisely so nobody has to rely on memory six months later about what was promised in a phone call.
It also protects the designer, not just you. A written scope keeps both sides working from the same understanding of what's actually being delivered, instead of two different memories of the same conversation drifting further apart over the course of a project.
What the contract says about issues found after launch
Ask directly what happens if an accessibility problem turns up after the site goes live. During an accessibility audit. From a customer complaint. From a demand letter.
Does that fall under a warranty period already built into the contract? Or is it billed as new work the moment launch day passes? There's a real difference between those two answers.
There's no single right answer here, but there needs to be a clear one, written down, before you sign. A vague answer in this specific spot is one of the more telling moments in the whole vetting conversation.
Some designers offer a short warranty window on this kind of issue as standard practice. Others treat every request after launch as new billable work. Neither approach is wrong on its own, but you want to know which one you're agreeing to.
Responsibility for content the owner adds later
A site can be built correctly and still become inaccessible six months later. Through content the owner adds after launch. A photo with no description. A PDF uploaded without a second thought. A new page built with a page-builder tool that skips proper heading structure.
Ask who's responsible for that ongoing gap. The designer, for the tools they handed over. The owner, for what gets added later. Both answers are partly right.
The honest answer is usually some mix of both, but it should be spelled out rather than left as an assumption everyone quietly disagrees about months later.
A content style guide handed over at launch helps here, something short that says how to write alt text and structure a page, so the standard doesn't quietly erode with every new person who touches the site.
Training for whoever will be posting to the site
If someone on staff will be adding blog posts, uploading photos, or updating pages after launch, ask whether training is included. Training on doing that without breaking what was built in the first place.
Writing usable alt text. Structuring headings correctly. Formatting an accessible PDF. All of it is learnable in a short session, but only if someone actually teaches it.
Without that training, the accessible site handed over on launch day tends to erode gradually. One untrained content update at a time, until nobody can say when it stopped working.
Even a short written cheat sheet helps between formal sessions. A page or two covering the handful of habits that matter most goes a long way for someone who only updates the site occasionally and won't remember a training call from months back.
Answers that sound reassuring and commit to nothing
Some answers sound complete but commit to nothing specific. "We care deeply about accessibility" describes a feeling, not a deliverable. "We can add a widget for that" is worth a second look, since whether those widgets hold up the way they're marketed is a genuinely open question rather than a settled fix. "Nobody's ever complained" describes an absence of evidence, not a working site.
The stronger version of each answer names something specific. A standard they test against. A page they can show you. A line in the contract you can point back to later.
That same instinct, press for specifics instead of a warm feeling, applies to the wider process of vetting who builds your site, and to figuring out who's responsible for the site once it's actually live. Accessibility is one piece of the fuller picture of accessibility for a small business site.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go