Website Accessibility for Small Business: A Practical Guide

Accessibility means people can use your website regardless of how they see, hear, move, or process information. That covers someone who is blind and uses a screen reader, someone with low vision who zooms to 200 percent, someone with a tremor who uses a keyboard instead of a mouse, and someone colour blind who can't tell your red error message from your green one.

It also helps people who would never call themselves disabled. The builder reading your site in harsh sunlight on a cracked phone. The parent scrolling one-thumbed with a toddler on their hip.

The small business version is simpler. Can any reasonable visitor find out what you do, decide to trust you, and get in touch without hitting a wall? If the honest answer is "mostly, unless they can't use a mouse", there's work to do.

The compliance angle gets the headlines. The commercial angle is where the money is. Every barrier on your site removes a slice of potential customers before they reach your contact form. And the web is full of barriers. In its 2026 report, the WebAIM Million scan of the top one million home pages found an average of 56.1 detectable accessibility errors per page, with low contrast text on 83.9 percent of them. And software only catches some errors.

The useful part: most accessibility fixes improve the site for everyone.

• Readable contrast helps every visitor on a phone outdoors.
• Clear headings help skimmers, screen reader users, and search engines understand the page.
• Labelled form fields reduce errors and abandoned enquiries.
• Bigger tap targets stop fat-thumb mistakes on mobile.

That's why accessibility and conversion overlap so much. Half of the signs your website is costing you customers are accessibility problems wearing a different hat.

This is general information, not legal advice. If you've received a complaint or demand letter, talk to a lawyer in your country.

• New Zealand: The Human Rights Act 1993 makes it unlawful to discriminate on the grounds of disability when providing goods and services. Government agencies must meet the NZ Government Web Accessibility Standard. Private businesses have no specific website rule, but the general principle applies.
• Australia: The Disability Discrimination Act 1992 covers goods and services, and WCAG is the benchmark usually referred to.
• United States: The Department of Justice's guidance on web accessibility and the ADA says businesses open to the public need accessible websites. Lawsuits are common, and small businesses are regularly targeted.
• United Kingdom: The Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, which can include your website.
• European Union: The European Accessibility Act has applied since 28 June 2025 to many consumer-facing digital services, including online shops. Microenterprises providing services are generally exempt, but check if you sell into Europe.

The common thread: nobody is grading you on perfection, but when a standard gets mentioned, it's almost always WCAG Level AA. That makes it the sensible target whether you're in Napier or New York.

WCAG stands for Web Content Accessibility Guidelines. It's published by the W3C, the body that maintains web standards, and the official WCAG overview is the place to start if you want the source. The current version is WCAG 2.2, published in October 2023.

The whole thing hangs on four principles, usually shortened to POUR:

1. Perceivable: people can see or hear the content. Think alt text, captions, and enough contrast.
2. Operable: people can use it. Keyboard access, enough time, nothing that flashes dangerously.
3. Understandable: the content and controls make sense. Clear labels, predictable behaviour, helpful error messages.
4. The final R: it works with assistive technology, like screen readers, because the code is built properly.

Each guideline has success criteria at three levels. A is the bare minimum, AA is the realistic target most laws point to, and AAA isn't expected for whole sites.

A few AA numbers worth remembering: normal text needs a contrast ratio of at least 4.5:1 against its background, and large text needs 3:1. WCAG 2.2 also added a minimum target size of 24 by 24 CSS pixels for things people tap or click, and a rule that keyboard focus shouldn't be hidden behind sticky headers or cookie banners.

The good news is that the same handful of issues turns up again and again.

None of these are exotic. They're small design decisions made without asking who might struggle, and small decisions are cheap to reverse.

You don't need a specialist to find the obvious problems. Open your site on a laptop and your phone and work through this.

