Accessibility used to be treated as a niche legal checkbox. In 2026 it's simply good web design: roughly 1 in 6 adults lives with some form of disability, and an inaccessible website quietly turns away a meaningful slice of your potential customers before they ever reach your contact form.
The good news is that most of what makes a site accessible also makes it faster, clearer, and easier to use for everyone else. This guide walks through the fixes that matter most for a small business website, in the order we'd tackle them on a real project.
1. Why accessibility matters for small business
Beyond the ethical case, there's a straightforward business one. Accessible sites tend to have cleaner code, better SEO, and lower bounce rates, because the same structure that helps a screen reader also helps Google understand your content and helps a mobile user with a cracked screen or bad connection get through your site.
There's also real legal exposure: businesses of every size, from local shops to national retailers, have faced accessibility-related lawsuits and demand letters in recent years. You don't need to be a Fortune 500 company to be a target — you just need a public-facing website.
2. Color contrast & readable text
Low-contrast text is the single most common accessibility failure we see on small business sites — light grey text on a white background looks "clean" in a mockup and is genuinely hard to read for anyone with low vision, glare on their screen, or just tired eyes at the end of the day.
-
Meet WCAG AA contrast ratios:
Body text should hit at least a 4.5:1 contrast ratio against its background; large headings can go as low as 3:1. Free tools like WebAIM's Contrast Checker will tell you instantly if a color pairing passes.
-
Don't rely on color alone:
If a required form field turns red on error, also add an icon or text label. Around 1 in 12 men have some form of color vision deficiency and may not perceive the red at all.
-
Keep body text a legible size:
16px is a reasonable minimum for paragraph text, with enough line height (1.4–1.6) that lines of text don't blur together for readers with dyslexia or low vision.
3. Keyboard navigation & focus states
Not everyone uses a mouse or trackpad. People with motor impairments, screen reader users, and plenty of power users navigate entirely by keyboard — tabbing from link to link and pressing enter to activate them.
-
Never remove the focus outline:
outline: none;without a visible replacement is one of the most common accessibility mistakes in custom CSS. Keyboard users need to be able to see exactly which element is currently focused. -
Test your own tab order:
Unplug your mouse for five minutes and tab through your homepage, nav, and a contact form. If focus jumps somewhere unexpected or gets trapped, that's a real bug to fix.
-
Add a "skip to content" link:
A hidden link that appears on first tab and jumps past the header/nav saves keyboard and screen reader users from re-tabbing through the same menu on every single page.
4. Alt text & meaningful images
Alt text is how screen reader users experience your images, and it also gives Google more context about the page. The trick is writing alt text that's actually descriptive rather than generic filler.
- Describe what's actually in the image and why it's there —
alt="Team meeting around a whiteboard sketching a website wireframe"beatsalt="image1.jpg"oralt="photo". - Purely decorative images (background textures, dividers) should use an empty
alt=""so screen readers skip over them instead of reading a meaningless description. - If an image contains important text, like a promo graphic with a discount code, put that same text in the alt attribute or, better, in real HTML text nearby.
5. Accessible forms & error messages
Forms are where accessibility problems cost you the most directly — a confusing or broken contact or checkout form doesn't just frustrate a visitor, it loses you the lead or the sale outright.
-
Label every field properly:
Use a real
<label>tied to each input withfor/id, not just placeholder text that disappears the moment someone starts typing. -
Write specific error messages:
"Please enter a valid email address" is far more useful than a generic "Error" banner, especially for someone using a screen reader who can't visually scan the form for what's wrong.
-
Make required fields clear:
Mark required fields with visible text ("required") in addition to an asterisk, and announce them via
aria-required="true"for assistive technology.
6. Testing tools & ongoing audits
You don't need to memorize the entire WCAG spec to make real progress. A handful of free tools will catch the majority of issues automatically, and a quick manual pass covers most of what's left.
- Automated scanners: Free browser extensions like axe DevTools or WAVE flag missing alt text, low contrast, and structural issues in seconds.
- Lighthouse accessibility score: Built into Chrome DevTools, it's a quick way to spot-check any page for free alongside your existing performance and SEO scores.
- Manual keyboard and screen reader pass: Automated tools catch roughly a third of issues; tabbing through key pages yourself and trying a free screen reader like NVDA catches the rest.
- Re-check after major changes: A new page template, form, or interactive widget can introduce new issues, so accessibility is worth revisiting any time you ship something new, not just once at launch.
7. Frequently asked questions
In the US, the ADA doesn't spell out exact web technical standards, but courts increasingly treat websites as places of public accommodation, and businesses of all sizes have faced accessibility lawsuits. Meeting WCAG 2.1 AA is the widely accepted way to reduce that legal risk while genuinely improving usability.
No. Most accessibility issues are fixable without a redesign: adding alt text, improving color contrast, fixing heading structure, and ensuring keyboard navigation works can all be layered onto an existing site.
Run a full audit any time you launch or redesign a site, then a lighter check every few months or whenever you add new page templates, forms, or major content types, since new features can introduce new issues.
Written by Build My Website
We build 100% custom websites, branding, and search engine strategies for small businesses. Operating since 2014 with 142+ websites shipped.