Most small business owners meet accessibility for the first time through a letter from a law firm. That is a bad introduction, because it makes the subject feel like a legal trap rather than what it mostly is: a set of ordinary build decisions that a competent site gets right anyway.
Here is the honest version, without the scare tactics and without the shrug.
What the rules actually say
There is no single federal regulation that spells out what a private business website must do. The Americans with Disabilities Act predates the web, and the Department of Justice has taken the position that it applies to businesses open to the public, without publishing a technical standard for them. In 2024 the DOJ did set a standard for state and local government sites, naming WCAG 2.1 Level AA. That rule does not bind your shop, but it made WCAG 2.1 AA the number everyone now points at.
So the practical standard is WCAG 2.1 AA. Not because a statute names it for you, but because it is what a court, an insurer, and an opposing lawyer will all reach for.
Two things follow. First, nobody can sell you a certificate that makes you immune. Second, the gap between a site that has had a serious afternoon of attention and one that has had none is enormous, and it is the second kind that attracts letters.
The short list that covers most of it
A handful of problems account for the overwhelming majority of real failures. Automated scans find them, screen reader users hit them immediately, and demand letters cite them.
Contrast. Light gray text on white is the single most common failure on small business sites. Body text needs a contrast ratio of at least 4.5 to 1 against its background, and large text at least 3 to 1. That pale gray your designer liked is probably around 2.8. This is a one-line change per color and it fixes a genuine readability problem for everyone over about fifty.
Text on images. A headline sitting directly on a photograph almost never passes, because the contrast changes across the image. Put a solid or tinted panel behind the text.
Alt text. Every image that carries information needs a short description. Every image that is purely decorative needs an empty alt attribute, not a missing one and not a filename. A photo of your storefront next to a heading that already says your name does not need to repeat it.
Keyboard access. Unplug your mouse. Press Tab repeatedly. You should be able to reach every link, button, and form field, you should always be able to see where you are, and you should never get stuck. Menus that only open on hover and popups that trap focus are the usual offenders.
Form labels. Every field needs a real label element tied to it. Placeholder text inside the box is not a label. It disappears the moment someone types, and screen readers treat it inconsistently.
Headings in order. One h1 per page, then h2 for sections, then h3 beneath those. Screen reader users navigate by heading the way sighted users skim. Skipping from h1 to h4 because it looked better is a navigation problem, not a styling one.
Link text that means something. “Click here” and “read more” are useless out of context, and out of context is exactly how they get read aloud. “Read our hosting plans” costs nothing extra.
Video captions. If you publish video with speech, it needs captions. Auto-generated captions cleaned up by hand are fine.
That list is not the whole of WCAG. It is the part that fails most often and matters most to the people affected.
Why overlay widgets are the wrong answer
You will be offered a script that promises to make your site compliant overnight for a monthly fee. A little icon appears in the corner, opens a panel with contrast and font size controls, and the vendor sends you a certificate.
Do not buy it, for three reasons.
They do not fix the underlying markup. The alt text is still missing, the headings are still out of order, and the form still has no labels. The widget layers a second interface on top of a broken one.
Screen reader users largely dislike them. People who rely on assistive technology already have it configured the way they want. A script that overrides it makes things worse, which is why disability advocacy groups have campaigned against these tools rather than for them.
They have not reliably prevented lawsuits. Plaintiffs have named sites running overlays, and the widget is sometimes cited as evidence that the owner knew there was a problem and papered over it.
The money is better spent fixing the eight things in the list above, once, permanently.
How to check your own site in an hour
Run an automated scan. Free browser extensions like axe DevTools or WAVE will find contrast failures, missing alt text, and unlabelled fields in seconds. Understand the limit: automated tools catch roughly a third of real issues. A clean scan is a floor, not a pass.
Do the keyboard walk. Tab through your homepage, your contact page, and whatever page takes an order or a booking. Those three carry most of your risk, because they are where someone is actually trying to do business with you.
Turn on the screen reader you already own. VoiceOver is built into every Mac and iPhone. Narrator is built into Windows. Listen to your homepage for two minutes. It is uncomfortable the first time and it teaches you more than any report.
Zoom to 200 percent. Press Ctrl and plus, or Command and plus, until the page is at double size. Text should reflow and stay readable. Nothing should be cut off or overlap.
What this is really about
Somewhere between one in four and one in five American adults reports a disability. Not all of those affect web use, but a lot do, and the number climbs steeply with age. If your customers skew older, which they do for most trades, home services, healthcare, and financial work, the share of your audience struggling with 13 pixel gray text is not small.
Every fix on the list above also helps someone with no disability at all. Better contrast helps a phone screen in a parking lot at noon. Real form labels help people filling in a booking with one thumb. Sensible heading order helps everyone who skims, which is everyone.
The legal risk is real and it is worth taking seriously. It is just not the best reason to do any of this.
Where to start
If you do nothing else, fix contrast, add real labels to your contact form, and Tab through the page that makes you money. That is an afternoon, it removes the most commonly cited problems, and it makes the site measurably better to use.
If you are having a site built, put WCAG 2.1 AA in the scope in writing before anyone starts designing. Retrofitting accessibility into a finished design costs several times what building it in costs, mostly because the color palette and the layout are the things that have to change.
