Website Accessibility: What Small Businesses Actually Have to Do
Accessibility is treated as a legal panic or a nice-to-have, and it is neither. What the standard asks for, and the few fixes that cover most of it.
Two things are usually true at once: nobody selling you a website mentioned accessibility, and the first time you hear about it is somebody implying you are about to be sued.
The reality is calmer and more useful. Most of what matters is a short list of unglamorous fixes, most of them are cheap if done during a build and expensive if retrofitted, and a meaningful share of your customers benefit — not a theoretical minority.
Not legal advice. This is a plain-English summary of a technical standard and the general legal backdrop. If you have received a complaint or a demand letter, talk to a lawyer, not a web agency.
The Standard Everyone Means
When anyone says "accessible", they almost always mean WCAG — the Web Content Accessibility Guidelines — at level AA. Version 2.1 is the most commonly cited in regulation; 2.2 is the current version and adds a small number of criteria. Building to 2.2 AA covers 2.1 AA.
It is organized around four ideas, which are worth knowing because they explain every specific rule: content should be perceivable, operable, understandable and robust.
The Legal Backdrop, Briefly
In the United States, the Americans with Disabilities Act does not itself name WCAG for private businesses, but courts have widely applied Title III to business websites, and WCAG 2.1 AA has become the practical benchmark used in settlements. Separately, the Department of Justice has set WCAG 2.1 AA as the requirement for state and local government under Title II. Web accessibility lawsuits and demand letters against small businesses are common and mostly settle.
In Australia, the Disability Discrimination Act applies to the provision of goods and services including online, and WCAG AA is the standard referenced in government guidance.
The honest summary: no regulator is going to audit a small business unprompted, and the realistic risk is a complaint from a real person or an opportunistic demand letter. Both are cheaper to prevent than to answer.
The Fixes That Cover Most of It
1. Color Contrast
Body text needs a contrast ratio of at least 4.5:1 against its background; large text needs 3:1. Light gray on white is the single most common failure on small business sites, and it is usually a designer choosing elegance over legibility. It is also the easiest thing to test and fix.
2. Real Alt Text on Meaningful Images
Describe the purpose, not the file. "Completed bathroom renovation with walk-in shower" rather than "IMG_4821". Purely decorative images should have an empty alt attribute so screen readers skip them — an empty alt is correct, a missing one is not.
3. Everything Reachable with a Keyboard
Put your mouse aside and press Tab through your own site. You should be able to reach every link, button and form field, do everything a mouse can do, and always see where you are. If focus disappears, or a menu cannot be opened, that is a genuine barrier — and it is the same barrier for someone with a motor impairment and for anyone whose mouse has just died.
4. Labeled Form Fields
Every field needs a real <label>. Placeholder text is not a label: it vanishes when typing starts, and it is invisible to a screen reader in the way people assume it is not. This is also just better for everyone filling in a form on a phone.
5. Headings in Order
One h1, then h2, then h3 — no skipping levels for visual effect. Screen reader users navigate by heading the way sighted users skim, so a broken hierarchy removes the ability to skim at all.
6. Captions on Video
Required for anyone deaf or hard of hearing, and used by a far larger group watching without sound on a phone. Auto-captions corrected by hand are fine.
7. Do Not Rely on Color Alone
A red field border marking an error is invisible to a large share of color-blind users. Add text: "Please enter an email address."
Check Your Own Site This Afternoon
- Tab through it. Keyboard only, no mouse, front page to contact form. Note anywhere you get stuck or lose the focus outline.
- Zoom to 200%. In your browser, not on your phone. Text should reflow and remain readable, not overlap or get cut off.
- Run a free automated checker on your three most important pages. WAVE and Lighthouse both work in the browser.
- Turn images off and see whether the page still makes sense.
- Read your form in a screen reader. VoiceOver on a Mac or iPhone, Narrator on Windows. Ten minutes here is worth a great deal.
An important caveat: automated tools reliably catch perhaps a third of issues. They are excellent at contrast and missing alt attributes, and blind to whether your alt text is meaningful or your tab order is sane. A green score is a floor, not a pass.
A Word on Accessibility Overlays
The widgets that promise instant compliance for a monthly fee — a floating icon that adds a contrast toggle and a font-size slider — are widely criticized by disability advocates and by screen reader users themselves, who often find they interfere with the assistive technology they already use. Businesses using them have still received complaints. They do not repair the underlying markup, because they cannot.
Fix the site. It is cheaper over any reasonable horizon and it actually works.
Build It In, Do Not Bolt It On
Accessibility during a build costs close to nothing: it is choosing legible colors, writing real labels and using headings properly. Retrofitting the same site afterwards can be a substantial project, because the decisions are baked into the markup.
That is why every site we build is WCAG 2.2 AA as standard rather than an upsell — it is on our pricing page as an inclusion and in the list of things every engagement gets. It is also, less loftily, straightforward good business: excluding people from your website means excluding them from buying from you.
If you are weighing up whether your current site needs work or replacing, read what a website actually costs first — accessibility is rarely a reason to rebuild on its own, and is usually a reason to fix.
Common Questions
Does My Small Business Website Legally Need to Be Accessible?
In the United States, courts have widely applied ADA Title III to business websites and WCAG 2.1 AA has become the practical benchmark used in settlements, though the ADA does not name it directly for private businesses. In Australia, the Disability Discrimination Act covers goods and services provided online. No regulator audits small businesses unprompted; the realistic risk is a complaint from a real customer or a demand letter. This is a summary, not legal advice.
What Is WCAG 2.2 AA in Plain English?
A technical standard saying content should be perceivable, operable, understandable and robust. In practice, level AA means adequate color contrast, meaningful alt text, full keyboard operability, properly labeled form fields, headings in order, captions on video, and never using color as the only way of conveying information.
What Is the Most Common Accessibility Problem on Small Business Websites?
Color contrast — light gray text on a white background. Body text needs a ratio of at least 4.5:1 and large text 3:1. It is usually a design preference for elegance over legibility, and it is both the easiest failure to test for and the easiest to fix.
Do Accessibility Overlay Widgets Make My Site Compliant?
No. Overlays that promise instant compliance for a monthly fee are widely criticized by disability advocates and by screen reader users, who often find they interfere with the assistive technology they already run. They cannot repair the underlying markup, and businesses using them have still received complaints. Fixing the site is cheaper over any reasonable horizon.
Can I Just Run an Automated Accessibility Checker?
Run one, but do not stop there. Automated tools reliably catch roughly a third of issues — they are excellent at contrast and missing alt attributes, and cannot tell whether your alt text is meaningful or your tab order makes sense. Add a manual keyboard pass and a zoom-to-200% check; together those take about half an hour.
