accessibility
Designing and building products so that people with disabilities, including those who use keyboards, screen readers or magnifiers, can use them fully.
In more detail
On the web, accessibility is measured against WCAG. It covers perceiving content (contrast, text alternatives), operating it (keyboard, enough time), understanding it and robust markup that assistive technology can read. A design system that builds it into its primitives makes every product that uses them more accessible.
Examples
In the browser: Accessibility starts with semantic HTML and correct ARIA, keyboard support and visible focus, and respects user settings such as reduced motion. a11y is a short form: 11 letters sit between the a and the y.Role-based Playwright locators find the same elements a screen reader announces.Headless React components exist largely to package this behaviour so it is not rebuilt, and broken, in every project.Related terms
- WCAG — The Web Content Accessibility Guidelines, the W3C standard that defines testable requirements for making web content accessible.
- ARIA — The W3C standard of HTML attributes, such as role and aria-expanded, that tell assistive technology what a custom widget is and what state it is in.
- screen reader — Software that reads the screen aloud or sends it to a braille display, used mainly by blind and low-vision people.
- assistive technology — Hardware or software that helps disabled people use computers, such as screen readers, magnifiers, switch devices and voice control.
- semantic HTML — Using HTML elements for their meaning, such as <button> for actions and <nav> for navigation, rather than generic <div>s.
- accessibility tree — A simplified version of the DOM tree that the browser builds for assistive technology, listing each element's role, name and state.
- UX — User experience: how easy, fast and pleasant an application feels to use.
- keyboard navigation — Using a page entirely with the keyboard: Tab to move between controls, Enter and Space to activate, arrow keys inside widgets, Escape to close.
Taught in
- Modern Color Spaces: OKLCH, Gamut Mapping & APCA Contrast — Design Systems & Component Engineering
- Headless Architecture: State vs Presentation Separation — Design Systems & Component Engineering
- WAI-ARIA Semantics: Roles, States & Accessible Name Computation — Design Systems & Component Engineering
- Automated Accessibility Testing: axe-core & Testing Library — Design Systems & Component Engineering
- Visual Contrast Auditing: Color Blindness & Reduced Motion — Design Systems & Component Engineering
- Semantic HTML Elements: Landmarks And Structure — Frontend Architecture & Web Platform
- Accessibility Tree, ARIA Roles, States And Live Regions — Frontend Architecture & Web Platform
- Pointer Events, Focus Trapping And Keyboard Accessibility — Frontend Architecture & Web Platform
- Modern CSS Animations, Transitions And View Transitions API — Frontend Architecture & Web Platform
- End-to-End Testing with Playwright: Multi-Tier Suites — Production Full-Stack Engineering
- Route Groups & Private Folders: Modular Structures — Next.js 15 & Modern App Router Architecture
- Action State: useActionState & Optimistic Form UI — Next.js 15 & Modern App Router Architecture
- Compound Components: Inversion of Control with Context — React 19 & Modern Component Architecture
- Slot Patterns And Headless UI Architecture in React — React 19 & Modern Component Architecture
- Creating Event Listener Hooks with Clean Teardown Logic — React 19 & Modern Component Architecture
- useId: Generating Stable Accessible Form Element Identifiers — React 19 & Modern Component Architecture
- Virtualization: Rendering Infinite Datasets Efficiently — React 19 & Modern Component Architecture
- Accessible Headless Primitives: ARIA, Focus, And Keyboard — React 19 & Modern Component Architecture