Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 36 ยท UX Fundamentals

Accessibility in UX

Learn why accessibility is part of good UX. Covers disabilities and situations, the WCAG principles, color contrast with a runnable checker, keyboard use and inclusive habits.

Accessibility means that people with a wide range of abilities can use your product. That includes people who are blind or have low vision, who are deaf or hard of hearing, who have motor, cognitive or learning differences, and who are temporarily or situationally limited. Making something accessible is not a bonus feature added at the end. It is part of good UX, and in many countries also a legal requirement.

Who benefits

Permanent disabilities are only part of the picture. Consider the persona spectrum:

Ability Permanent Temporary Situational
Vision Blind Cataract surgery Bright sunlight on the screen
Hearing Deaf Ear infection Noisy cafe
One arm Amputation Broken arm Holding a baby

Designing for the permanent case often helps everyone: captions, keyboard access, high contrast and large targets are enjoyed far beyond the original audience.

The WCAG principles

The Web Content Accessibility Guidelines (WCAG), published by the W3C, are organized around four principles, often remembered as POUR:

  • Perceivable: information can be perceived. Provide text alternatives for images, captions for video, and enough contrast.
  • Operable: the interface can be used. Everything works with a keyboard, there is enough time, nothing flashes dangerously, and targets are big enough.
  • Understandable: content and behavior are predictable. Clear language, consistent navigation, helpful error messages.
  • Robust: works across browsers and assistive technologies, which means using correct, semantic markup.

WCAG has three conformance levels, A, AA and AAA. Level AA is the usual target in laws and policies.

POUR

Perceivable Can be seen or heard
Operable Works by keyboard too
1 / 2

Color and contrast

Text must stand out from its background. WCAG AA requires a contrast ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text (about 24 px regular or 18.66 px bold) and for important interface components. Never rely on color alone: a red border that signals an error should also have an icon or text.

The ratio uses relative luminance: compute a brightness number for each color, then divide the lighter plus 0.05 by the darker plus 0.05. This stand-in implements the published formula, so it gives real ratios, but it is only a calculator, not a full audit.

JS Contrast checker (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Gray #767676 on white is famous for being just about the lightest gray that passes 4.5 to 1.

Keyboard and screen readers

Many people never use a mouse. Check that:

  • Every interactive element can be reached and used with Tab, Enter, Space and arrow keys.
  • The focus indicator is clearly visible. Never remove the outline without a replacement.
  • The tab order follows the visual order.
  • Pages have headings, landmarks and labels so a screen reader can announce structure.
  • Images have meaningful alt text (empty alt for decoration). Form fields have visible labels.

In HTML, using the right element gives most of this for free: a real <button> is focusable and announced as a button; a <div> with a click handler is neither. See the HTML course for semantics.

Inclusive design habits

  • Test with real assistive technology and, when possible, with people who use it.
  • Write plain language; it helps people with cognitive differences and non-native speakers.
  • Allow zoom and text resizing up to 200 percent without breaking.
  • Provide captions and transcripts for media.
  • Do not time people out without warning and a way to extend.
  • Include accessibility in your definition of done, not as a late audit.

Automated tools catch only a portion of problems (often cited as a minority of issues), so manual checks matter.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What does POUR stand for in WCAG?

    These are the four WCAG principles.
  2. 2. What is the AA minimum contrast ratio for normal text?

    Normal text needs 4.5 to 1; large text needs 3 to 1.
  3. 3. Why should an error not be shown by red color alone?

    Never rely on color alone to convey meaning.
  4. 4. Which HTML choice is best for a clickable action?

    A button is focusable, keyboard operable and announced correctly by default.
  5. 5. Why is accessibility good for everyone?

    Captions, contrast and large targets help in noise, sunlight or with a broken arm.

Summary

  • Accessibility is part of UX and often a legal duty; target WCAG 2.2 level AA.
  • POUR: perceivable, operable, understandable, robust.
  • Contrast: 4.5 to 1 for text, 3 to 1 for large text and components; do not rely on color alone.
  • Support keyboard use, visible focus, semantic markup and screen readers.
  • Build it in from the start and test with real assistive technology.

Next: Research Goals and Questions