The Guide To Understanding Web Accessibility?

Hi, I'm Heather — I've been building websites since 2008 and running Ravenous Raven Design here in Spokane for years now. And I want to tell you about the single most common conversation I have with business owners, because it always goes the same way.

Someone forwards me an email. Sometimes it's a demand letter. Sometimes it's a "compliance alert" from a company trying to sell them something. Sometimes it's just a client asking, "Hey, is my website ADA compliant? My cousin said I could get sued."

And then I look at their website, and almost every time, I find the same handful of problems. Not exotic ones. Not deep technical failures. Gold text on a cream background nobody can read. Photos with no alt text. A contact form where the fields have no labels attached to them. A menu you can't reach with a keyboard.

Here's the good news, and I mean this sincerely: web accessibility is one of the most fixable problems in your entire digital presence. It is not mysterious. It is not endlessly expensive. And the work you do to make your site usable for people with disabilities makes it better for everybody — including the search engines and AI assistants deciding whether to recommend you.

So let's walk through it properly. What accessibility actually is, what the law actually says right now in 2026, how to test your own site today for free, and how to tell the difference between someone who will genuinely fix your website and someone selling you a false sense of security.

What is web accessibility?

Web accessibility means designing and coding your website so people with disabilities can use it independently and get the same information, products, and services as anyone else.

That's a broader group than most people picture. It includes someone who is blind and navigates using a screen reader that announces your page out loud. Someone with low vision who zooms to 200% or needs strong color contrast. Someone with a motor disability who navigates entirely by keyboard or voice because a mouse isn't an option. Someone who is Deaf or hard of hearing and needs captions on your video. Someone with dyslexia, ADHD, or a cognitive disability who needs clear structure and plain language.

According to CDC data from the Behavioral Risk Factor Surveillance System, 28.7% of U.S. adults — roughly 70 million people — report having a functional disability involving hearing, vision, mobility, cognition, self-care, or independent living. That's more than one in four of your potential customers.

And here's the part people miss: accessibility isn't a permanent category. It's situational too. The person holding a baby and using one thumb. The person on a construction site squinting at their phone in direct sun. The 68-year-old with reading glasses trying to find your phone number. Your grandmother. Eventually, you.

The four principles behind every accessibility standard

Every rule you'll encounter traces back to four principles, known by the acronym POUR. I find this framework genuinely useful because it turns an intimidating spec document into four common-sense questions:

