8-Step Website ADA Compliance Playbook for US SMBs

Yes, if your website serves the public, the Americans with Disabilities Act applies to it. The Department of Justice treats WCAG 2.1 Level AA as the working standard for what “accessible” means, and state and local government sites now face firm deadlines to meet it. Your next move is simple: audit your top pages against that standard and fix the worst barriers first. Compliance isn’t a certificate you earn once. It’s a habit you maintain.

TL;DR:

  • Most accessibility failures on websites stem from poor heading structure, missing alt text, and insufficient color contrast, which pose high compliance risks.
  • Automated testing detects only about 30 to 40 percent of issues, so manual keyboard navigation and screen reader checks are essential for accurate assessment.
  • Prioritize fixing transactional pages and high-traffic content first, focusing on comprehensive remediation that becomes part of ongoing site maintenance.
  • Even small businesses likely fall under Title III or Title II if serving the public or government, making WCAG 2.1 Level AA compliance a legal necessity.
  • Building accessibility into website design from the start reduces costs, improves user experience for everyone, and lowers the risk of legal action.
King Digital Marketing Agency
Build A More Accessible Website
King Digital creates tailored websites and digital strategies for Albuquerque businesses focused on visibility, leads, and better online experiences.

Table of Contents

Two different parts of the ADA govern this issue, and mixing them up causes most of the confusion online. Title III covers “public accommodations,” which is legal language for businesses open to the public: retailers, restaurants, banks, medical offices, hotels. Title II covers state and local government entities: city websites, public school portals, transit authority apps.

The Department of Justice has long taken the position that Title III’s nondiscrimination requirement extends to a business’s website, not just its physical storefront. That position isn’t new. Courts have backed it repeatedly, including in the Winn-Dixie case, where the DOJ argued that a retailer’s website needs to provide equal access when it is tied to services the company offers to the public. The DOJ didn’t wait for Congress to write website-specific rules into the ADA text. It simply applied the existing nondiscrimination principle to a new medium.

Title II is where things got concrete. In 2024, the DOJ finalized a rule requiring state and local government entities to make their web content and mobile apps conform to WCAG 2.1 Level AA. This wasn’t a suggestion. It came with actual compliance dates, tied to the size of the government entity, and an implementing regulation that spells out what “conform” means in technical terms.

Here’s what business owners need to understand about how this plays out in practice:

  • There is no federal “ADA compliant” certificate or seal. Nobody at the DOJ issues a stamp of approval. Compliance is a status you maintain, not a badge you purchase.
  • Title III has no codified technical standard the way Title II now does, but WCAG 2.1 AA is the de facto benchmark courts and plaintiffs’ attorneys point to.
  • Private lawsuits under Title III are the dominant enforcement mechanism for businesses, not direct DOJ action, though the DOJ can and does investigate complaints.
  • “Equivalent facilitation” is a concept baked into Title II flexibility. If your government-adjacent entity meets accessibility goals through an alternative method that works as well as the WCAG technique, that can satisfy the intent of the rule.

For a private business, the risk isn’t a government fine. It’s a demand letter or a federal lawsuit from a plaintiff who couldn’t complete a purchase, book an appointment, or read your menu because your site fought them at every turn.

Does the ADA Apply to Your Website?

The test hinges on one question: does your organization serve the public, and does your website connect to that service? A “public accommodation” under Title III is a broad category. Retail stores, restaurants, movie theaters, banks, doctor’s offices, gyms, and law firms all qualify, and so does almost any small business with a storefront or a service the public can hire.

If you run a state agency, county office, public university, or municipal transit system, you fall under Title II instead, with the specific WCAG 2.1 AA requirement and its compliance deadlines attached directly to your entity.

Run through this short checklist to figure out where you stand:

  • Does your site let visitors buy something, book something, or request a service? If yes, you’re almost certainly a public accommodation under Title III.
  • Is your website an extension of a physical location open to the public (a “nexus”), even if the site itself is just informational?
  • Are you a government body, school district, or agency that receives public funding? Then Title II and its firm WCAG 2.1 AA requirement apply directly.
  • Does your site host any interactive element, like a contact form, chat widget, or online scheduler, that a person with a disability might need to use independently?

Almost every small to medium business with an online presence answers “yes” to at least one of these. If your site does anything beyond serving as a static brochure, treat website accessibility requirements as a real obligation, not a theoretical one.

What WCAG 2.1 Level AA Actually Requires

WCAG organizes accessibility around four principles known as POUR: content must be Perceivable, Operable, Understandable, and Robust. Each principle breaks into “success criteria,” rated Level A (minimum), AA (the standard the DOJ points to), or AAA (aspirational, rarely required).

Wcag Pour Principles And Conformance Levels

You don’t need to master all of WCAG to make real progress. A handful of success criteria account for the vast majority of real-world accessibility failures on business websites, and they deserve your attention first.

Keyboard accessibility (SC 2.1.1 and 2.1.2) sits at the top of that list. Every interactive element, menus, forms, buttons, sliders, needs to work without a mouse, and users must never get stuck with no way to move focus away from an element. The Access Board’s keyboard baseline is blunt about this: a site that traps keyboard users is failing at a fundamental level, not a cosmetic one.

