ADA Website Compliance Checklist for Small Businesses in 2026

If you run a small business with a website, ADA compliance is not optional. The law applies to you the same way it applies to Fortune 500 companies. The difference is that you probably do not have a compliance team or a six-figure budget for remediation.

The good news: most small business websites have a limited number of pages, which makes fixing accessibility issues manageable if you know what to prioritize. This checklist covers the 15 most critical items, ordered by the frequency they appear in ADA lawsuits and demand letters.

The Legal Landscape for Small Businesses

According to Seyfarth Shaw's ADA Title III lawsuit tracking, 8,667 ADA lawsuits were filed in federal court in 2025. A growing share target websites specifically.

Small businesses are disproportionately targeted by serial plaintiffs because they lack the legal resources to fight in court and tend to settle quickly. The average settlement range is $5,000 to $75,000 according to data compiled by Accessible.org, but attorney fees can double or triple that amount.

The DOJ's April 2024 final rule under ADA Title II set specific WCAG 2.1 AA compliance deadlines for government websites. While Title III (private businesses) does not yet have a specific technical standard codified in regulation, courts routinely use WCAG 2.1 and 2.2 AA as the benchmark.

The 15-Point ADA Compliance Checklist

Priority 1: Critical (Fix These First)

These violations appear in the majority of ADA lawsuits and are the easiest for plaintiffs to demonstrate.

1. Add alt text to every image Every element needs a descriptive alt attribute. Decorative images should use alt="" (empty alt) so screen readers skip them. This is WCAG 1.1.1 and the single most common violation cited in ADA complaints. 2. Ensure sufficient color contrast Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). Light gray text on white backgrounds is the most common failure. Check your entire site with a contrast tool. This is WCAG 1.4.3. 3. Label all form fields Every input, select, and textarea needs an associated element or aria-label. Placeholder text alone is not sufficient. This is WCAG 1.3.1 and 4.1.2. 4. Set the page language Add lang="en" (or the appropriate language code) to your element. Screen readers use this to determine pronunciation. This is WCAG 3.1.1 and takes five seconds to fix. 5. Make all links and buttons descriptive Links that say "click here" or "read more" are not descriptive enough for screen reader users who navigate by links. Empty links (no text content) are even worse. This is WCAG 2.4.4.

Priority 2: High (Fix These Next)

6. Ensure full keyboard navigation Every interactive element must be reachable and operable using only the Tab key, Enter, and arrow keys. Test by unplugging your mouse and tabbing through your entire site. This is WCAG 2.1.1. 7. Add a visible focus indicator When users tab through your site, they need to see which element is currently focused. If your CSS removes the default focus outline (outline: none) without replacing it, keyboard users cannot navigate your site. This is WCAG 2.4.7. 8. Use proper heading hierarchy Headings should follow a logical order: H1, then H2, then H3. Do not skip levels (H1 to H3) or use heading tags for visual styling. Screen reader users navigate by headings to understand page structure. This is WCAG 1.3.1. 9. Add skip navigation links Include a "Skip to main content" link at the top of every page so keyboard users can bypass the navigation menu. This is WCAG 2.4.1. 10. Ensure video has captions All video content needs synchronized captions. Auto-generated captions from YouTube are a starting point but often contain errors that need manual correction. This is WCAG 1.2.2.

Priority 3: Important (Address These Proactively)

11. Make error messages clear and specific Form validation errors must identify which field has the problem and describe the error in text. "Invalid input" is not sufficient. Say "Email address must include an @ symbol." This is WCAG 3.3.1 and 3.3.3. 12. Ensure target sizes are adequate Touch and click targets should be at least 24x24 CSS pixels. Small links and tiny buttons are difficult for users with motor impairments. This is WCAG 2.5.8, new in version 2.2. 13. Do not use color alone to convey information If you use red to indicate required fields or green to indicate success, you must also use text, icons, or patterns. Colorblind users cannot distinguish color-only indicators. This is WCAG 1.4.1. 14. Ensure tables have proper markup Data tables need elements for headers and scope attributes to associate headers with data cells. Layout tables should be avoided entirely. This is WCAG 1.3.1. 15. Test with a screen reader Spend 15 minutes navigating your own site with a screen reader. NVDA is free for Windows. VoiceOver is built into macOS and iOS. This reveals issues that automated tools cannot detect.

How to Prioritize

Not every page carries equal risk. Focus your remediation effort here first:

• Homepage: This is the page plaintiffs test first
• Contact page: If someone cannot submit your contact form, that is a clear barrier
• Product/service pages: These are the core of your business
• Checkout/payment pages: Inaccessible checkout is a direct barrier to commerce
• Any page with forms: Forms are where the most violations cluster

What About Overlay Widgets?

Overlay widgets (like accessiBe, AudioEye toolbar mode, or UserWay) add a toolbar to your site that lets users adjust font size, contrast, and other settings. They do not fix the underlying accessibility problems in your HTML.

The National Federation of the Blind's statement on overlay widgets specifically condemns this approach. Multiple courts have found that sites using overlays still violate the ADA. The overlay fact sheet signed by hundreds of accessibility professionals explains why overlays fail in detail.

Fix the actual code. It is more work upfront, but it is the only approach that holds up legally.

Document Everything

Courts look at whether you made a good-faith effort to comply. Keep records of:

• Your initial audit results and score
• Each violation you fixed and when
• Your ongoing monitoring plan
• Any manual testing you performed

This documentation can be the difference between a quick resolution and a prolonged legal fight.

Start Your Audit Now

Run a free scan with OnePageAudit to see your current ADA compliance score. You will get a list of every violation on your page, mapped to specific WCAG criteria, with fix instructions. Takes under 60 seconds, no account required.

For a complete assessment with a downloadable PDF report documenting your compliance status, get a full audit report that you can share with your legal team or web developer.

Related reading:

• ADA Compliance Checker: How to Test Your Website
• WCAG 2.2 Requirements: What Your Website Needs
• How Much Does an ADA Lawsuit Cost?