An accessible website is one that people with disabilities can see, hear, navigate, and understand, whether they use a mouse, a keyboard, a screen reader, or voice control. In practice, that means meeting WCAG 2.1 Level AA, the standard U.S. law points to. Most of the work is not exotic. It comes down to contrast, text descriptions, labels, structure, and testing.
Most websites still miss the basics. WebAIM’s 2026 study of the top one million home pages found detectable accessibility failures on 95.9% of them, with an average of 56 errors per page. And those are only the errors software can detect.
Who Is Website Accessibility For?
More than 1 in 4 U.S. adults has some type of disability, according to the CDC. That includes people who are blind or have low vision, people who are deaf or hard of hearing, people who can’t use a mouse, and people with cognitive or learning disabilities.
Accessibility also helps people who wouldn’t describe themselves as disabled: someone reading a phone in bright sun, an older customer who zooms in to read, a parent navigating a form one-handed. Clear, well-structured sites work better for everyone, and they tend to perform better in search, too.
What Are the Most Common Accessibility Failures?
Six problems account for the large majority of errors WebAIM found. Here’s what each one is and how to fix it.
1. Low-Contrast Text (83.9% of Home Pages)
Light gray text on white, or white text on a pale brand color, is hard to read for people with low vision and for anyone on a phone outdoors. WCAG requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
The fix: Check your brand colors against the standard before you build. We made this change on our own site, darkening the blue behind our button text so it passes. Small shifts in shade usually keep the brand intact.
2. Images With No Text Description (53.1%)
A screen reader can’t see a photo. It reads the image’s alternative text, or “alt text,” instead. When that text is missing, a blind visitor hears nothing, or a file name like “IMG_4021.jpg.”
The fix: Give every meaningful image a short description of what it shows or does. Mark purely decorative images so screen readers skip them.
3. Form Fields With No Label (51%)
Placeholder text that disappears when you start typing isn’t a label. Without a real label, a screen reader user hears “edit text” and has to guess what goes in the box.
The fix: Every field needs a visible label connected to it in the code. Error messages should say what went wrong and how to fix it, not just turn the field red.
4. Links With No Readable Name (46.3%)
Icon links, like a social media logo or a magnifying glass, often have no text behind them. A screen reader announces “link” and nothing more.
The fix: Give every link and icon a text name a screen reader can announce. Avoid vague link text like “click here” so links make sense out of context.
5. Buttons With No Readable Name (30.6%)
The same problem applies to buttons: menu toggles, carousel arrows, and close buttons built from icons alone.
The fix: Label every button with what it does: “Open menu,” “Next slide,” “Close.”
6. No Page Language Set (13.5%)
Screen readers use the page’s declared language to pronounce words correctly. Without it, English text can be read with the wrong pronunciation rules.
The fix: One line of code in the page template. It’s the easiest fix on this list.
What Do Automated Tools Miss?
Automated checkers are a good start, but they catch only part of the problem. A person has to test:
- Keyboard use. Can you reach and use every link, menu, and form with the Tab key alone, and can you see where you are on the page?
- Screen reader behavior. Do headings, landmarks, and announcements make sense when the page is read aloud?
- Video and audio. Do recordings have accurate captions and transcripts?
- Documents. Are your PDFs tagged so a screen reader can read them in order? Scanned documents usually aren’t readable at all.
- Zoom and reflow. Does the page still work when text is enlarged to 200% or viewed on a narrow screen?
A site can pass an automated scan and still lock out someone who relies on a keyboard to submit a form.
Will an Accessibility Widget Fix My Website?
No. Accessibility widgets and overlays are the toolbar icons that let visitors change text size or contrast. Some promise compliance with a single line of code. They don’t deliver it.
An overlay sits on top of the page. It doesn’t add missing labels to your forms, fix how your menu works with a keyboard, caption your videos, or repair your PDFs. Many people who rely on assistive technology already have their own tools set up, and overlays can interfere with them. Lawsuits have been filed against websites that had overlays installed.
The reliable path is fixing the website itself: the code, the content, and the documents.
Do Private Businesses Need an Accessible Website?
For state and local governments, the answer is a firm yes, with deadlines. The U.S. Department of Justice’s rule under ADA Title II requires WCAG 2.1 AA, starting 04/26/2027 for larger governments and 04/26/2028 for smaller ones and special districts. We cover that rule in detail in The ADA Website Rule: What Tennessee Cities, Counties, and Districts Need to Know.
Organizations funded by the U.S. Department of Health and Human Services face a similar rule under Section 504.
Private businesses don’t have a website rule or a deadline, but website accessibility lawsuits under the ADA continue, and courts have applied the law to business websites. Building to WCAG 2.1 AA is the clearest way to reduce that risk, and it makes the site easier for every customer to use.
How Do You Get Started?
- Run an automated check on your homepage and the pages customers use most.
- Fix the basics first: contrast, alt text, labels, and link and button names.
- Test with a keyboard. Put the mouse away and try to complete your most important task.
- Review your documents and videos.
- Publish an accessibility statement that tells visitors how to report a problem. Ours is an example.
- Build accessibility into every update, so new pages and posts don’t reintroduce old problems.
Gridwell designs and builds ADA compliant websites for organizations across Middle Tennessee, and makes accessibility part of every site we build. If you’d like to know where your site stands, request a free Accessibility Snapshot: a short report on your homepage and key pages, with the top issues to fix in plain English.
Frequently Asked Questions
What makes a website accessible?
A website is accessible when people with disabilities can perceive, navigate, and use it, including with a keyboard, screen reader, or voice control. In the U.S., the working standard is WCAG 2.1 Level AA.
What is the most common website accessibility problem?
Low-contrast text. WebAIM’s 2026 study found it on 83.9% of the top one million home pages.
Can an automated tool tell me if my website is accessible?
Only partly. Automated tools find issues like contrast and missing alt text, but keyboard use, screen reader behavior, captions, and documents need manual testing.
Do accessibility overlays make a website ADA compliant?
No. Overlays change how a page appears but don’t fix the underlying code, forms, video, or documents, which is where most accessibility failures live.
How long does it take to make a website accessible?
It depends on the site’s size, how it was built, and how many documents it has. Many sites can fix the most common issues in weeks. Sites with hundreds of PDFs or older code may be better served by a rebuild.





