Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 38 ยท Getting Started

What Is Web Accessibility?

Learn what web accessibility means, who benefits from it, why it matters for every site, and how this course will teach you to build pages that work for everyone.

Web accessibility means building websites and apps so that everyone can use them, including people who are blind, have low vision, are deaf or hard of hearing, have motor or cognitive disabilities, or simply find themselves in a difficult situation such as bright sunlight, a broken trackpad or a noisy train. An accessible page can be perceived, understood, navigated and operated no matter how a person reaches it.

You will often see the short form a11y (an "a", eleven letters, then a "y"). It is only a nickname. This course teaches the real work behind it: writing HTML that carries meaning, designing with enough contrast, supporting the keyboard, and testing with the tools people actually use.

One note before we start. Some examples later in the course use screen readers, browser extensions and operating-system settings. Those cannot run inside the sandboxed editors on this site, so we show them as read-only descriptions, and every runnable example is plain HTML, CSS and JavaScript that you can try right here.

The web was designed to be universal

Tim Berners-Lee, who invented the web, said that its power is in its universality, and that access by everyone regardless of disability is an essential aspect. That is not an add-on. HTML itself is built around it: a <button> is focusable and works with the keyboard, a <label> is read aloud with its field, and an alt attribute gives a picture a spoken name. Most accessibility work is using the platform properly rather than inventing something new.

The same page, two ways of reading it

Both controls look similar and both respond to a mouse. Only the real <button> can be reached with Tab and activated with the keyboard. A screen reader will also announce it as a button, while the styled <span> is just text. That single difference is the heart of this whole course.

Who benefits?

Disability is common and it is not always permanent. Think of three kinds of situations:

  • Permanent: a person who is blind uses a screen reader; a person with one arm uses a keyboard or voice control.
  • Temporary: a broken wrist, an eye infection, a lost pair of glasses.
  • Situational: a parent holding a baby in one hand, a commuter on a loud train, a presenter on a dim projector.

Designing for the permanent case almost always improves the other two. Captions help people in noisy rooms. Good contrast helps people in sunlight. Keyboard support helps power users who prefer not to touch the mouse. This is sometimes called the curb-cut effect: ramps built for wheelchairs also help people with strollers, suitcases and bicycles.

Accessibility helps many people

See Blind and low-vision users
Hear Deaf and hard-of-hearing users
Move Keyboard, switch and voice users
Think Focus, memory and reading needs
1 / 2

Why it matters

There are four honest reasons to care, and they reinforce each other:

  1. People. Roughly one in six people worldwide lives with a significant disability. Excluding them from shops, banks, schools or government services is a real harm.
  2. Law. Many countries require accessible websites, and complaints and lawsuits are increasingly common. You will meet the main laws in the legal chapter.
  3. Quality. Accessible pages are usually cleaner, faster and easier to maintain. Semantic HTML is also what search engines understand best.
  4. Reach. More people can buy, read and sign up, so accessible sites tend to earn more.

Accessibility is not a feature you add last

It is cheap to build in and expensive to retrofit. Fixing a missing label while writing the form takes seconds. Rebuilding a custom drop-down after launch can take weeks. Throughout this course, treat accessibility the way you treat security or performance: a quality of the whole product, checked at every stage.

It is also not only about screen readers, and it is not about a perfect score. No automated tool can promise a site is accessible. Tools catch only a minority of problems, so you will learn to combine automated checks, keyboard testing, screen reader testing and, ideally, feedback from disabled users.

Common myths

  • "Few of our users are disabled." You usually cannot tell, because people who hit barriers leave quietly.
  • "It makes sites ugly." Accessible sites can look any way you like. Contrast and focus styles are design choices, not restrictions on creativity.
  • "A plugin or overlay fixes it." Widgets that promise one-line compliance cannot repair broken markup, and many disabled users report that they get in the way.
  • "Text-only versions are enough." Separate versions go stale and are rarely equal. One good page for everyone is better.

How this course is organised

You will move from the human side (users and assistive technology), to the rules (WCAG), to the building blocks (semantic HTML and ARIA), to the keyboard and focus, and then to colour, media, forms, testing, law and projects. Each lesson has small examples you can run and a short quiz.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the main idea of web accessibility?

    Accessibility means one site that people can perceive, understand, navigate and operate with a wide range of abilities and tools.
  2. 2. Which situation is an example of a situational limitation?

    Situational limits come from the environment, not from a lasting condition. Sun glare makes low contrast hard to read for anyone.
  3. 3. Why does a real <button> beat a styled <span>?

    Native elements come with keyboard support and a role for assistive technology; a span has neither unless you add them yourself.
  4. 4. What does the curb-cut effect describe?

    Like sidewalk ramps that help strollers and suitcases, captions, contrast and keyboard support benefit many users beyond their original audience.

Summary

  • Web accessibility means everyone can perceive, understand, navigate and operate a site.
  • Disability can be permanent, temporary or situational, so the audience is large.
  • Native HTML gives you much of accessibility for free; use it first.
  • Accessibility is cheapest when built in from the start, and no tool can promise it alone.
  • Overlays, text-only versions and "few users need it" are myths to avoid.

Next: Users and Disabilities