Picture a customer who wants to book an appointment on your website. She's sharp, motivated and ready to pay. She also has low vision, so she zooms the page to a size that makes your layout fall apart. The booking button is light gray on white. She can't tell it's a button, and the form below it has no labels she can read. After a few minutes, she gives up and calls your competitor.
You never knew she was there. That's the strange thing about accessibility problems: they don't announce themselves. They show up as people who quietly leave.
This guide to website accessibility for small business is meant to take the mystery out of it. It's not a legal brief. It's a plain-English tour of who this helps, what the standard says, which fixes matter most and where the common shortcuts go wrong.
Who accessibility helps (more people than you would think)
When people hear "accessibility," they often picture a narrow group. The reality is broader. The W3C's Web Accessibility Initiative describes the audience as people with disabilities across hearing, vision, movement, speech, cognitive and neurological differences. It also notes the benefits reach people who don't think of themselves as disabled:
- Someone with a broken wrist using one hand.
- An older customer whose eyesight and fine motor control have changed.
- A person on a phone in bright sunlight, squinting at low-contrast text.
- A visitor on a slow or expensive connection.
- Someone in a noisy room watching a video without sound.
Good accessibility helps all of them, and it makes the site easier for everybody. That's the first reason a small business should care. Accessible sites tend to be clearer, faster to use and easier to read, which are the same qualities that turn visitors into customers.
The second reason is simpler. Turning people away at the door is bad business, and it's rarely intentional. Most inaccessible sites are inaccessible by accident, because nobody on the project knew to check.
What WCAG is, in plain English
If you've heard "WCAG" and your eyes glazed over, here's the short version. The Web Content Accessibility Guidelines are the international standard for accessible websites, published by the W3C. You can read the overview on the W3C's WCAG page.
A few things worth knowing:
- It's a set of testable rules. Each "success criterion" is something you can check as passed or failed, such as "text has enough contrast with its background."
- It has three levels: A, AA and AAA. A is the baseline, AA is the level most organizations and policies aim for, and AAA is the most demanding and isn't expected for every kind of content.
- It has versions. WCAG 2.0, 2.1 and 2.2 each add criteria without removing earlier ones, so a site that meets 2.2 also meets the older versions. The W3C encourages using the latest.
- It's built around four ideas: content should be perceivable, operable, understandable and solid enough to work with different tools.
You don't need to memorize the document. It's written mainly for developers and evaluators, and even the W3C says it isn't an introduction to accessibility. What a business owner needs is the target: aim for WCAG 2.2 level AA, and ask anyone building your site to do the same.
The common fixes that matter most
Here's the part that surprises owners. A handful of repeat problems cause a large share of the barriers on small business sites. Fixing these gets you most of the way.
Color contrast
Text has to stand out from its background. At level AA, normal-size text needs a contrast ratio of at least 4.5 to 1, and large text needs 3 to 1. Light gray on white, pale buttons and text over busy photos are the usual offenders.
Free contrast checkers will tell you the ratio for any two colors. If your brand palette fails, you rarely have to abandon it; you adjust the shade of the text or button until it passes. Our piece on color psychology in web design covers choosing a palette that works on emotion and legibility at once. Also remember that color shouldn't be the only signal. If required form fields are marked only in red, someone who can't see red misses it. Add a symbol or a word.
Text descriptions for images
People who use screen readers hear a description in place of a picture. That description is the alt text, and it should say what the image contributes. A photo of your crew on a roof might read "Two Summit Roofing installers replacing shingles on a two-story home." A purely decorative flourish gets empty alt text so it's skipped.
Two traps to avoid: leaving it blank on images that carry meaning, and stuffing it with keywords. Write for a person who can't see the image, and the search engines will be fine too. If your logo links to the homepage, its description should say that, not just the company name.
Keyboard use
Some people can't use a mouse. They navigate with the Tab key, a switch device or voice control. Try it yourself: put the mouse aside and use only your keyboard on your own site.
- Can you reach every link, button and form field?
- Can you always see where you are (a visible outline or highlight on the focused item)?
- Does the menu open and close without a mouse?
- Can you get out of every pop-up?
- Is there a way to skip past a long menu straight to the content?
If you get trapped or lost, so does a real user. Removing the focus outline for looks is one of the most common mistakes, and it's easy to reverse.
Form labels and error messages
Forms are where many small businesses make money, and they're where inaccessible sites hurt most. Each field needs a real label tied to it in the code, not just gray placeholder text that vanishes when someone starts typing. When something goes wrong, the error message should say what happened in words ("Please enter a phone number with area code"), and point to the field.
Short tap targets matter here too. WCAG 2.2 sets a minimum target size so buttons aren't too tiny to hit, which also helps anyone using a phone with a thumb.
Headings and page structure
Screen reader users often jump from heading to heading to scan a page, the way sighted users scan with their eyes. So headings should describe the content and follow a sensible order: one main heading, then sections, then subsections. Don't pick a heading level because it looks the right size. Choose it for structure, and style it separately.
Use real lists for lists and real buttons for buttons. Page landmarks, such as a clear header, navigation and main content area, help too. A good web accessibility setup is mostly this: proper structure that assistive tools can understand.
Captions and transcripts
Video with speech needs captions, and audio-only content needs a transcript. Captions help deaf and hard-of-hearing visitors, and they also help anyone watching in a waiting room or on a train. If you have a welcome video on your homepage, it's worth doing first.
Why overlay widgets aren't the fix
You've probably seen the pitch: add one line of code, get a little accessibility icon on your site, and become "compliant." It's tempting, because it sounds cheap and quick.
Here's the honest picture. An overlay is a layer of software that sits on top of your existing site. It can offer genuinely handy display options such as larger text or higher contrast. What it can't do is repair the underlying problems: missing alt text, mislabeled forms, a menu that traps keyboard focus, headings used for styling. Those live in your site's code and content, and a script loaded on top doesn't reliably change them.
There's a second problem. Many people who rely on assistive technology already have their own tools set up exactly how they like them, and an overlay can interfere with those. That's why a number of accessibility professionals and disability advocates are openly skeptical of overlays.
That doesn't mean overlays are evil, or that display options are useless. Think of one as an extra, not a foundation. If a vendor promises that a widget makes you "fully compliant" or protects you from legal trouble, be cautious. Nothing you can install replaces building the site properly. The work is in the structure, the content and the testing.
The legal question, answered honestly
We're a web design company, not a law firm, so nothing here is legal advice. If you have a legal question about your own obligations, talk to an attorney who knows your industry and location.
With that said, here's what we can tell you straight. Accessibility is required by law in many situations, and the rules vary by country, by state and by the kind of business you run. In the United States, laws about discrimination on the basis of disability have been applied to websites by courts and by businesses sending demand letters. Other countries have their own rules, and some set specific technical requirements for certain organizations.
What we won't do is scare you with statistics we can't source, or tell you a particular tool makes you bulletproof. Nobody can honestly promise that. What's true is that a site built to WCAG 2.2 AA, with documented testing and a way for visitors to report problems, is in a much stronger position than one that never considered the issue. And it's the right way to run a business regardless.
A good attorney can tell you whether specific rules apply to you, such as government contracts, healthcare or education, which tend to come with extra requirements. We can build and test the site against the technical standard. Those are two different jobs, and you may need both.
A practical way to start without a big budget
Website accessibility for small business does not need a huge project. Here is the order of operations we would suggest:
- Run a quick automated scan. Our free website check is a good first look at your site's health, and dedicated accessibility checkers will flag missing alt text, low contrast and unlabeled fields. Automated tools only catch part of the problems, so treat the results as a starting point.
- Do the keyboard test. Ten minutes with no mouse will reveal more than you'd expect.
- Zoom to 200 percent and see if the page still works. Then check it on a phone.
- Check your top pages by hand: home, contact, your main service pages and anything involving a purchase or a form.
- Fix in order of impact. Forms and navigation first, then images and contrast, then the long tail.
- Add an accessibility statement with a contact method, so people can tell you when something doesn't work. Then answer when they do.
- Test with real people if you can. Nothing beats watching someone who uses assistive technology try your site.
Keep notes on what you tested and fixed. If anyone ever asks, a record of good-faith effort matters.
Build it in when you redesign
Retrofitting accessibility onto a finished site is slower than building it in from the start. If you're planning a new site, put accessibility in the brief. Ask any designer or developer how they handle contrast, keyboard use and form labels. If they stare blankly, that tells you something. Our web design process includes these checks as part of the build, not as an add-on at the end.
Also remember that accessibility isn't a one-time fix. Every new page, photo and video you add is a chance to keep it up or let it slip. Train whoever updates your site on the basics: write alt text, use real headings, caption videos.
Website accessibility for small business: make it normal
The best way to think about accessibility is as part of making a site good, not a separate compliance chore. Clear contrast, honest structure, labeled forms and captioned videos are the same habits that make a site easy to read, easy to use and trusted.
You won't get everything perfect on the first pass, and nobody does. Start with the keyboard test and the contrast check this week. Fix what you find. Then keep going, one page at a time.
If you'd like a second opinion on where your current site stands, we're happy to talk it through on a discovery call, including when the honest answer is that a few fixes will do.