Written by the AX4E accessibility team. Checked against the primary sources listed at the end of this page (W3C, U.S. Department of Justice, ISO and others). Last reviewed November 4, 2026. Read how we write and review guides in our editorial standards.
If a customer cannot complete a purchase because a button has no label, or a parent cannot read a school newsletter because it is a scanned image, the problem is not the person. It is the design. Digital accessibility is the practice of removing those barriers before anyone hits them.
Who it is for
More people than most organizations assume. The CDC estimates that more than one in four adults in the United States has some type of disability. That includes people who are blind or have low vision, people who are Deaf or hard of hearing, people with motor disabilities who cannot use a mouse, and people with cognitive, learning or neurological disabilities.
It also includes a much larger group that does not identify as disabled: older adults whose vision is changing, someone with a broken wrist, a commuter reading in bright sun, a person watching a video without sound. Accessible design works better for all of them.
The four principles behind the standard
The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the international reference for accessible digital content. Every requirement in WCAG falls under four principles, often shortened to POUR:
- Perceivable. People can take in the content: text alternatives for images, captions for video, enough color contrast to read.
- Operable. People can use it: everything works with a keyboard, nothing traps focus, people have enough time.
- Understandable. People can follow it: clear language, predictable navigation, helpful error messages.
- Robust. It works with assistive technology: clean, standard code that screen readers and other tools can interpret.
WCAG has three conformance levels: A, AA and AAA. Level AA is the level most laws, policies and procurement contracts point to. The current version is WCAG 2.2.
Where most sites stand today
Not well. WebAIM's 2026 study of the top one million home pages found detectable WCAG failures on 95.9% of them, with an average of 56 errors per page. The most common problems are not exotic:
| Issue | Share of home pages (2026) |
|---|---|
| Low-contrast text | 83.9% |
| Images missing alternative text | 53.1% |
| Form fields missing labels | 51.0% |
| Empty links | 46.3% |
| Empty buttons | 30.6% |
| Missing page language | 13.5% |
Those six issues are fixable, most of them in the content and templates your team already manages. That is good news: a lot of accessibility progress comes from a short list of habits.
It is more than websites
Accessibility covers every digital touchpoint: websites, web apps, mobile apps, PDFs and other documents, video, email, kiosks and the software your staff use. Documents are often the biggest backlog. See our guide to PDF remediation.
Why it matters to an organization
- Reach. Accessible sites work for more customers, students, patients and residents.
- Quality. Accessible code tends to be cleaner, faster and better understood by search engines and AI assistants.
- Risk. Laws in the U.S. and abroad expect accessible digital services. See accessibility for businesses.
- Sales. Public-sector and enterprise buyers increasingly ask vendors for accessibility documentation before they sign.
Where to start
- Run an automated scan to see the obvious issues. Understand what a scan can and cannot tell you.
- Try your own site with a keyboard only. Can you reach and use everything? Can you see where you are?
- List your most important tasks and documents: buying, applying, registering, paying, contacting.
- Fix at the source, in templates and content, and test with people who use assistive technology.
Common questions
Is digital accessibility a legal requirement?
In many cases, yes. U.S. courts and the Department of Justice treat the ADA as applying to websites of businesses open to the public, and public entities have a specific federal rule. Other countries, including the EU, have their own laws. The details depend on who you are and where you operate.
What is the difference between WCAG A, AA and AAA?
They are conformance levels. A covers the most basic barriers, AA adds the requirements most laws and contracts reference, and AAA is the highest level, which is not usually required for whole sites.
Can software make a site accessible automatically?
No. Automated tools can find many issues and some tools can adjust a page in the browser, but conformance depends on the underlying content and code. People still need to fix and verify it.
Want a second set of eyes?
Request a free assessment. A real person on our team looks at your site or documents and tells you, in plain language, what to fix first.
Request a free assessment Run a free scan