Design Core B · Official guidance

Accessibility

Accessibility helps people with different abilities understand and use a product.

See how it works
You might call it a11yinclusive design

See how it works

Original worked exampleAccessibility

Another example

A form works with a keyboard, screen reader, zoom, and voice input. Its errors are also easy to fix.

Main parts

  1. 01Foundation or token
  2. 02Applied component
  3. 03Visible state and rule

Use it when

Plan it from the first flow and component choice, not as a final fix.

Do not use it when

Never treat a passed automated check as proof. Test with people and real assistive tools too.

Name used in code

WCAG / semantic HTML / ARIA

Before you ship

Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience.

Request you can copy

Outcome: Use or define Accessibility to make the visual experience clear and easy to use. User context: A form works with a keyboard, screen reader, zoom, and voice input. Its errors are also easy to fix. Design concept to apply: Accessibility. Why it fits: Plan it from the first flow and component choice, not as a final fix. Do not use it when: Never treat a passed automated check as proof. Test with people and real assistive tools too. Design requirements: Set the content order, shared design values, and reusable components. Define how the layout changes by screen size and state. Keep useful design choices separate from decoration. Inclusion and resilience: Check contrast, zoom, languages, themes, and reduced motion when needed. Do not use color or effects as the only way to show meaning. Acceptance criteria: The design stays clear on phones and desktops, at zoom, in every theme, and in all supported languages. Interactive states stay clear and consistent. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Brand limits, amount of content, supported themes and languages, target devices, and design-system rules.

Check this request

Review the current use of Accessibility. Definition: Accessibility helps people with different abilities understand and use a product. Release checks: Check content order, shared design values, component consistency, contrast, zoom, and layout changes by screen size. Verify every theme, language, and state. If there is motion, offer an equal reduced-motion experience. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

B
How official is this term?

Official guidance

The named platform, framework, project, or expert group has an official guide for this term.

It is official for that source. Other platforms or teams may use the term in another way.

Scope
Web accessibility
Document status
recommendation
Checked on
2026-07-30

Evidence sources & scope

Authority source · W3C · recommendation Web Content Accessibility Guidelines (WCAG) 2.2 Scope: Web accessibility conformance Role here: Authority within stated scope Source covers: accessibility, usage guidance, avoidance guidance Authority source · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 Scope: Web accessibility semantics Role here: Authority within stated scope Source covers: canonical name, definition, semantics, implementation

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.