The Venbit TeamThe short answer
Web accessibility means people with disabilities can use your site. It matters because it is the right thing to do, it expands your customer base, it helps SEO, and small businesses do receive demand letters over inaccessible sites. Most of what counts comes down to six practical basics covered here.
Key takeaways
- Accessibility is about real people, not just legal compliance. Roughly one in four Americans has some kind of disability.
- The practical basics: alt text, color contrast, keyboard navigation, labeled forms, readable text, and descriptive links.
- Overlay widgets do not fix accessibility. They layer a bandage over problems that need real fixes.
- Full WCAG compliance is a moving target. Start with the high-impact items and keep improving.
- This article is not legal advice. If you have received a demand letter, talk to an attorney.
We are a web design and SEO studio based in Mill Creek, Washington, and we work with businesses up and down the Puget Sound as well as clients across the US and Canada. One question that comes up consistently, no matter where a client is located, is web accessibility. Can a person who uses a screen reader get through your navigation? Can someone who cannot use a mouse still fill out your contact form? These are not obscure technical questions. They affect real customers, they affect how search engines read your pages, and in some cases they affect whether you end up with a demand letter in your inbox.
This guide is written for small business owners, not developers. You do not need to know what ARIA stands for to understand what needs fixing. We will cover what accessibility actually means, why it matters in practical terms, and what the basics look like without the jargon.
What web accessibility actually means
Web accessibility means that people with disabilities can perceive, navigate, and interact with your website. That covers a wide range of situations: people who are blind or have low vision, people who are deaf or hard of hearing, people with motor impairments who cannot use a mouse, people with cognitive differences who benefit from clear structure and plain language, and people using older devices or slow connections.
About one in four American adults has some kind of disability, according to the CDC. That is a large slice of your potential customer base, whether you are running a local service business in the Seattle area or selling nationally. Some of them use assistive technology like screen readers. Some rely on keyboard navigation. Some need high-contrast text to read comfortably. Building a site that shuts those people out is not just a legal risk. It is leaving customers behind.
WCAG: the standard behind most accessibility guidance
The Web Content Accessibility Guidelines (WCAG) are the internationally recognized technical standard for web accessibility. They are published by the W3C, the body that sets web standards, and they organize requirements around four principles: content must be Perceivable, Operable, Understandable, and Robust. Those four words spell out POUR, and that framing is actually useful for non-developers.
- Perceivable: Users can see or hear all content, even if they use a screen reader or cannot perceive color.
- Operable: Users can navigate and interact with everything using a keyboard, not just a mouse.
- Understandable: Content is clear, forms explain their errors, and pages behave predictably.
- Robust: The site works with current and future assistive technologies.
WCAG has three conformance levels: A (minimum), AA (the practical standard most guidance references), and AAA (the highest, rarely required in full). When someone talks about an accessible website, they usually mean WCAG 2.1 AA or the newer WCAG 2.2 AA. Those are the benchmarks courts and regulators tend to point to as well.
Why small businesses should pay attention
Three reasons that are worth being direct about.
It is the right thing to do. People with disabilities deserve the same access to your products and services as anyone else. Full stop.
It widens your customer base and helps SEO. An accessible site is cleaner, faster to parse, and more logically structured. Search engines reward that. Alt text on images, proper heading structure, descriptive link text, and clear page hierarchy all overlap with good SEO practice. Accessible sites tend to rank better, not because of some special bonus, but because the same things that help screen readers also help crawlers.
Small businesses do get demand letters. The ADA does not include a private right of action for injunctive-only claims in some circuits, but serial litigation over inaccessible websites has been a real pattern for over a decade. Large companies are the most visible targets, but small business owners have received demand letters too. We are not saying this to scare you. We are saying it because pretending it does not happen is not useful to you.
The practical basics that cover most of the ground
You do not need to fix everything at once. Start with the items that come up most often in audits and that affect the most users. Here is an honest ranking of where to focus.
| What to fix | Why it matters | Difficulty |
|---|---|---|
| Alt text on images | Screen readers read this aloud. Without it, an image-heavy page is a wall of silence. | Low |
| Color contrast | Light gray text on white is unreadable for many people. WCAG AA requires a 4.5:1 ratio for normal text. | Low to medium |
| Keyboard navigation | Every link, button, and form must be reachable and usable with Tab and Enter alone. | Medium |
| Labeled form fields | Every input needs a real label element. Placeholder text disappears when you start typing and does not count. | Low |
| Readable text size | Body text below 16px on most screens is a real barrier. Avoid tiny print. | Low |
| Descriptive link text | "Click here" tells a screen reader nothing. "Request a free quote" tells them everything. | Low |
| Captions on video | Required for deaf and hard-of-hearing users, and watched without sound by many others. | Medium |
| Logical heading structure | One H1 per page, then H2 for sections, H3 for subsections. Do not skip levels. | Low |
A practical checklist to get started
Work through this list on your own site. Most of it you can check yourself in about an hour with a browser and some free tools.
- 1Open every page and look at every image. Does it have alt text that describes what the image shows? Decorative images (dividers, backgrounds) should have empty alt text (alt="") so screen readers skip them. Meaningful images need real descriptions.
- 2Check your color contrast. The free WebAIM Contrast Checker lets you plug in your foreground and background colors and see the ratio. Aim for 4.5:1 or better for body text. Large text (18px bold or 24px regular) can use 3:1.
- 3Put your mouse down and navigate your site using only the keyboard. Press Tab to move through links and buttons. Press Enter to activate them. You should be able to reach every interactive element and see a visible focus indicator (the outline that shows where you are). If it disappears or you get stuck, that is a problem.
- 4Review every form on your site. Each field should have a label that stays visible. The label element must be properly connected to its input, not just visually nearby. Error messages should clearly say what went wrong and how to fix it.
- 5Check your font sizes in a real browser at normal zoom (100%). Body text should be comfortably readable, generally 16px or larger. Let users zoom without the layout breaking.
- 6Search your pages for any link that says "click here," "read more," or "learn more" with no additional context. Rewrite them to describe the destination: "Download our accessibility checklist," "Read the full project case study."
- 7If you have any videos on your site, confirm they have accurate captions. Auto-generated captions are a start but often need corrections, especially for industry terms or proper nouns.
- 8Check your heading structure. Each page should have exactly one H1. Section headings should be H2. Sub-sections should be H3. Do not use heading tags just to make text look bigger. Use CSS for that.
- 9Run your site through the free WAVE tool (wave.webaim.org). It will flag obvious errors and contrast failures. It is not a complete audit, but it will surface the most common problems quickly.
- 10Add a simple accessibility statement to your site, even just a short paragraph in your footer, noting your commitment to accessibility and providing a contact method for anyone who runs into a barrier. This shows good faith.
On overlay widgets: they are not the fix people sell them as
You may have seen companies selling accessibility overlay tools, browser widgets that promise to make your site compliant with a single script. Names like AccessiBe, UserWay, and others. They do not work as advertised.
Overlay tools apply automated fixes on top of inaccessible code. They cannot see what your images actually show, so they cannot write meaningful alt text. They cannot fix broken keyboard traps. They cannot restructure a page with broken heading hierarchy. Real assistive technology users have documented how overlays frequently make their experience worse, not better, by interfering with the tools they already rely on.
More to the point: courts and plaintiffs have not accepted overlay tools as a defense against ADA claims. You can spend money on an overlay and still receive a demand letter. The fix for an inaccessible site is to fix the underlying code, not to layer something over it.
An overlay widget is like putting a ramp sticker on your steps. It looks like you did something. But the steps are still there.
The honest truth about "100% compliant"
No one's site is perfectly accessible forever. WCAG guidelines get updated. New assistive technologies emerge. Content changes. The goal is not a one-time certification and then done. The goal is to build accessibility into how you maintain and update your site: write alt text when you upload images, check contrast when you update colors, test keyboard navigation when you add a new form.
Automated tools catch maybe 30% to 40% of accessibility issues. The rest require human judgment: does this label actually make sense? Is this navigation logical in sequence? Does this error message actually help? A proper audit combines automated scanning with manual testing and ideally includes testing by actual users of assistive technology.
For a small business site, the practical target is: fix the obvious failures, build good habits around the basics, and make meaningful progress. That is a more honest standard than a compliance badge, and it does more actual good for real users.
What to do if your site has a long way to go
Start with the checklist above. Fix what you can fix yourself this week: alt text, link text, form labels. Those are low-cost, high-impact changes that any developer can make in an afternoon.
If your site is built on a theme or platform that has structural accessibility problems, the fix often requires a developer who knows what they are looking for. A proper audit will tell you what is actually broken, in plain terms, so you know what you are asking someone to fix and can get a realistic scope and cost.
If you have received a demand letter, stop and call an attorney before you do anything else. Do not respond, do not delete emails, and do not assume that quickly adding an overlay will resolve it. Get legal counsel first.
Not sure where your site stands?
Whether you are in the Seattle area or running a business anywhere in the US or Canada, we can do a plain-English accessibility and SEO review of your site and tell you what the real issues are, what to prioritize, and what it would take to fix them. No jargon, no pressure.
Related services
The Venbit Team
Web design & SEO, Seattle
Venbit is a Seattle-area web design, SEO, and digital marketing studio. Since 2011 we've designed, built, and ranked small-business websites for clients across the Puget Sound and around the country, so the numbers and advice here come from real projects, not a content mill.