Website accessibility and ADA compliance, explained in plain English.
Website accessibility means building your site so people with disabilities can actually use it. In the US there is no separate ADA web standard, so courts and settlements measure sites against WCAG 2.1 Level AA instead. Here is what that requires, where sites fail, and how to fix it.
What website accessibility actually means.
Accessibility is measured against the WCAG, the Web Content Accessibility Guidelines published by the W3C. Its current versions are 2.1 and 2.2, and it defines three conformance levels: A, AA, and AAA. AA is the practical target almost everyone aims for, and it is built on four principles, easy to remember as POUR.
Perceivable
People can perceive the content. Text alternatives for images, captions on video, and enough colour contrast that the words are actually readable.
Operable
People can operate it. Full keyboard access, no keyboard traps, and enough time to complete things like forms and checkouts.
Understandable
Content and controls behave predictably and read clearly. Navigation stays consistent, and errors explain themselves instead of just turning a field red.
Robust
It works with assistive technology like screen readers. That mostly comes down to clean, semantic HTML rather than divs pretending to be buttons.
Why website accessibility matters.
The human one
Around one in four US adults lives with a disability, so this is not a small audience. Get it right and they can read, navigate, and buy from you. Get it wrong and you are quietly turning them away.
The legal one
The Americans with Disabilities Act has been applied to websites, and Section 508 covers federal-related sites. Other regions have their own rules, including the European Accessibility Act, Canada’s AODA, and the UK’s Equality Act.
The business one
Accessible sites tend to be better sites. Clean headings, alt text, strong contrast, and keyboard support also help SEO, mobile users, and anyone reading in bright sunlight or a hurry.
What “ADA compliance” actually requires.
The ADA itself does not publish a technical web standard. WCAG 2.1 Level AA is the benchmark used in practice.
That benchmark shows up in settlements, in Department of Justice guidance, and in expert testimony. If your site meets WCAG 2.1 AA, you are in a strong position. If it does not, that is where the risk sits. So “make my site ADA compliant” and “meet WCAG 2.1 AA” are, for practical purposes, the same job.
One note before going further: this is practical guidance, not legal advice. If you are dealing with a specific complaint or demand letter, talk to a lawyer.
The most common accessibility barriers.
Most failures are not exotic, and most are fixable without rebuilding anything. Our website accessibility checklist walks through each one in detail.
Images without alt text
Screen readers announce nothing useful, or read out a filename like IMG_4821.jpg. Decorative images need empty alt attributes, not missing ones.
Low colour contrast
Light grey text on white is the single most common failure on the web. AA wants 4.5:1 for body text and 3:1 for large text.
Forms without labels
A screen reader user cannot tell what a field wants. Placeholder text is not a label, and it disappears the moment someone starts typing.
No keyboard access
Menus, sliders, or pop-ups that only work with a mouse. If you cannot tab to it and press Enter, a lot of people simply cannot use it.
Poor heading structure
Headings chosen for how big they look rather than what they mean, so the page has no navigable outline for anyone skimming by heading.
Missing focus indicators
Someone navigating by keyboard cannot see where they are on the page. Usually caused by a stylesheet removing outlines and never replacing them.
Video without captions
No captions and no transcript, which locks out deaf and hard-of-hearing visitors and anyone watching with the sound off.
Unlabelled icon buttons
A bare icon for search, cart, or close reads as “button” and nothing else. Icon-only controls need an accessible name in the markup.
None of these need a rebuild.
Almost every item on this list is a content or template fix, not a redesign. That is the part most owners get wrong before they ask for a quote.
Where WordPress sites fail most.
Accessibility guides tend to stay generic. If your site runs on WordPress, the failures cluster in a few predictable places, and knowing them shortens an audit considerably.
Page builder output
Builders nest divs deeply and often output headings as styled text. The page looks fine and has no real outline underneath it.
Sliders and carousels
Auto-advancing sliders move content out from under people who read slowly, and most slider plugins ship without working pause or keyboard controls.
Theme colour settings
Brand colours picked in the customiser for looks, not contrast. Muted greys and pastel accents fail AA constantly, and it is a global fix once caught.
Popups and cookie bars
Modals that do not trap focus properly, cannot be closed with Escape, and leave the page behind them still reachable by keyboard.
Form plugin defaults
Contact form plugins vary a lot. Some ship accessible markup, some rely on placeholders and colour alone to signal a required field or an error.
PDFs treated as content
Menus, price lists, and forms published as scanned PDFs. A PDF is a document, and an image-only one is invisible to a screen reader.
Scanner, audit, or overlay. Only one of these works.
These three get talked about as if they were interchangeable options at different price points. They are not doing the same job, and one of them actively causes problems.
| Automated scanner | WHAT COMPLIANCE ACTUALLY NEEDSManual WCAG 2.1 AA audit | Overlay widget | |
|---|---|---|---|
| What it catches | Contrast, missing alt text, some structure | The full standard, including judgement calls | Nothing. It layers controls on top of the problem |
| Share of WCAG covered | A meaningful minority of criteria | All of it, by a human using the site | Not a testing method at all |
| Catches keyboard traps | Rarely, and never reliably | Yes, because someone tabs through the site | No, and it can introduce new ones |
| Judges alt text quality | No. It only checks the attribute exists | Yes. Wrong alt text is worse than none | No |
| Legal standing | A starting point, not a pass | The evidence settlements are built on | Named in accessibility lawsuits |
| Best used as | A first sweep before the real audit | The actual compliance work | Avoid |
A warning about accessibility overlays.
There is no one-click fix. Real accessibility lives in the site itself.
You have probably seen the widgets that promise instant ADA compliance from one line of code. Be sceptical. Accessibility overlays and toolbars do not make a site compliant, they can interfere with the assistive tech people already use, and a notable share of accessibility lawsuits have named sites that were running one. Screen reader users have been vocal about this for years, which is worth more than any vendor claim.
Not sure where your site stands?
Start with a free website review. We will look at the obvious accessibility barriers alongside everything else, and tell you plainly what needs doing.
How to make your website accessible.
The honest short version is three phases, and the third is the one people skip. Our guide on how to make your website accessible covers the fixes step by step.
Audit against WCAG 2.1 AA
Run an automated checker first to clear the mechanical issues, then test manually with a keyboard and a screen reader. A meaningful part of WCAG can only be verified by a person actually using the site, so treat an automated score as a starting point, not a pass.
Fix in priority order
Start with the barriers that block people entirely: keyboard traps, unlabelled forms, and missing alt text on meaningful images. Contrast and heading structure come next. On a typical small business site this is days of work, not months.
Maintain it
Accessibility is not a one-time project. Every new page, plugin, and design change can introduce fresh barriers, which is why it fits an ongoing maintenance arrangement better than a single audit that goes stale in a quarter.
Choose plugins carefully
On WordPress, some plugins genuinely help and many do not. Our guide to the best WordPress accessibility plugins sorts the useful from the harmful.
Accessibility is ongoing work.
Which is exactly what a subscription team is built for: an initial pass to fix the barriers, then keeping the site compliant as it changes. We handle accessibility fixes as part of website development and support, on a flat monthly fee.
Website accessibility questions.
Get your site made accessible, risk-free.
Start with a free website review to see where you stand, or jump straight in. Every plan is backed by a 7-day money-back guarantee.