A plain-English guide to digital accessibility

What accessibility means

After reading this guide, you'll know what digital accessibility means, which laws may apply to your business, and what to do first. You don't need a technical background to follow it.

Digital accessibility means people can find information and finish tasks on your website, app, or documents, including people with disabilities. A customer needs to be able to book an appointment, read a bill, or ask for help with the tools that work for them.

The W3C introduction to web accessibility explains the idea: design and build websites so people with disabilities can use them. The work lives in the content, the design, and the code.

Why most websites are not there yet

Most barriers are accidents. A photo is uploaded without a useful description. A designer removes the outline that shows which button has keyboard focus. An error message says something went wrong without saying which field.

These problems go unnoticed when a team only checks a page with a mouse at the default text size. Most can be fixed in the page itself. Some need changes to shared components or to a service you buy from someone else.

Start by checking one task your customers need to finish. Our guide to finding and fixing common accessibility barriers explains what to look for and how to check a fix.

The business case

Accessibility helps customers use what you offer, and it gives your team a record of the work it has done. The W3C business case describes benefits including market reach, innovation, and brand reputation. How much you see depends on your product and your customers.

Fewer customers stopped partway

A price too faint to read, a button with no name, or a form that throws away an answer can stop a purchase or an application. Removing the barrier lets the customer carry on. To see the result, test the task again and listen to what customers tell you.

Better answers for buyers

Clearer content and less repeated work

Descriptive headings and image descriptions help people understand a page. Google also uses image descriptions and the content around them to understand images. That is a reason to write useful descriptions, not a promise of higher rankings.

Fixing a shared form component fixes every page that uses it. Checking accessibility in design and content reviews also catches barriers before they ship.

Accessibility is good design

• Captions make speech and important sounds available as text, including when someone can't listen to a video.
• Clear labels tell people what a form asks for before they type.
• Text that stays readable when enlarged works for anyone who needs a closer view.
• Navigation that stays in the same place helps people find the same service again.

Accessibility doesn't dictate a visual style. It asks whether people can understand and use what you designed. Include people with disabilities when you review the experience, because checking against the standard can't tell you everything they run into.

The standard, in plain words

Each requirement has a level: A, AA, or AAA. Meeting AA means meeting every A and AA requirement. The levels are not scores or service packages.

Our WCAG overview explains the principles, versions, and levels with examples. Use the official WCAG 2.2 standard for the exact requirements and exceptions. A law or contract may name a different version, so confirm which one applies before you agree the scope of a review.

What the law expects of you

Whether a law applies depends on where you operate, your sector, and sometimes your size. Do not assume a small business is exempt. Check the law, because some thresholds are low and some laws have none. A WCAG version named in one law also doesn't apply to every organization.

Our accessibility law summaries set out who each law covers:

• In the United States, ADA Title III covers businesses open to the public, whatever their size. Title II covers state and local governments, with deadlines from April 26, 2027. Section 508 covers federal agencies' technology, and the HHS Section 504 rule covers organizations that receive HHS funding.
• In Canada, the Accessible Canada Act covers federally regulated organizations. In Ontario, the AODA requires businesses and nonprofits with 50 or more employees to make their public websites accessible.
• In the European Union, the European Accessibility Act has covered specified products and consumer services since June 28, 2025. The Web Accessibility Directive covers public sector websites and apps.
• In the United Kingdom, read about the Equality Act and the public sector accessibility regulations.
• In Australia, the Disability Discrimination Act covers access to goods and services, including digital services.

How a law is enforced varies as much as who it covers. In the United States, the Department of Justice accepts complaints, and people can also file lawsuits. Ontario checks the compliance reports businesses file and can take enforcement measures, including financial penalties. In the EU, each country sets its own enforcement bodies and penalties. Each summary explains the process and links to the official sources. Check them, and get advice for your situation, before you rely on a deadline or an exemption.

An evaluation records what was found within its scope. It does not guarantee a legal outcome.

The words you will hear

You don't need to memorize these. They help when you talk about the work with a developer or a reviewer:

The accessibility glossary explains these and other terms with examples.

What to do first

Find out where you stand

Choose one important task, such as signing up, buying, booking, or asking for help. Include every step, the error messages, and the confirmation. Follow our practical checks and note where the task stops working.

An automated scan finds some problems. It can't tell whether instructions make sense or whether a task works with assistive technology, so a person needs to check the rest. W3C's evaluation guidance explains how the methods fit together.

Fix what stops people first

Start with barriers that stop people from finishing essential tasks. Check whether a shared component causes the same problem elsewhere. Give each finding an owner and an expected result, and test the fix before you close it.

A small team can keep this in its existing task list. A larger organization also needs to name the teams and suppliers responsible for shared components, documents, and services it buys.

Build it into how you work

Check accessibility when you write content, choose designs, build components, and review releases. Ask about it when you choose outside services, such as booking systems and payment tools. Our guide to how far to take accessibility explains how to organize the work.

Tell people

Keep checking

Content and software change. Test important tasks after updates that affect them, look for problems that keep coming back, and involve people with disabilities. Keep a dated record of what you checked, what you found, and what is still open.

Things people often get wrong

A clean scan means the site is accessible. Tools test only part of the standard. They can't decide whether an image description is useful or whether a task makes sense. Use scans alongside a manual evaluation and what people tell you.

We have to finish everything before we can begin. Find the most serious barriers, assign the work, and improve the product in steps. A plan organizes that work. It does not replace a legal duty or a deadline that applies to you.

Keep learning

• How to find and fix common accessibility barriers: practical checks and examples for your website.
• Know the standard: WCAG: requirements, versions, and what A, AA, and AAA mean.
• How far to take accessibility: choose how far to go and build the work into your team.
• Talk to us about an evaluation: the tasks and questions a review of your product needs to cover.