1. The keyboard test (5 minutes). Put the mouse aside. Press Tab to move through your homepage and contact page. Can you always see where you are? Can you open the menu, reach the contact button, fill in the form, and submit it? If you get stuck or lose track, so does everyone who relies on a keyboard.
2. The zoom test (3 minutes). Zoom your browser to 200 percent. Does the text reflow, or do things overlap, get cut off, or force sideways scrolling?
3. The automated scan (5 minutes). Run a free checker such as WebAIM's WAVE tool or Lighthouse, which is built into Chrome's developer tools. It won't catch everything, but it finds contrast, alt text, and label problems fast.
4. The image check (5 minutes). For every important image, ask: if this picture disappeared, what would someone need to know? That's your alt text. Purely decorative images should have empty alt text so screen readers skip them.
5. The form check (5 minutes). Submit your contact form with mistakes on purpose. Does it tell you clearly what went wrong and where, in words, not just colour?
6. The screen reader taste test (7 minutes). Turn on VoiceOver on an iPhone, or try NVDA, which is free on Windows. Swipe through your homepage. It feels awkward at first. Listen for whether the page makes sense read aloud in order.

If your site fails three or more of those, it's probably costing you enquiries already, regardless of the legal side. Our guide to conversion rate optimisation for small business covers the overlapping fixes from the sales angle.

Don't fix everything at once. Start with whatever stands between a visitor and an enquiry.

Forms come first for a reason. A contact form that a screen reader can't make sense of is a closed door with your phone number painted on it. For patterns that work, our roundup of contact page examples shows forms that are clear for everyone.

A note on mobile: zoom and tap target problems usually trace back to how the site was built rather than what's on it. If your site was designed desktop-first and squeezed onto phones later, our guide to responsive web design services explains why that matters.

You've probably seen the little accessibility icon in the corner of some websites. Some of these tools are sold on the promise that one line of code makes your site compliant.

Tempting pitch. Not how accessibility works.

An overlay sits on top of your website. Accessibility lives inside it. If the form has no labels and the menu traps the keyboard, a toolbar in the corner doesn't change the code underneath.

Many accessibility practitioners and disabled users are openly critical of overlays, partly because they can interfere with the assistive tools people already use. Installing one doesn't make a site conform to WCAG, and it shouldn't be treated as a legal shield.

A preference toolbar on an already well-built site is harmless. Using one instead of fixing the basics is like putting a ramp sticker on a staircase.

This is the question everyone actually wants answered. Prices vary with site size, platform, and review depth, so treat these as typical ranges, not quotes.

That last row is the important one. Accessibility is cheapest when it's a design habit, not a repair job. An accessible colour palette costs nothing at the mockup stage. Changing it after launch means reworking buttons, banners, and brand assets everywhere.

Cheap websites aren't automatically inaccessible. But a cheap build where nobody checked these details often becomes an expensive one later.

Most owners don't need to bin their site. But sometimes the fixes cost more than they're worth.

Leaning towards the second list? Our website redesign cost and timeline guide walks through what a rebuild involves and how to protect your search rankings along the way. Briefing someone new? Our list of questions to ask a web designer is a good start. Add "which WCAG level do you build to?" A vague answer tells you plenty.

We treat accessibility the same way we treat conversion: as part of the build, not a bolt-on at the end. Both are about removing reasons for a visitor to give up.

The honest note: we're a young studio, and we won't claim a site is formally WCAG-certified without a specialist audit behind it. What we will do is build with the standard as the target and test the things that matter most to real visitors.

If you want to know where your current site stands, get a free website audit. We'll flag accessibility problems alongside the clarity and conversion issues, ranked by what to fix first. If you're planning a new build, our services and packages page shows what each tier includes, and our concept demos show the standard we work to. They're concept builds, labelled as such, not client sites.

Website accessibility for small business comes down to one habit: making sure every visitor can read your page, find your button, and send you an enquiry. Treat it as a box to tick once and it'll quietly drift out of date.

Start with the 30-minute check. Fix forms, contrast, and keyboard access first. Skip the magic widget. Building something new? Put accessibility in the brief, where it costs almost nothing.

The best website is the one that helps the right customer trust you faster. That includes the customer using a screen reader, the one zoomed to 200 percent, and the one squinting at their phone in a car park. If you'd like a second pair of eyes, send us your site for a free audit and we'll show you what to fix first.