Alternatives for non-text content (SC 1.1.1) means every meaningful image needs alt text that describes its purpose, not just its filename. Decorative images should be marked so screen readers skip them entirely.

Headings and page structure (SC 2.4.x) require a logical outline, one H1, properly nested H2s and H3s, so screen reader users can navigate by heading the same way a sighted user scans a page visually.

Contrast (SC 1.4.3) sets a minimum ratio between text and its background, generally 4.5 to 1 for normal text. Light gray text on a white background, a favorite of minimalist design, routinely fails this.

Captions for media (SC 1.2.x) apply to any prerecorded video with audio. No exceptions for short marketing clips.

Form labels and error handling (SC 3.3.2) require every input field to have a programmatically associated label, and error messages need to tell users specifically what went wrong and how to fix it.

Repetitive content deserves a mention too. WCAG’s bypass blocks requirement and the consistent-navigation success criteria exist because keyboard and screen reader users shouldn’t have to tab through your entire header and navigation menu on every single page just to reach the content they came for.

Your Practical ADA Compliant Website Checklist

Legal theory doesn’t fix a broken form field. Here’s a working checklist for tackling the highest-impact problems first, organized by effort and legal exposure so you know where to start.

  1. Add skip links and test keyboard-only navigation. Effort: low. Risk if ignored: high. Press Tab repeatedly through your homepage and checkout flow. If focus disappears, jumps randomly, or gets trapped in a menu, that’s a critical fix, not a nice-to-have.

  2. Write real alt text for every meaningful image. Effort: low. Risk: high. Skip generic phrases like “image1.jpg” or “photo.” Describe what the image conveys and why it’s there. Purely decorative images get an empty alt attribute so screen readers ignore them.

  3. Fix your heading structure. Effort: low. Risk: medium. One H1 per page. Headings nested in order, no skipping from H2 straight to H4 because it “looked better” in the CSS. This is also good practice for keyword optimization, so the fix pays double.

  4. Label every form field and write clear error messages. Effort: medium. Risk: high. A checkout form with unlabeled fields is one of the most common triggers for demand letters, because it blocks an actual transaction, not just a browsing experience.

  5. Run a contrast check on your color palette. Effort: low. Risk: medium. Branding decisions often clash with accessibility here. If your brand guide calls for light gray on white, expect to negotiate.

  6. Add captions to video content. Effort: medium to high. Risk: medium. Auto-generated captions from your video host are a starting point, but they need a human review pass for accuracy before you consider the job done.

  7. Audit your PDFs and downloadable documents. Effort: medium. Risk: medium. A scanned PDF with no text layer is invisible to a screen reader. Either provide an accessible HTML version of critical documents (menus, applications, policies) or run the PDF through a proper accessibility remediation process before publishing it.

  8. Review your ARIA usage, and remove what you don’t need. Effort: medium. Risk: low to medium. The rule of thumb here matters: use semantic HTML first, and reach for ARIA roles only when native HTML can’t do the job. Overused or incorrect ARIA attributes frequently create more confusion for assistive technology than having no ARIA at all.

Pro Tip: Test your own checkout or booking flow with your mouse unplugged before you hire anyone to audit it. Fifteen minutes of keyboard-only browsing will surface more real problems than most people expect, and it costs nothing.

If your site runs on WordPress, the same priorities apply, and the platform actually makes several of these fixes faster. Most modern WordPress themes support proper heading hierarchy and alt text fields out of the box, but you still have to fill them in. Making WordPress accessible usually comes down to plugin discipline (avoid ones that inject unlabeled sliders or carousels), theme choice, and a content editor who understands why heading order matters.

Testing Your Site: Why One Tool Is Never Enough

No single tool catches everything, and treating an automated scan as your finish line is one of the most expensive mistakes a business can make. Automated scanners typically catch roughly 30 to 40 percent of accessibility issues, the kind of problems a machine can detect through code structure alone, like missing alt attributes or invalid HTML. Everything else, confusing navigation, illogical tab order, form errors that don’t actually help a real user, requires a human.

A hybrid testing workflow, combining automated scans with manual and assistive-technology checks, is what government agencies and accessibility consultants both rely on, and it’s the same standard your business should aim for.

The workflow looks like this in practice:

  • Run a full-site automated scan first. This gets you a baseline and flags the low-hanging fruit fast.
  • Do manual keyboard navigation testing on every critical page. Checkout, contact forms, booking flows, anything transactional.
  • Spot-check with a screen reader, NVDA on Windows or VoiceOver on Mac, focusing on the same critical pages.
  • Run task-based testing with real assistive-technology users where possible, especially before a major redesign launch.

For manual inspection, your browser’s own DevTools Accessibility panel exposes the accessibility tree and computed ARIA properties directly, which is invaluable for catching mislabeled buttons. ANDI, a free single-page testing tool, offers similar inspection without requiring you to install anything.

A useful audit report doesn’t just list problems. It maps each issue to a specific WCAG success criterion, assigns a severity level, estimates the remediation effort, and includes verification steps so someone can confirm the fix actually worked once it ships.

