What the standard says
Web accessibility means building websites so people with disabilities can use them [1]. That covers visual, hearing, physical, speech, cognitive and neurological disabilities [1]. People who are blind may use screen readers, which speak the text on the screen [2]. People who can’t use a mouse may move through a page with the keyboard or with voice commands, and people with low vision may need to zoom in to enlarge text [2].
The main technical standard is the Web Content Accessibility Guidelines (WCAG), published by W3C, the web’s standards body [3]. Its requirements, called success criteria, are sorted into three levels: A, AA and AAA [3]. The current version is WCAG 2.2, published in October 2023, and W3C encourages using the latest version [3]. Version 2.2 added nine new success criteria, such as larger tap targets and easier sign-in [4].
For businesses open to the public, the Department of Justice has long said the ADA applies to the goods and services they offer online [2]. DOJ’s 2022 guidance says there is no regulation setting detailed technical standards for this, and points to WCAG and the federal Section 508 standards as helpful guidance [2]. It also says businesses have flexibility in how they comply [2].
A separate DOJ rule from April 2024 sets a specific standard, WCAG 2.1 Level AA, but it applies to state and local governments and their agencies, not to private businesses [5]. Businesses that provide services to the public under a government contract may be expected to help meet it [5]. In April 2026, DOJ pushed the rule’s deadlines to April 2027 for larger governments and April 2028 for smaller ones [6].
The common fixes are well known:
Image descriptions. Meaningful images need short alternative text a screen reader can read aloud [2][7].
Color contrast. Regular text should have a contrast ratio of at least 4.5:1 against its background [8]. Don’t use color alone to signal something, like a required field [2].
Form labels. Every field needs a label a screen reader can announce [2][7].
Headings. Real headings let people jump between sections [7].
Link text. Links should say where they go, since screen reader users often browse a list of links [9].
Keyboard access. Every menu, button and form should work without a mouse [2][7].
What you’ll hear
“Install this widget and your site is ADA compliant.”
The appeal makes sense: an add-on sounds easier than fixing the site. DOJ says automated checkers and overlays can be helpful tools, but need to be used carefully, and that a clean report doesn’t necessarily mean everything is accessible [2]. In early 2025 the Federal Trade Commission alleged that one overlay company claimed its product could make any website WCAG compliant when it did not [10]. The FTC finalized a $1 million order against the company that April [11].
You’ll also hear “you’ll be sued any day now.” The legal question is real, which is why DOJ published guidance [2]. The fair version is calmer: accessibility is ordinary website upkeep, and the basic fixes are within reach.
What the numbers say
We couldn’t find a government or standards-body statistic on how many small-business websites have accessibility problems. Here are the numbers that matter:
More than 1 in 4: U.S. adults with some type of disability, according to the CDC [12]. Its source is CDC’s Disability and Health Data System, a national survey of adults; the page doesn’t state the data year.
5.5%: U.S. adults with a vision disability, from the same CDC page [12].
4.5:1: the minimum WCAG contrast ratio for regular text at Level AA; large text needs 3:1 [8].
9: new success criteria added in WCAG 2.2 [4].
Automated scores are a starting point, not a verdict. W3C says evaluation tools can’t check every accessibility issue and that human judgment is required [13]. Google, which makes Lighthouse, says automated tools don’t catch all accessibility errors and lists items to check by hand [14].
What we’ve seen
We haven’t run into this yet.
Putting it together
An automated report like Lighthouse is a useful first look at real, fixable problems. Make the quick fixes, add a manual check, and be wary of any product that promises compliance in one step.
What good looks like
Meaningful images have short, accurate descriptions.
Text is easy to read against its background, and color is never the only signal.
Every form field has a visible label and clear error messages.
Pages use real headings in order, and links say where they go.
The whole site works with a keyboard alone.
New pages get a quick check by hand, not just a tool.
WCAG 2.2 Level AA is the stated target for the site.
Questions for your IT resource
What did the accessibility report flag on our home page, and which items are quick fixes?
Has anyone tried using our site with only a keyboard, or with a screen reader?
Do our contact and quote forms have labels a screen reader can read?
Are we relying on any widget or add-on for accessibility, and what does it actually do?
Do we provide any services to the public under a government contract?
Related learning
Is your website’s software up to date?
Your website is built from software: the platform, its add-ons and the code libraries it loads. Keeping each piece current, removing what you don’t use and backing up first closes the known holes that automated attacks look for.
Who holds the keys to your domain and website?
Your domain registrar, DNS provider and web host each have a login, and whoever holds those logins controls your website and where your email is delivered. Give each one its own strong password, turn on MFA, and know who has access.
How we put together your Free Security Assessment
The Free Security Assessment is a review of what’s already public about your business: your email setup, domain, website, phone listings and anything left open to the internet. We make one ordinary visit to your home page and never scan, log into or test anything.
Related services
Sources
W3C Web Accessibility Initiative, Introduction to Web Accessibility, updated February 3, 2026. (checked 2026-10-08)
U.S. Department of Justice, Guidance on Web Accessibility and the ADA, ADA.gov, March 18, 2022. (checked 2026-10-08)
W3C Web Accessibility Initiative, WCAG 2 Overview, updated September 17, 2026. (checked 2026-10-08)
W3C Web Accessibility Initiative, What’s New in WCAG 2.2, October 5, 2023. (checked 2026-10-08)
U.S. Department of Justice, Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments, ADA.gov, April 8, 2024. (checked 2026-10-08)
U.S. Department of Justice, Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities, interim final rule, April 16, 2026. (checked 2026-10-08)
W3C Web Accessibility Initiative, Easy Checks – A First Review of Web Accessibility, updated March 21, 2024. (checked 2026-10-08)
W3C, Understanding Success Criterion 1.4.3: Contrast (Minimum), updated September 6, 2026. (checked 2026-10-08)
W3C, Understanding Success Criterion 2.4.4: Link Purpose (In Context), updated May 18, 2026. (checked 2026-10-08)
Federal Trade Commission, FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines, January 3, 2025. (checked 2026-10-08)
Federal Trade Commission, FTC Approves Final Order Requiring accessiBe to pay $1 Million, April 22, 2025. (checked 2026-10-08)
Centers for Disease Control and Prevention, Disability Impacts All of Us Infographic, May 5, 2026. (checked 2026-10-08)
W3C Web Accessibility Initiative, Selecting Web Accessibility Evaluation Tools, updated May 13, 2024. (checked 2026-10-08)
Google, Automated accessibility testing, web.dev, updated January 12, 2023. (checked 2026-10-08)
This page is general information, not legal advice. For questions about how it applies to your business, check with your attorney or compliance contact.
How we rate these. Our judgment from real setups, applied the same way on every page. Cost: $ = no new spend or under $25/month · $$ = a modest monthly tool or a short project · $$$ = new hardware, licensing, or a larger project. Effort: Light = one sitting · Moderate = setup plus follow-up over days or weeks · Heavy = planning, testing and staff changes. Outlined marks show how far it can go for some businesses. N/A = doesn’t apply to this topic. Time to fix: how long the first useful step takes, then how long until it’s fully done. Ratings are typical averages, not quotes. Time to fix: the filled dot is when the first useful step lands, the hollow dot is when it’s fully done. Who can do it: highlighted chips are who can reasonably handle it.