Website Accessibility for a Small Business
AI-generated sites usually get headings and labels right and get contrast, focus and link text wrong. Seven checks, in the order worth doing them.
Most small business websites fail accessibility on the same seven things, and all seven can be checked in an afternoon without buying anything. If an AI tool built your site, the picture is usually mixed: generated markup tends to get headings and labels right and gets colour contrast, focus visibility and link text wrong, because those three depend on design choices nobody told it about.
This is the shortlist, the order to work through it, and what to do about each one.
Why bother, in plain terms
Accessibility work is usually sold on compliance, which is the least motivating version of the argument. Three better reasons for a business with no legal department:
A share of your visitors cannot use a site that depends on seeing a colour, hovering a mouse, or reading small grey text. That share grows with the age of your customer base, and for most local businesses the customer base is older than the person who built the site.
Several of the fixes improve the site for everyone. Larger text, real contrast and a visible focus outline help in sunlight, on a cracked phone screen and at the end of a long day.
The checks overlap heavily with technical hygiene a search engine also reads. A page title, a declared language and a sensible heading structure are accessibility items and they are also the basic things a crawler needs, which makes this one of the few jobs that pays twice.
The seven checks
The W3C Web Accessibility Initiative publishes a set of easy checks anyone can run. There are thirteen in the full set. These seven are the ones that apply to almost every small business site and that you can act on alone.
1. Page title
Every page needs a title that describes that page, not the site. "Contact" is worse than "Contact Riverside Dental, Bristol". The title appears in the browser tab and is the first thing a screen reader announces, which makes a page full of identical titles genuinely disorienting. On an AI-built site, check whether every route actually got its own title rather than inheriting one from a template.
2. Image alternative text
Every image that carries meaning needs a short description of its purpose. Decorative images get an empty alt attribute so assistive technology skips them, which is a real answer and not a cop-out. The common failure on generated sites is a filename in the alt attribute, or the same generic phrase on every photo.
The test: read the page aloud with the images replaced by their alt text. If a sentence stops making sense, that alt text is wrong.
3. Headings
Headings should show the structure of the content. One main heading per page, then sections beneath it, in order, with no levels skipped. Screen reader users navigate by jumping between headings, so a page where the headings are chosen for their font size rather than their rank is a page they cannot skim.
4. Colour contrast
Text, interactive elements and the meaningful parts of charts all have to stand out enough from their background. This is where generated designs fail most often, because light grey on white looks modern in a mockup and disappears on a phone outdoors. Browser developer tools report a contrast ratio for any selected text, and that number is the answer.
While you are there, check that you are not using colour alone to convey anything. A required field marked only in red, or a status shown only by a green dot, carries no information for a visitor who cannot distinguish them.
5. Visible keyboard focus
Press Tab repeatedly from the top of the page. You should always be able to see where you are. If the outline disappears, somebody removed the default focus style in CSS without replacing it, which is one of the most common single lines of damage in a generated stylesheet. Check the whole journey, including inside any form and any dropdown menu.
6. Form labels and required fields
Every field needs visible text saying what to enter, properly associated with the field rather than just sitting near it. Placeholder text is not a label: it vanishes the moment someone types. And fields that are required should be marked as required before submission, not only in the error message afterwards.
For a small business this usually means one form, the contact or booking form, and it is the single highest-value thing on the list because it is the page that makes you money.
7. Zoom
Enlarge the page to 200 percent in the browser and use it. Text should reflow and stay readable, nothing should overlap, and no content should be cut off. Fixed-height containers and absolutely positioned elements are what break this, and both are common in generated layouts.
Where the WCAG principles fit
The underlying standard organises everything around four principles, summarised in WCAG at a glance: content must be perceivable, operable, understandable and robust. Perceivable covers text alternatives and being able to see and hear content. Operable covers keyboard access, enough time, avoiding content that causes seizures, and navigation. Understandable covers readable text, predictable behaviour and helping people avoid and correct mistakes. Robust covers compatibility with current and future user tools.
The seven checks above are a subset. They are not a conformance claim, and the WAI page says so directly: these checks are quick and not exhaustive, so a page that passes them may still have barriers.
What automated tools catch, and what they miss
Tool finds reliably | Needs a human |
|---|---|
Missing alt attributes | Whether the alt text is accurate |
Contrast ratios below a threshold | Whether colour alone carries meaning |
Missing form labels | Whether the label makes sense to a stranger |
Skipped heading levels | Whether the heading describes the section |
Missing page language | Whether the reading order is logical |
Missing page title | Whether the title distinguishes this page |
Run an automated checker, by all means. A browser extension or a built-in audit in developer tools takes two minutes and will find the mechanical failures. Then do the keyboard pass and the zoom pass yourself, because no tool reports that your focus outline is invisible on a dark section or that your checkout breaks at 200 percent.
Getting an AI tool to help without making it worse
AI is good at the generation half of this and poor at the judgement half. What works:
Ask it to add alt text, then rewrite every one it produces. It can see the file name and your page copy, not the photograph.
Ask it to find every place in your CSS where an outline or focus style is removed. That is a mechanical search and it is good at mechanical searches.
Ask it for the contrast ratio of a specific colour pair and the nearest compliant alternative, then confirm the number in developer tools.
Do not ask it whether your site is accessible. It will tell you about the code it can read, which is not the same question.
If an agent is writing the markup in the first place, giving it accessibility requirements up front is cheaper than retrofitting, which we covered in getting an AI coding agent to write accessible code.
Frequently asked questions
How long does this take on a small site?
For a five-page site, two to three hours for the audit and a day for the fixes, most of which is contrast and focus styling. The form is usually the longest single item, and it is also the one worth testing with a real person who was not involved in building it.
Do I need an accessibility statement?
It is good practice and in some contexts expected, particularly if you sell to the public sector. A short honest page saying what you have done, what is known to be imperfect and how to contact you about a barrier is worth more than a generated statement claiming full conformance.
Does this apply to a site an AI builder made for me?
Yes, and arguably more, because the generated design made the colour and focus decisions without being asked about either. The markup is usually a decent starting point. The styling is where the work is. If you are at the planning stage, how to build an app with AI covers the wider process these checks sit inside.
Will an overlay widget fix this?
No. A floating accessibility widget does not repair the underlying markup, and the people who rely on assistive technology are consistently the ones least enthusiastic about them. Spend the money on the seven checks instead.
Is this a legal requirement for a small business?
It depends entirely on where you are and what you sell, and it has been getting stricter rather than looser in most places. Treat the question as one for a local adviser and the checks above as worth doing regardless of the answer.
Two adjacent jobs worth doing in the same afternoon: making sure the contact form actually reaches you, and making sure the replies that go back out are yours rather than a template, which we covered in responding to customer reviews with AI without sounding fake.
For the wider view of where AI genuinely helps a small business, see AI for small business: what actually works.
How did this land?
About the author

Growth & SEO Lead
Manuele covers distribution: SEO, content strategy, and how AI-built products find their first thousand users. He tests everything he recommends.


