Web accessibility for small business websites: complete guide

Is your website actually usable by everyone who visits it—or are you unknowingly turning away customers who use screen readers, keyboards, or other assistive tech? Web accessibility for small business isn't just a legal box to tick; it's a revenue issue that most founders ignore until a lawsuit lands.

What web accessibility actually means

Web accessibility means your site works for everyone: people with vision loss, hearing loss, mobility disabilities, cognitive differences, or temporary limitations like a broken arm or poor lighting. In practice, it means your site must work with screen readers, keyboard navigation, voice control, and text resizing without breaking.

The WCAG 2.1 standard (Web Content Accessibility Guidelines) sets the bar. WCAG has three levels:

• A: basic compliance; rare to sue over, but noticeable barriers remain
• AA: the legal baseline most courts expect; covers colour contrast, alt text, form labels, heading hierarchy, keyboard access
• AAA: near-perfect; rarely enforced, expensive to achieve

For small business, WCAG AA is your target. It catches most common barriers without demanding perfection.

The confusion many owners have: accessibility isn't a feature you "add on." It's baked into how you structure your HTML, name your buttons, choose your colours, and test before launch. Retrofit accessibility later, and costs spike.

Why courts now expect compliance—and "undue hardship" isn't a defence

A few years ago, small businesses could claim "undue hardship" if accessibility would cost too much. That defence has collapsed in recent UK and US case law. Courts increasingly expect websites to meet WCAG AA regardless of business size, especially for service-based or e-commerce sites.

Why? Because tools and templates that meet WCAG are now cheaper and faster than ever. A freelancer or agency that doesn't build accessible sites from the start is choosing complexity, not suffering it. Judges notice.

In the UK, the Equality Act 2010 requires reasonable adjustments for disabled people. Websites count as public services under that law. A few settlements have already pushed small businesses to retrofit, sometimes at £5k–£20k depending on site complexity. Prevention is vastly cheaper: build it right the first time.

The practical risk: a single accessibility complaint letter from a legal firm (even a template one) costs you hundreds in legal fees to respond. A compliance audit audit will cost you £500–£2,000 depending on site size. An inaccessible site that gets sued costs you £10k–£50k+, plus reputational damage. The maths is straightforward.

Auditing your site: which barriers cost you the most customers

Most small businesses have no idea which accessibility problems actually hurt them. You might have poor colour contrast on your homepage (fixable in 2 hours) and inaccessible forms (fixable in 4 hours), but the forms are costing you 3× more lost customers because 10% of your visitors try to book via your form.

Start with a free automated scan using tools like WAVE, Axe, or Lighthouse (built into Chrome DevTools). These catch ~50% of issues in minutes and flag false positives. They won't catch everything, but they'll flag low-hanging fruit: missing alt text, poor colour contrast, unlabelled buttons.

Then do a manual keyboard audit: visit your site using only the Tab key. Can you reach every button, link, and form field? Can you tell where focus is? Can you submit forms? If you get stuck, so do keyboard users.

For a small business site (5–10 pages), a professional accessibility audit costs £400–£1,200. For a larger site (20+ pages), expect £1,500–£3,500. If you're planning a redesign, fold accessibility into the brief upfront; it's cheaper than retrofitting.

Prioritise by impact: form accessibility usually blocks more revenue than colour contrast. Video captions matter more for media companies than for plumbers. A healthcare site needs robust form labels and clear navigation; a portfolio site needs good image descriptions. Audit first, then rank barriers by how many visitors they touch.

What it actually costs to fix: DIY vs. hiring

If you've got a small site (under 5 pages) and basic barriers (missing alt text, poor contrast, unlabelled buttons), you can often fix 70% yourself in a weekend using free tools like Lighthouse and a checklist. Expect to spend 4–8 hours. Cost: £0 if you do it; £200–£600 if you hire a contractor for 2–3 days at junior rates.

If you've got medium complexity (7–15 pages, some forms, embedded media), a junior developer or accessibility specialist will charge £800–£2,000 to audit and remediate. That usually includes a written report, code fixes, and testing.

If you're hiring an agency or rebuilding your site, insist on WCAG AA built in from the start. You'll pay nothing extra—maybe 10–15% less than retrofitting, because the team won't need to unpick bad markup later. Sitewright builds WCAG AA compliance into every project without a separate "accessibility fee" because it's standard practice.

Subscription tool costs (if you use them):

• Axe DevTools Pro: £0–£40/mo (team plans)
• Accessibility Checker (browser plugin): Free–£10/mo
• Userway or similar overlay tools (see next section): £0–£50/mo
• Accessibility testing software (Deque, Siteimprove): £200–£1,000+/mo (overkill for small business)