• Perceivable — Can people take in the information? (Images need text alternatives. Video needs captions. Text needs contrast.)
• Operable — Can people actually use the controls? (Everything reachable by mouse must be reachable by keyboard. No time limits people can't extend.)
• Understandable — Does it behave predictably? (Consistent navigation. Clear error messages that say what went wrong and how to fix it.)
• Robust — Does it work with assistive technology? (Valid, semantic HTML that screen readers and voice control software can interpret.)

If you remember nothing else from this article, remember POUR. When you're evaluating any part of your site, run it through those four questions and you'll catch most of what matters.

Why accessibility matters for Spokane businesses

I'll give you three reasons, in the order I think they actually deserve.

1. You are turning away paying customers right now

This is the one that gets buried under legal fear, and it's the one that should lead. When a med spa's booking form has unlabeled fields, a screen reader user hears "edit text, edit text, edit text" and has no idea which box is the phone number. They don't file a lawsuit. They leave and book with your competitor.

Every inaccessible form, every unreadable price, every button a keyboard can't reach is a conversion you paid to generate and then quietly threw away. If you're running SEO campaigns or Google Ads to drive traffic to a site people can't use, you're funding the leak.

2. The legal exposure is real, and it's aimed at small businesses

I'm not going to fearmonger, because plenty of vendors already do that. But I'm also not going to pretend this isn't happening.

According to UsableNet's tracking of digital accessibility litigation, plaintiffs filed roughly 4,900 web accessibility lawsuits in 2025, and more than 25,000 since 2018. The detail that matters most for you: analysis of that 2025 data found 64% of cases were filed against companies with annual revenue under $25 million. This is not a Fortune 500 problem. It is very much a small and mid-sized business problem.

Lawsuits are also just the visible part. Demand letters — the "pay us $10,000 and we go away" letters that never reach a courtroom — are estimated to outnumber filings several times over. Most business owners settle quietly because fighting costs more.

3. Accessible sites perform better in search and in AI answers

This one delights me because it's where my two obsessions overlap. Accessibility work and technical SEO are, to a startling degree, the same work wearing different hats:

• Alt text tells a screen reader what an image shows. It also tells Google, and it's how you rank in image search.
• Proper heading hierarchy lets a screen reader user jump between sections. It also gives crawlers and large language models the structural map they use to understand and cite your content.
• Descriptive link text ("view our web design pricing" instead of "click here") helps someone tabbing through links. It's also a ranking and relevance signal.
• Semantic HTML and clean structure is what assistive technology needs — and it's exactly what makes your content extractable for AI Overviews and chatbot citations.
• Captions and transcripts serve Deaf users and simultaneously hand search engines a full text version of video content they otherwise can't read.

I've watched sites pick up rankings after an accessibility remediation with no other changes, purely because the cleanup fixed structural problems crawlers were also struggling with. Accessibility isn't a tax on your marketing. It's an upgrade to it.

Understanding WCAG and web accessibility standards

Here's where most articles get vague, so let me be precise — because the precision is the useful part.

The Americans with Disabilities Act (ADA) is a civil rights law from 1990. It prohibits discrimination but contains no technical instructions for websites. The Web Content Accessibility Guidelines (WCAG) are the technical instructions — published by the W3C, an international standards body, not a government agency.

So WCAG is not itself a law. It is the standard that courts, regulators, and settlement agreements have consistently adopted as the measuring stick for whether a website meets the ADA's non-discrimination requirements. That distinction is why you'll hear conflicting things from different sources, and why an honest answer has to explain both pieces.

Which WCAG version and level do you need?

Version	Published	What it means for you
WCAG 2.0 AA	2008	The old floor. Referenced in Section 508 for federal agencies. Treat as the minimum, not the target.
WCAG 2.1 AA	2018	The practical target. Added mobile, touch, and cognitive criteria. This is the standard DOJ adopted for public entities and the one most settlements reference.
WCAG 2.2 AA	2023	Current version. Adds focus visibility, dragging alternatives, and larger target sizes. Building to 2.2 now means you won't redo this later.
Level AAA	—	The W3C itself doesn't recommend AAA as a site-wide requirement. Don't let anyone sell you on it as necessary.

My recommendation to every client: build to WCAG 2.2 Level AA, document your conformance against 2.1 AA. You satisfy the legal benchmark and you're ahead of the next revision.

What the law actually requires in 2026

This changed recently and a lot of published advice is now out of date, so pay attention to the dates here:

• ADA Title II (state and local government, public schools, public universities, special districts): DOJ published a final rule on April 24, 2024 adopting WCAG 2.1 Level AA as the required technical standard. On April 20, 2026, DOJ issued an interim final rule pushing the compliance deadlines back one year — April 26, 2027 for entities serving populations of 50,000 or more, and April 26, 2028 for smaller entities and special districts. The substantive requirements did not change, and DOJ stated it fully anticipates implementing the rule at the new deadlines.
• Recipients of HHS funding (many healthcare organizations): A parallel Section 504 rule imposes similar web and mobile accessibility requirements with its own compliance dates. If you take federal healthcare dollars, verify your specific deadline with counsel — this one has moved.
• ADA Title III (private businesses — most of my readers): There is no federal regulation specifying a technical standard. DOJ's Title III rulemaking has been paused indefinitely. But your obligation not to discriminate already exists, DOJ has published guidance stating web content must be accessible, and courts routinely apply WCAG as the yardstick. "There's no official rule" is not a defense that has worked.
• Section 508: Applies to federal agencies and their contractors. If you sell to the government, this is your standard.

If you want it straight from the source, DOJ's Guidance on Web Accessibility and the ADA is plain-English and short. The W3C's WCAG Quick Reference is the actual technical checklist.

Common accessibility problems in small-business websites

Here's my favorite fact in this whole field, because it turns an overwhelming problem into a to-do list.

WebAIM runs an annual automated scan of the top one million home pages on the internet. Their 2026 report, based on February 2026 data, found 95.9% of home pages had detectable WCAG failures — an average of 56.1 errors per page, and actually a step backward from 94.8% the year before.

But here's the punchline: 96% of all those errors fall into just six categories. And those same six have topped the list for seven straight years.

The problem	% of home pages	Who it locks out
Low contrast text	83.9%	Low vision, color blindness, anyone outdoors on a phone
Missing image alt text	53.1%	Screen reader users — plus your image SEO
Missing form input labels	51%	Screen reader and voice control users — this is your lead form
Empty links	46.3%	Anyone navigating by link list — usually icon links
Empty buttons	30.6%	Screen reader users hit "button" with no idea what it does
Missing document language	13.5%	Screen readers pick the wrong pronunciation — a one-line fix

Look at that list again. Not one of those is a hard engineering problem. Missing document language is literally one attribute in your HTML. Alt text is a text field WordPress already gives you. Contrast is a color decision.

What I see specifically on WordPress and page-builder sites

WordPress powers a huge share of small-business sites, and it actually performs slightly better than average in WebAIM's data — 52.8 errors per page versus the 56.1 overall. But page builders and themes introduce their own predictable trouble spots, and these are the ones I find over and over in the WordPress sites I take over:

• Heading levels chosen for looks, not structure. Someone picked H4 because it was the right size. WebAIM found skipped heading levels on 41.8% of pages. Headings are navigation, not typography — style them with CSS instead.
• Sliders and carousels that auto-advance. They move before people can read them, trap keyboard focus, and rarely have working pause controls. I generally recommend removing them entirely — they also hurt conversion rates.
• Brand colors used at unreadable contrast. Gold on white is a classic offender. Body text needs a 4.5:1 contrast ratio; large text needs 3:1. Run your palette through a contrast checker before it goes site-wide.
• Icon-only buttons and social links. A hamburger menu or Facebook icon with no accessible name reads as "button" or "link" and nothing else.
• Custom-styled forms with placeholder text instead of labels. Placeholders disappear when you start typing and are not a substitute for a real label. This is the one that costs you leads directly.
• Invisible or missing focus indicators. Someone removed the "ugly" outline on focused elements with CSS. Now a keyboard user has no idea where they are on the page.
• PDFs. Menus, price sheets, and intake forms uploaded as untagged PDFs are frequently unreadable by assistive tech. Put the content on a real web page.

How to test a website for accessibility

You can start this in the next ten minutes, for free, without installing anything. Do these four checks on your homepage and your main contact or booking page.

Test 1: Unplug your mouse

Seriously. Put it aside and navigate using only the Tab key, Shift+Tab, Enter, and the arrow keys. Ask yourself:

• Can you always see where you are? There should be a visible outline or highlight on the focused element at every step.
• Can you open the menu, move through it, and close it?
• Can you fill out and submit your contact form?
• Does focus ever get stuck — in a popup, a chat widget, a video player?
• Does the tab order follow the visual order of the page, or does it jump around?

This single test catches more real barriers than any automated scanner will. It's also uncomfortably revealing. I've had clients go quiet halfway through.

Test 2: Zoom to 200%

Press Ctrl and + (or Cmd and + on a Mac) until you're at 200%. Content should reflow and stay readable. Nothing should overlap, get cut off, or require horizontal scrolling. Then check your site on an actual phone, not just a browser resize.

Test 3: Turn on a screen reader

You already own one. VoiceOver is built into every Mac (Cmd+F5) and iPhone. Narrator ships with Windows (Ctrl+Win+Enter). NVDA is a free download for Windows.

Turn it on, close your eyes, and try to find your phone number. It will be humbling and it will be the most useful twenty minutes you spend on this. You don't need to become an expert — you just need to hear what your website sounds like.

Test 4: Check your color contrast

WebAIM's free Color Contrast Checker takes two hex codes and tells you whether the combination passes. Test every text-on-background pair in your brand palette: body text, headings, button labels, links, and — the one everyone forgets — text sitting on top of a hero image.

Using a web accessibility checker (and what it can't tell you)

Automated scanners are genuinely useful. They're fast, they're free, and they catch the highest-volume issues instantly. Start with these:

• WAVE (webaim.org/wave) — browser extension from the nonprofit behind the research above. Shows errors visually, overlaid on your actual page. My default starting point.
• Lighthouse — already built into Chrome. Right-click, Inspect, Lighthouse tab, run the accessibility audit.
• axe DevTools — free browser extension from Deque, widely used by developers and known for low false positives.
• The W3C Markup Validator — catches the broken HTML underneath a lot of accessibility failures.

Now here's the part you need to internalize, and it's the reason so many businesses get blindsided:

A scanner can tell you an image has no alt text. It cannot tell you whether the alt text you wrote is accurate or useful. It can confirm a form field has a label. It can't tell you the label is confusing. It can't evaluate whether your error messages make sense, whether your tab order is logical, or whether your video captions actually match the audio. Those require a human.

The honest truth about accessibility overlays and widgets

You've seen these — the little accessibility icon floating in the corner of a website that opens a panel of toggles for contrast, text size, and cursor options. They're sold as one line of code that makes your site compliant.

I'm going to be straight with you, because you deserve accurate information more than you deserve a comfortable answer:

• Overlays do not fix your underlying code. They modify the page in the browser after it loads. The source your site actually ships stays broken.
• Federal regulators have acted on overlay marketing claims. In January 2025 the FTC announced an action against overlay vendor accessiBe, and the final order in April 2025 required a $1 million payment over allegations the company misrepresented its AI tool's ability to make websites WCAG-compliant. The FTC's complaint stated the plug-in failed to make basic components — menus, form fields, image descriptions — accessible. You can read the case file on FTC.gov.
• Using a widget does not prevent lawsuits. UsableNet's litigation tracking found 1,416 companies were sued in 2025 while using a third-party accessibility widget, up from 1,023 in 2024.
• Many disabled users actively dislike them. Overlays can conflict with the screen reader or magnification setup someone has already configured to their own needs. University accessibility offices at Washington, Michigan, Minnesota, Iowa, and Arizona State all publicly advise against them.

Where does that leave you? Automated tools and scanners belong in your process — as diagnostics. What they can't be is your compliance strategy. If a vendor promises full ADA compliance from a script you paste in, that promise is not one the technology can keep, and a federal regulator has now said so in writing.

How accessible design improves usability and conversions

This is my favorite section to write, because accessibility gets framed as a cost center and that framing is just wrong.

Nearly every accessibility fix is also a conversion rate fix. Watch:

• Properly labeled form fields reduce errors and abandonment for everyone. Form abandonment is one of the biggest silent leaks in lead generation.
• Strong color contrast means your CTA button is readable on a phone in a parking lot in July. That is most of your mobile traffic.
• Clear, descriptive link and button text — "Book a consultation" instead of "Learn more" — raises click-through because people know what happens next.
• Logical heading structure makes your page scannable, and scanning is how nearly all visitors read.
• Helpful error messages that name the problem and the fix rescue abandoned checkouts and forms.
• Captions on video serve the enormous share of people who watch with sound off.
• Faster, cleaner code from removing bloated sliders and scripts improves Core Web Vitals, which affects both rankings and bounce rate.

Accessible design is just good design with the guesswork removed. When I rebuild a site with accessibility baked into the foundation, the client doesn't get a compromised version of what they wanted — they get a clearer, faster, better-converting version. You can see how that plays out across the sites in my portfolio.

Choosing an accessibility-focused Spokane web designer

Whether you hire me or someone else, here's how to tell the difference between a professional and a salesperson. I'd rather you find the right person than the nearest one.

Five questions to ask any web designer

1. "What WCAG version and level do you build to, and how do you verify it?" A real answer names a version (2.1 AA or 2.2 AA) and describes both automated and manual testing. A vague answer about "following best practices" means no.
2. "Do you test with a keyboard and a screen reader, or only with scanners?" Scanner-only is not testing. It's a third of testing.
3. "Will you fix the source code, or install an overlay?" You now know why this matters.
4. "What happens when my team adds new content?" Accessibility degrades with every uncaptioned video and untagged PDF. There should be a plan and training, not just a launch-day handoff.
5. "Can you show me a documented audit from real work you've done?" Ask for a redacted example. Anyone doing this properly has one.

Red flags to walk away from

• "One line of code makes you compliant." No.
• "100% ADA compliant, guaranteed." Conformance is measured against specific criteria at a point in time. Nobody can guarantee immunity from a lawsuit.
• "Certified ADA compliant" badges. There is no federal certification program for websites. That badge is marketing.
• Fear-based cold outreach with an artificial deadline. Legitimate practitioners don't need to scare you.
• A quote with no audit. If they haven't looked at your site, they're guessing at scope.

Why I take this personally

I've spent years working on sites in healthcare, financial services, nonprofits, and political campaigns — environments where compliance isn't optional and where I've handled HIPAA, CCPA, and GDPR requirements alongside accessibility. That's not a badge I bought. It's work I did, on deadline, with real consequences attached.

Here in Spokane I've been recognized as Best Web Designer (2019) and Best SEO (2020), and I've built accessible small-business websites for clients from the Inland Northwest to Japan, Canada, Australia, and the Netherlands. If you're weighing your options, I put together an honest guide to what actually separates a good website designer from a bad one — read it even if you hire someone else.

Next steps for improving your website

Don't try to do everything. Do these in order, and stop when you run out of time — you'll still be dramatically better off than when you started.

This week (2–3 hours, free)

• Run WAVE on your homepage, your top service page, and your contact page. Write down what it finds.
• Do the keyboard test on those same three pages.
• Check your brand color combinations in a contrast checker.
• Confirm your site declares a document language.

This month

• Write real alt text for every meaningful image. Describe what it shows and why it's there. Decorative images get alt="".
• Fix your form labels. Every field, properly associated — not placeholder text.
• Repair heading structure: one H1 per page, no skipped levels.
• Give every icon-only button and link an accessible name.
• Restore visible focus indicators if someone removed them.
• Caption your videos.

This quarter

• Get a manual audit against WCAG 2.2 AA covering your real user journeys, not just page templates.
• Publish an accessibility statement with your conformance level, known issues, and a way to report barriers. It's a genuine trust signal and it demonstrates good faith.
• Move critical PDF content onto real web pages.
• Train whoever publishes content — alt text and heading structure are content decisions, made weekly.
• Put accessibility checks into your ongoing site maintenance routine so it doesn't drift.

Frequently asked questions about ADA compliant websites

Is my small business website legally required to be ADA compliant?

If your business is a place of public accommodation under ADA Title III — which covers most businesses serving the public — your non-discrimination obligation already applies to your website. What doesn't exist is a federal regulation naming a specific technical standard for private businesses; DOJ's Title III rulemaking is paused. In practice, courts and DOJ guidance point to WCAG, and the absence of a formal rule has not protected defendants. Treat WCAG 2.1 AA as your working requirement. This is general information, not legal advice — talk to an attorney about your specific exposure.

How much does it cost to make a website ADA compliant?

It depends almost entirely on how many unique page templates you have and how bad the underlying code is — not your total page count. A 300-page site built on eight templates prices like an eight-page audit, because the same problems repeat everywhere. For a typical small-business site, a manual audit plus remediation commonly lands in the low thousands. A large site with heavy custom functionality runs considerably more. Any quote given without looking at your site is a guess. You can see how I structure project pricing on my web design pricing page.

Will an accessibility widget or overlay protect me from a lawsuit?

The evidence says no. UsableNet's tracking found 1,416 companies were sued in 2025 while running a third-party accessibility widget — up from 1,023 the year before. And in April 2025 the FTC finalized a $1 million order against overlay vendor accessiBe over its claims about making websites WCAG-compliant. Overlays modify the page in the browser; they don't fix the source code that courts and screen readers actually evaluate.

I just received a demand letter or lawsuit. What do I do first?

Call an attorney with ADA digital accessibility experience before you respond to anything, and before you pay anyone. Do not ignore it, and do not install an overlay hoping it makes the problem go away — that argument has not worked. In parallel, start a documented remediation effort, because demonstrating genuine good-faith progress matters in resolving these matters. Repeat filings against the same company are common when the original fix was cosmetic.

Does WordPress, Divi, Squarespace, or Wix make my site accessible automatically?

No platform makes a site accessible on its own. Every major platform is capable of producing accessible output, and every one of them can be used to build something completely unusable. WebAIM's 2026 data shows WordPress pages averaging 52.8 detected errors against an overall average of 56.1 — slightly better than typical, but nowhere near clean. Accessibility comes from how the theme is built, which plugins you run, and what your team publishes every week.

Does web accessibility actually help SEO, or is that a myth?

Accessibility is not a direct ranking factor, and anyone claiming otherwise is overselling. But the overlap is substantial and real: alt text, semantic heading structure, descriptive link text, video transcripts, valid HTML, and page performance all serve accessibility and search simultaneously. Structured, well-marked-up content is also what AI systems parse when deciding what to summarize and cite. The work compounds across both.

My developer says my site is already compliant. How do I verify that?

Ask for the artifact, not the assurance. A real conformance claim comes with a report: which WCAG version and level, which pages and user flows were tested, what tools and assistive technologies were used, which criteria passed and failed, and what remains open. If the answer is "we ran a scanner and it came back green," that covers roughly a quarter to a third of the criteria. Then do the keyboard test yourself — it takes five minutes and tells you a lot.

Do I need an accessibility statement on my website?

It isn't legally required for private businesses, but I recommend one for every client. A good statement names your target conformance level, acknowledges known issues honestly, gives people a direct way to report a barrier, and commits to a response time. It's a real trust signal to disabled visitors and it documents good faith. Just don't publish claims you can't back up — an inaccurate statement is worse than none.

Let's make your website work for everyone

If you made it this far, you care about doing this right — and honestly, that already puts you ahead of most business owners I talk to.

Start with the free checks in this article. Genuinely, do them today. If what you find is more than you want to tackle, or if you're staring at a demand letter and need someone who has navigated compliance-heavy environments before, I'm right here in Spokane and I'd love to look at your site.

No fear tactics, no certification badges, no one-line miracle scripts. Just a clear look at where your site stands, what it would take to fix it, and what it's worth doing first.

Want help beyond the website itself? I also handle search engine optimization and IT consulting for businesses that need one person who understands how all of it connects.

---

Heather Valencia is the owner of Ravenous Raven Design in Spokane, Washington. She has been developing websites since 2008, holds a BS in Business – Information Technology Management, and works with accessibility, HIPAA, CCPA, and GDPR requirements across healthcare, financial services, and nonprofit clients. This article is general information about web accessibility standards and is not legal advice.

Sources: U.S. Department of Justice, Guidance on Web Accessibility and the ADA and Title II final rule (April 2024) and interim final rule (April 2026) · W3C, Web Content Accessibility Guidelines 2.2 · WebAIM, The WebAIM Million 2026 (February 2026 data) · Federal Trade Commission, In the Matter of accessiBe, Inc., final order April 2025 · UsableNet, digital accessibility lawsuit reports 2024–2026 · CDC, Disability and Health Data System (2022 BRFSS). Last reviewed July 2026.