Web accessibility means websites work for everyone, including people with disabilities

Web accessibility is the practice of building and maintaining websites so that people with disabilities can use them the same way anyone else can. A person who is blind should be able to read your site with a screen reader. Someone with limited hand mobility should be able to navigate using only a keyboard. A person who is deaf should be able to understand video content through captions. A person with color blindness should be able to tell buttons apart without relying on color alone.

Accessibility is not a separate feature bolted onto a website. It is built into how the site is coded, designed, and written from the start. When done well, it is invisible — the site simply works. When done poorly, entire groups of people cannot use it at all.

Key Takeaways

  • Web accessibility means people with disabilities can navigate, read, and interact with websites using whatever tools or methods they need.
  • Accessible websites use semantic HTML, keyboard navigation, text alternatives for images, captions for video, and sufficient color contrast so text is readable.
  • The Web Content Accessibility Guidelines (WCAG) set the technical standards that most countries and organizations follow.
  • Accessibility benefits everyone: captions help people in loud environments, keyboard navigation helps people with tremors or arthritis, and clear writing helps people learning a language.

How people with different disabilities use the web

A person who is blind typically uses a screen reader — software that reads aloud everything on the page, from text to button labels to form instructions. The screen reader user navigates by pressing keys to jump between headings, links, and form fields. If a website has no headings, or if images have no text descriptions, the screen reader user gets no information.

A person with low vision might use a screen magnifier to zoom in on part of the page, or they might increase the text size in their browser. If the website is built rigidly and does not reflow when text gets larger, content disappears off the edge of the screen or overlaps.

A person with limited hand mobility might not be able to use a mouse. They navigate using only the keyboard — pressing Tab to move between interactive elements and Enter to activate them. If a website requires a mouse (for example, a dropdown menu that only opens on hover), that person cannot use it.

A person who is deaf cannot hear audio or video. They need captions — a text transcript of what is being said — and ideally a description of important sounds (like "[door slams]" or "[phone ringing]"). A person with hearing loss might use captions even if they can hear some sound.

A person with dyslexia or a cognitive disability might struggle with dense text, poor contrast, or confusing layouts. Clear writing, good spacing, and simple navigation help them understand what the page is for.

The technical standards: WCAG and what they cover

The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility. They are maintained by the World Wide Web Consortium (W3C), a nonprofit that sets web standards. Most countries, states, and large organizations follow WCAG when they set their own accessibility rules.

WCAG has three levels: A (basic), AA (standard), and AAA (strict). Most organizations aim for AA, which covers the most common barriers without requiring extreme effort. WCAG 2.1 is the current version, and WCAG 3.0 is in development.

The guidelines are organized around four principles: Perceivable (people can see or hear the content), Operable (people can navigate and use it), Understandable (people can comprehend it), and Robust (it works with assistive technology). Under each principle are specific criteria — for example, "images must have text descriptions" or "buttons must have a visible focus indicator when you tab to them".

What accessible websites actually look like

An accessible website has semantic HTML — headings marked as <h1>, <h2>, not just styled text. It has alt text on every image that describes what the image shows. It has captions on videos and transcripts for podcasts. Form fields have labels so a screen reader knows what each field is for.

Colors are not the only way to convey information. A form might show required fields in red, but also with an asterisk or the word "required". A chart might use different colors for different lines, but also different patterns or labels. Text has enough contrast with the background — at least 4.5 to 1 for normal text, higher for smaller text.

The site works with keyboard alone. You can tab through all interactive elements in a logical order. Buttons and links have a visible focus indicator so you know where you are. Dropdown menus open and close with the keyboard. There are no keyboard traps — places where you get stuck and cannot tab away.

The site is responsive and reflows when you zoom in or increase text size. Nothing breaks or becomes unusable. Links have descriptive text — "read the full report" instead of "click here" — so a screen reader user knows what they are clicking before they click it.