For a solo founder or small team, a one-time £1,000 audit + DIY fixes saves you £5,000+ compared to full agency remediation.

Should you use accessibility overlay tools? (Spoiler: probably not as your main strategy)

"Accessibility overlay" tools (UserWay, AudioEye, etc.) are JavaScript widgets that inject features like text resizing, screen reader enhancement, or reading guides into your site. They're heavily marketed and look like a quick fix.

The honest take: overlays catch maybe 10–20% of accessibility barriers. They can't fix poor heading hierarchy, keyboard navigation, or form structure—that's baked into your HTML. Courts and accessibility auditors now view overlays as a band-aid that signals you didn't fix the underlying code. Some law firms explicitly exclude sites using overlays from settlement agreements because they know the barrier still exists.

Use an overlay if you're in a hard transition (e.g., you're rebuilding your site and need temporary coverage for 3 months) or as a supplement to real fixes, not instead of them. Don't market it to users or rely on it alone.

Most accessibility experts recommend: skip the overlay, fix the code, and spend the £30/mo on a human review or developer time instead.

Industry-specific barriers: where your site differs

A hairdressing or beauty salon site mostly needs a working booking form and clear contact info. Accessibility priority: form labels, focus management, mobile responsiveness. Cost to fix: low. A quick audit + one developer day.

An e-commerce or SaaS site (product listings, checkout, filtering) needs robust form controls, searchable content, and keyboard access to every interactive element. Accessibility priority: form validation messages, product filters, checkout flows. Cost: medium. Expect 3–5 developer days and testing.

A healthcare or financial-services site (forms, sensitive data, compliance) needs clear language, proper heading hierarchy, and robust form error handling because users are often stressed or in a hurry. Accessibility priority: forms, error messages, navigation clarity. Cost: medium to high, plus compliance review.

A portfolio or blog needs good image alt text, readable text contrast, and sensible heading hierarchy. Accessibility priority: images, typography, code blocks. Cost: low to medium.

The timeline also varies. A salon can often achieve WCAG AA in 1–2 weeks of contractor work. An e-commerce site might need 6–12 weeks if you're overhauling checkout and product filters. A healthcare provider should plan 8–16 weeks and budget for compliance review by a third party.

Managing accessibility during a redesign or CMS migration

This is where most small businesses slip up. You rebuild your site, migrate to a new CMS, and suddenly your old alt text is gone or your form labels are wired incorrectly. You've lost ground.

Before you redesign:

1. Audit your current site and document what works (alt text, heading structure, form labels, colour contrast).
2. Brief your designer or developer: "We need WCAG AA compliance baked in, not added later."
3. Get sign-off on a simple accessibility checklist (15–20 items) that the team will verify before launch.

During migration:

• Export your old alt text and image metadata before you delete anything.
• Test forms in the new CMS with keyboard-only navigation before you go live.
• Use the new CMS's built-in accessibility features (e.g., Strapi's semantic HTML options) rather than fighting them.
• Assign one person to "accessibility QA"—someone who will test the site weekly during build and flag issues early.

After launch:

• Run an accessibility audit within a week. Fix any regressions immediately while the team is still focused on the project.
• Keep a simple log of what you've tested and what's compliant.

A website redesign vs rebuild decision often hinges on accessibility too: if your old site is deeply inaccessible and tightly coupled to a legacy CMS, a full rebuild often costs less than patching both.

The revenue argument: why accessibility matters beyond compliance

You probably don't think of accessibility as a revenue lever, but it is. A site that's keyboard-accessible loads faster for everyone, not just keyboard users. Good heading hierarchy helps with SEO, not just screen readers. Readable colour contrast helps users on old monitors, phone screens in sunlight, and people with dyslexia—that's 15–20% of your traffic.

One consultant reported a 30% increase in form completions after improving form labelling and error messages. A healthcare provider saw a 20% jump in appointment bookings after fixing navigation clarity and reducing cognitive load. These aren't "accessibility" wins; they're user experience wins that accessibility standards happen to enforce.

If you're stuck justifying the cost to your team, ask: What percentage of my customers use their phone in sunlight, rush through forms on mobile, or struggle with unclear instructions? It's usually 20–40%. Accessibility improvements help all of them.

The risk-adjusted case is even simpler: fixing accessibility now costs £1,000–£3,000. Getting sued costs £10,000–£50,000+. There's no reason to gamble.

Start with a free audit using Lighthouse or WAVE, pick the top 5 barriers by user impact, and fix them. Most small business sites can hit WCAG AA compliance in 2–4 weeks and a budget under £2,000. Getting ahead of accessibility now protects your revenue, your reputation, and your sleep at night—and it's increasingly table stakes, not a nice-to-have.