Website accessibility means a site works for visitors using screen readers, keyboard navigation, or who have low vision or color blindness — and a handful of basic practices (contrast, alt text, keyboard-navigable menus, readable font sizes) cover most of what a small business site needs without requiring a formal accessibility audit. Skipping these isn't just an ethical gap; it's a real business and legal risk you're handing your client without them knowing it.
Accessibility gets treated as an optional, advanced topic by a lot of freelancers, mostly because full WCAG compliance sounds like a specialist undertaking. The basics aren't. Most of what actually matters for a small business site is a short list of habits that add almost no time to a build when they're part of your default process from the start.
Why This Is a Business Risk for Your Client, Not Just a Nice-to-Have
Website accessibility lawsuits against small and mid-sized businesses have become common enough that it's a real exposure, not a hypothetical one — plenty of businesses with fewer than 10 employees have received demand letters over inaccessible websites. A client who hired you assuming a professional build would obviously be usable has no way to know it isn't, until a complaint or letter arrives. At that point, the accessibility gap becomes your reputation problem too, since you're the one who built it.
Beyond legal exposure, there's a direct commercial case: an estimated 1 in 4 adults has some form of disability. A site that's hard to use for a meaningful share of visitors is a site that's quietly turning away customers your client is paying you to attract.
The Practical Basics (No Specialist Audit Required)
| Area | What to do | |---|---| | Color contrast | Body text should meet at least a 4.5:1 contrast ratio against its background; check with a free contrast checker tool | | Alt text on images | Every meaningful image needs a short, descriptive alt attribute — decorative images can have empty alt text, but never skip it entirely | | Keyboard navigation | Every interactive element (menu, form, button) should be reachable and usable with Tab and Enter alone — test this by unplugging your mouse for five minutes | | Font size and line height | Body text at minimum 16px, with enough line spacing to avoid a cramped, hard-to-scan block | | Form labels | Every input needs a visible, associated label — not just placeholder text that disappears once someone starts typing | | Heading structure | Use headings (H1, H2, H3) in logical order to convey structure, not just for visual size | | Focus states | Buttons and links should show a visible outline or highlight when tabbed to, not just on mouse hover | | Video/audio content | Captions or a transcript for anything with spoken content |
None of these require an accessibility specialist. They require building them in as defaults rather than an afterthought — most take seconds per element when done as you build, and hours to retrofit later.
A Five-Minute Accessibility Spot-Check
Before delivery, run this alongside your regular QA checklist:
- [ ] Tab through the entire site using only the keyboard — can you reach and activate everything?
- [ ] Run a free contrast checker on your main text and button colors
- [ ] Confirm every image has alt text (spot-check a sample if the site is large)
- [ ] Zoom the browser to 200% — does the layout still work, or does content overlap/disappear?
- [ ] Check that form fields have real labels, not just placeholder text
This isn't a substitute for a full accessibility audit on a site that needs formal compliance (larger businesses, certain regulated industries), but it closes the majority of the gap for a typical small business site, and it costs you almost nothing in build time when it's habitual.
Turning Accessibility Into a Selling Point
Most competing freelancers never mention accessibility at all, which makes it a genuine differentiator when you do — especially with clients in regulated or risk-conscious industries (healthcare, finance, professional services, government-adjacent work) where accessibility exposure is a real, named concern for the business owner. Framing it plainly in a pitch or proposal — "I build every site with basic accessibility practices in place by default, which reduces your legal exposure and reaches more of your potential customers" — is a specific, credible claim that few competitors are making.
Where This Fits in the Framework
Accessibility sits alongside speed, mobile experience, and visual polish as a delivery-quality dimension most freelancers skip, not because it's hard, but because no one taught them it belongs in the default build process. This follows how long it should take to build a small business website — accessibility basics fit inside a realistic timeline as a default habit, not an extra phase. Next: website mistakes that make a business look untrustworthy, which covers the trust-signal side of the same broader problem. For the full framework, see how to build websites that win and keep clients.
Accessibility Fits a Bigger Career Move, Too
Building accessibility fluency is also a credible way to grow beyond solo freelance work — clients with real accessibility risk (larger local chains, healthcare, professional services) tend to have bigger budgets and longer engagements, which connects to how to scale from solo freelancer to agency as your client base shifts toward more risk-aware, higher-value businesses.
Runvax: Finding the Clients Who Value This Most
Accessibility-conscious clients — healthcare practices, professional services, anything with real legal exposure — are often businesses that also lack a proper website in the first place. Runvax finds local businesses without a website in any city and category, so you can target exactly these higher-value prospects and lead with a pitch that goes beyond looks.