Marcus Andrey Study
Ler em português Library

UX Foundations · Step 7 · 7 min read

Accessibility fundamentals

About one in six people lives with a significant disability. The four WCAG 2.2 principles, levels A, AA and AAA, the criteria designers own (contrast, focus, target size, labels, headings, alt text), assistive technologies, and the laws that require it.

An entrance with stairs and a ramp. Point at the ramp and the cart rolls up to the door; point at the stairs and it stops at the first step. Illustration: Marcus Andrey, drawn with Hairline (MIT, Lucas Marques).

Accessibility is not a final check; it's a design decision you make from the first sketch. Contrast, focus, target size, labels and headings are chosen by designers long before a developer writes code. If you leave them to the end, they become expensive fixes; if you decide them early, they cost almost nothing and make the product easier for everyone.

What you'll be able to do after reading:

  • Explain what digital accessibility is, and who it's for
  • Name the four WCAG principles and the three conformance levels
  • Check six criteria that designers own, on any screen
  • Describe how people use assistive technologies
  • Know which laws apply, and where to read them

1. Who accessibility is for

The W3C defines web accessibility as making sure that "websites, tools, and technologies are designed and developed so that people with disabilities can use them" (W3C WAI, Introduction to Web Accessibility, updated 2026). That covers auditory, cognitive, neurological, physical, speech and visual disabilities.

It's not a small group. The WHO estimates that "1.3 billion people experience significant disability", which "represents 16% of the world's population, or 1 in 6 of us" (WHO, Disability fact sheet, 7 March 2023). The same W3C page adds older people, people with "temporary disabilities" such as a broken arm, and people with "situational limitations" such as bright sunlight.

Close-up of a refreshable braille display: a row of cells with small raised pins, under a computer keyboard.
A refreshable braille display raises pins to show, one line at a time, the text a screen reader finds. It can only show what the design exposes: real text, labels and headings, not words inside an image. Photo: Eddau (cropped), Wikimedia Commons, CC0.

2. WCAG 2.2: four principles, three levels

The Web Content Accessibility Guidelines (WCAG) are the international standard. WCAG 2.2 became a W3C Recommendation on 5 October 2023, with a small update on 12 December 2024 (W3C WAI, What's New in WCAG 2.2). It added nine success criteria and removed one, 4.1.1 Parsing.

PPerceivable

People can see, hear or feel the content.

Contrast, alt text, captions
OOperable

People can use every control, with any input.

Keyboard, visible focus, big targets
UUnderstandable

People can follow the words and predict what happens.

Labels, clear errors, plain words
RRobust

It works with browsers and assistive technologies.

Real buttons, headings, names
The four principles of WCAG, with what a designer can do for each. Diagram: Marcus Andrey, CC BY 4.0.

Every success criterion has a level (W3C, WCAG 2.2):

Level What it means In practice
A "the minimum level of conformance" Without it, some people can't use the product at all
AA All A and AA criteria The usual target in laws and company policies
AAA All A, AA and AAA criteria Aim for it where you can; W3C does not recommend requiring it "as a general policy for entire sites" (Understanding Conformance)

3. Six things designers own

These are decided in your design file:

Criterion Level What you do
1.4.3 Contrast (Minimum) AA Text at least 4.5:1 against its background; large text (about 24 px, or 18.5 px bold) at least 3:1. 1.4.11 Non-text Contrast asks 3:1 for icons, input borders and focus rings. See Colour and contrast
2.4.7 Focus Visible AA Design a clear focus style for every control. The keyboard focus indicator must be visible
2.5.8 Target Size (Minimum) AA Targets "at least 24 by 24 CSS pixels", or spaced so a 24 px circle around each doesn't touch the next (Understanding 2.5.8). 44 by 44 is the AAA level (2.5.5)
3.3.2 Labels or Instructions A Every input has a visible label; a placeholder that disappears is not a label. See Forms
1.3.1 Info and Relationships and 2.4.6 Headings and Labels A and AA Mark real headings in order (H1, H2, H3) and write headings that describe the section
1.1.1 Non-text Content A Write alt text for meaningful images; mark decorative ones as decorative (W3C, An alt Decision Tree)

Also: 1.4.1 Use of Color (A). Never use colour alone to show an error or a status; add text or an icon.

In WebAIM's 2026 scan of the top million home pages, "95.9% of home pages had detected WCAG 2 failures"; the most common were low contrast text (83.9%), missing alt text (53.1%) and missing form labels (51%) (WebAIM Million, 2026). Designers can prevent all three.


4. How people use assistive technologies

W3C lists the main tools: "screen readers that read aloud web pages for people who cannot read the text", screen magnifiers, speech recognition software and selection switches, plus everyday settings such as larger text and captions (W3C WAI, Tools and Techniques, 2024).

What that means for your design:

  • A screen reader user moves by headings, links and form fields, not by looking. Headings are their table of contents.
  • A keyboard or switch user moves one focusable element at a time, in order. Your layout order must make sense.
  • A magnifier user sees a small part of the screen. Keep a label close to its field and an error close to its cause.
  • Someone who doubles the text size (WCAG 1.4.4 asks that text can be resized up to 200%) needs boxes that grow, not text cut off in fixed heights.

5. The laws (briefly)

  • European Union: the European Accessibility Act (Directive (EU) 2019/882) was adopted on 17 April 2019. Countries had to turn it into national law by 28 June 2022 and apply it from 28 June 2025, for products and services such as e-commerce, banking, e-books, transport and phones (EUR-Lex). Microenterprises providing services are exempt, and some older services have a transition until 2030.
  • Brazil: the Lei Brasileira de Inclusão (Lei nº 13.146, 6 July 2015) makes accessibility "obrigatória" (mandatory) on websites of companies based or represented in the country and of government bodies (art. 63) (Câmara dos Deputados).

Not legal advice. Which rules apply depends on the country, the sector and the company size; ask your legal or compliance colleagues.


6. Common mistakes

  • Leaving accessibility to a final "audit" before launch.
  • Grey text on white "because it looks elegant".
  • Placeholders used as labels.
  • Headings chosen by size, not by structure.
  • Thinking "we have no blind users"; you can't see who leaves.

7. Vocabulary

Term Meaning
WCAG Web Content Accessibility Guidelines, the W3C standard
POUR Perceivable, Operable, Understandable, Robust
Contrast ratio How different two colours are in lightness, from 1:1 to 21:1
Focus indicator The visible mark on the element the keyboard is on
Assistive technology Tools such as screen readers, magnifiers, switches and speech recognition
Alt text A short text that replaces an image for people who can't see it

8. Try it (no tools needed)

  1. Take a screen you designed, or a printed page of any app.
  2. Put your mouse away and imagine moving with Tab: number each control in the order you would reach it. Does the order make sense?
  3. Find every input. Does each have a label that stays visible while typing?
  4. Find every image. Write one line of alt text for each, or "decorative".

Optional, in Figma: run a contrast plugin on the text and icons, and draw a 24 by 24 box over the smallest targets.

Reflection questions: Which of the six criteria would your current product fail first? Which one could you fix in the design system, once, for every screen?


9. If you already practise

  • Put focus states, target sizes and contrast pairs into the design system as tokens and component rules, so each screen inherits them.
  • Annotate your handoff: heading levels, reading order, alt text, labels and focus order. Developers can't guess them.
  • Use your product with a phone screen reader (VoiceOver or TalkBack) for ten minutes a week.

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Inclusive design · Colour and contrast · Forms · What a design system is · Handoff to developers · Accessibility with and for AI

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close