Who is required to make their website accessible

In the United States, websites run by government agencies must follow Section 508 of the Rehabilitation Act, which requires WCAG AA compliance. Websites run by public schools and universities must also be accessible under Title II of the Americans with Disabilities Act (ADA). Many states have their own accessibility laws that apply to state agencies and sometimes to private businesses.

Private companies are not federally required to be accessible, but they can be sued under the ADA if their website is the primary way they do business and it excludes people with disabilities. Courts have increasingly ruled that the ADA applies to websites. Some states and cities have passed their own laws requiring private business websites to be accessible.

Beyond legal requirements, many organizations make their websites accessible because it is the right thing to do, and because accessible sites often perform better in search engines and work better on mobile devices.

Accessibility benefits people without disabilities too

Captions on videos help people watching in a loud coffee shop or a quiet office where they cannot play sound. They also help people learning English as a second language. Keyboard navigation helps people with arthritis or tremors who find a mouse difficult to control. Clear, simple writing helps everyone understand the page faster.

Transcripts of podcasts let people search for a specific topic and find the exact moment it was discussed. Text descriptions of images help people on slow internet connections where images take time to load. Responsive design that works on phones and tablets is accessibility in disguise — it is the same principle of making content work in different contexts.

Good color contrast makes text easier to read in bright sunlight. Logical heading structure helps people skim the page quickly. Large, easy-to-click buttons help people with any kind of hand tremor or imprecision, not just people with disabilities.

How to check if a website is accessible

You can test a website yourself without special tools. Turn off images in your browser and see if the page still makes sense — if not, images are missing alt text. Try navigating using only the keyboard: press Tab to move through the page and see if you can reach every button and link. Try zooming in to 200 percent and see if the layout breaks.

Use your browser's built-in color contrast checker or a free tool like WebAIM's Contrast Checker to see if text is readable. Listen to a video and check for captions. Read the page aloud using your browser's reader or a screen reader like NVDA (free, for Windows) or VoiceOver (built into Mac and iOS).

For a formal audit, organizations use automated tools like Axe, Lighthouse, or WAVE to scan for common problems. These tools catch about 30 percent of accessibility issues. The rest require human testing with real assistive technology and real people with disabilities.

Frequently Asked Questions

Is accessibility the same as usability?

No. Usability means a website is easy to use for anyone. Accessibility means it works for people with disabilities. A website can be usable but not accessible — for example, a site with beautiful design but no keyboard navigation. A site can be accessible but not usable — for example, a site that works with a screen reader but has confusing navigation. Both matter.

Does making a website accessible cost a lot of money?

It depends on the website's age and how it was built. A new website built with accessibility in mind from the start costs little extra — it is just a different way of working. An old website with thousands of pages and no alt text on images costs more to fix. Most organizations find that fixing the biggest barriers — missing alt text, poor color contrast, broken keyboard navigation — takes weeks or months, not years.

Can automated tools make a website fully accessible?

No. Automated tools catch obvious problems like missing alt text and low contrast, but they cannot understand whether an image description is actually accurate, or whether a form is confusing to use. About 30 percent of accessibility issues require a human to find and fix. The best approach is to use automated tools regularly and also test with real people using assistive technology.

What is the difference between WCAG A, AA, and AAA?

WCAG A is the basic level — for example, images must have some kind of text alternative. WCAG AA adds stricter requirements — for example, text must have 4.5 to 1 contrast with the background. WCAG AAA is the highest level and requires things like 7 to 1 contrast and audio descriptions for all video. Most organizations aim for AA because it covers the most common barriers without requiring extreme effort.

Do screen readers work the same way on all websites?

No. Screen readers like NVDA, JAWS, and VoiceOver read the code of the website, so if the code is poorly written, the screen reader cannot help. A screen reader user might hear "button" with no label, or a list with no structure, or links that say "click here" with no context. Good code makes the screen reader's job easier and the user's experience better.