Website accessibility basics for local businesses

Most website audits stop at speed, mobile usability and whether the SSL certificate is valid. Website accessibility basics for local businesses rarely make it onto that list, not because they don't matter, but because they are less visible: a slow homepage announces itself within a few seconds, while a form a screen reader cannot fill in, or text a colour-blind visitor cannot read against its background, only shows up if you know to look for it. For a freelance web designer building out an audit process, accessibility is worth adding, both because it is the right thing to check and because most local business sites have never had anyone check it.

What accessibility means for a small business site

Accessibility does not mean a full legal audit against every clause of WCAG. For a local plumber's site or a village hairdresser's booking page, it means something much more practical: can someone using a screen reader work out what the business does and how to contact it, can someone with limited colour vision read the text against its background, and can someone navigating by keyboard alone, rather than a mouse, actually reach the booking button. These are usability questions before they are compliance questions, and they affect more visitors than most business owners assume, not just the small minority who use assistive technology day to day, but anyone browsing in bright sunlight, on an older phone, or one-handed while doing something else.

An accessibility audit checklist worth actually running

A handful of checks cover most of what goes wrong on a typical small business site, and none of them need specialist tools. Alt text on images is the most common gap: product photos, team headshots and hero images that a screen reader either skips entirely or reads out as a meaningless filename. Colour contrast is the next most common, usually light grey body text on a white background, or a call-to-action button in a brand colour that looks fine to the person who chose it and is nearly unreadable to plenty of visitors. After that, check whether every form field has a proper label rather than just placeholder text that disappears the moment someone starts typing, whether the page can be navigated using only the Tab key, and whether headings follow a sensible order rather than jumping from an h1 straight to an h4 because it happened to look right at the time.

Where these problems tend to hide

Site builders make some of this worse rather than better. A template that looks polished out of the box often has contrast issues baked into the theme itself, decorative images with no alt text field exposed to the person editing the site, or a booking widget embedded from a third party that was never built with keyboard navigation in mind. This is one of the reasons working out what a website is built on before you quote is useful beyond pricing: it tells you roughly which accessibility problems you are likely to find before you have even opened the page properly.

Pitching accessibility without leaning on scare tactics

The UK's Equality Act 2010 does require service providers to make reasonable adjustments, and a website that is unusable for a disabled visitor is a live version of that question, but leading a pitch with legal risk tends to put business owners on the defensive rather than interested. A better opening is the same one that works for any other audit finding: specific and concrete. Telling someone their contact form has no labels so a screen reader user can't tell which box is the phone number lands better than a general warning about compliance. Frame it as a usability gap that is turning away customers who would otherwise book, the same way you would frame a slow homepage or a broken booking link, and it reads as care about their business rather than a sales tactic dressed up as a warning.

How much to actually fix

Not every accessibility issue needs solving before a site is in reasonable shape. Missing alt text and poor contrast are quick wins worth including in almost any project. Full keyboard navigation and screen reader testing across an entire site is a bigger piece of work, worth scoping separately and pricing accordingly rather than folding it silently into a fixed-price rebuild. Being upfront with a client about which fixes are quick and which are a proper piece of work is more useful to them than either ignoring the topic or treating every finding as equally urgent.

None of this needs specialist software to check for the first time. A pass through the checks above, run by hand on a handful of pages, tells you most of what matters on a typical small business site. Patchscout's audit runs alongside that manual check rather than replacing it: it flags speed, mobile usability, SSL and the site builder automatically, so the time you save there is time you can spend actually checking contrast and alt text on the sites worth pitching in the first place.

The three free searches at app.patchscout.co.uk/signup are enough to see whether narrowing your prospect list that way is worth doing before you start checking accessibility by hand.