Turning Findings Into a Remediation Plan That Sticks

An audit that sits in a shared drive helps nobody. The value comes from what happens after, and that requires prioritization, not a scramble to fix everything simultaneously.

Weigh each finding against four factors: how many users it blocks, how much traffic or revenue that page drives, how much legal exposure it carries, and how complex the fix actually is. A missing form label on your contact page and a missing form label on your primary checkout flow are not the same priority, even though they look identical in an audit report.

  1. Inventory every finding from your audit, mapped to the specific page and WCAG success criterion it violates.
  2. Triage by impact and exposure, putting transactional pages and high-traffic landing pages ahead of low-traffic archive content.
  3. Build fixes into your next sprint or development cycle rather than treating them as a separate emergency project competing for resources.
  4. Add regression tests so a future redesign or plugin update doesn’t quietly reintroduce a problem you already fixed.
  5. Set a monitoring cadence. A quarterly automated scan paired with manual review after any major site change catches drift before it becomes a pattern.

The DOJ’s own compliance guidance frames this correctly: accessibility works best as an ongoing part of how you build and maintain a site, not a one-time project you close out and forget. That means training whoever writes your content to add alt text by default, holding vendors and developers to accessibility standards in their contracts, and treating a new heading hierarchy check the same way you’d treat a broken link check.

Pro Tip: Build an accessibility checklist into your content management workflow, not just your development one. A blog post with a missing image description undoes a developer’s careful keyboard-navigation fix just as fast as broken code does.

How King Digital Marketing Agency Approaches Website Accessibility

Accessibility work only holds up when it’s built into the site from the ground up, not bolted on after launch. King Digital Marketing Agency treats it that way in every SEO-friendly web design project: proper heading structure, labeled forms, and keyboard-navigable menus from the first wireframe, not a fix-it list handed off after the site goes live.

For a small or medium business, the decision to bring in outside help usually comes down to bandwidth and risk tolerance. If your internal team can run a keyboard test and fix a contrast issue in an afternoon, do it yourself. If you’re staring down a backlog of findings across dozens of pages, or your checkout flow is the piece generating legal exposure, that’s the point where an agency engagement with clear deliverables, a scoped audit, prioritized fixes, and a maintenance plan, starts paying for itself.

Treating website accessibility as a legal chore misses the bigger picture. A site that works for people using screen readers, keyboard navigation, or voice control also tends to work better for everyone else, mobile users on shaky connections, older customers less comfortable with fussy interfaces, anyone trying to get something done quickly. Clean heading structure and clear form labels are good UX regardless of who’s using the site.

I’ve seen businesses treat an accessibility fix as pure legal defense and completely miss that it usually improves conversion along the way. A checkout form with clear error messages helps every customer finish a purchase, not just the ones using assistive technology. The businesses that get ahead of this instead of reacting to a demand letter tend to spend less money and end up with a genuinely better website. That’s the actual argument for acting now, not just the legal one.

— Bernadette

Make Your Website Accessible Without the Guesswork

If you’ve read through that checklist and realized your site needs real work, you don’t have to figure out the remediation order alone. King Digital Marketing Agency is the alternative to hiring a specialized accessibility-only consultant at premium hourly rates: our in-house team builds accessibility directly into SEO-friendly web design projects and ongoing website hosting and maintenance, so you get one point of contact instead of juggling a developer, an SEO consultant, and a separate accessibility auditor.

King Digital Marketing Agency

Some agencies work with small and medium businesses needing sites that pass both an accessibility review and a Google ranking check, without locking clients into long-term contracts or withholding account access if they decide to move on. If your current site has never had a real accessibility pass, reach out through our website and start with a straightforward conversation about where your site stands today.

Sources

FAQ

Are Websites Legally Required to Be ADA Compliant?

Businesses that qualify as public accommodations under Title III must provide equal access on their websites, based on longstanding DOJ guidance. State and local government entities face an explicit requirement under the 2024 Title II rule, which sets WCAG 2.1 Level AA as the binding technical standard with defined compliance dates.

What Are the New ADA Requirements for Websites?

The newest concrete requirement comes from the DOJ’s 2024 Title II rule, which requires state and local government websites and mobile apps to conform to WCAG 2.1 Level AA. Private businesses under Title III don’t have a codified technical standard yet, but courts and regulators consistently point to the same WCAG 2.1 AA benchmark.

How Can I Check if a Website Is ADA Compliant?

Start with a full-site automated scan to catch structural issues, then run manual keyboard-only navigation on your critical pages and spot-check with a screen reader like NVDA or VoiceOver. Automated tools alone catch only a portion of real issues, so a hybrid testing approach is the only reliable way to know where you stand.

Can I Be Sued if My Website Is Not ADA Compliant?

Yes. Private lawsuits under Title III are the primary enforcement path for businesses, and courts have repeatedly supported the position that a public-facing website tied to a business’s services must provide equal access, as seen in cases like Winn-Dixie. There’s no federal certificate that shields you from a claim; the strongest defense is an accessible site backed by a documented testing and remediation process.

Author