6 Accessibility and Inclusive Design
Learn how accessibility and inclusive design reduce barriers in digital products, apply the POUR principles, and guide design, evaluation, and testing.
and inclusion
enables people with disabilities to perceive, understand, navigate, and interact with digital products. takes a broader view, accounting for human diversity—including ability, age, language, culture, technology, and context—to support participation by more people.
The two ideas overlap, but inclusion does not replace . A product can appear welcoming while still containing barriers that prevent disabled people from using it. Designing for varied situations can benefit many users, while must continue to address the specific barriers disabled people encounter.
Users, needs, and contexts
Needs vary among individuals and can change over time. One person might use a screen reader, keyboard, voice input, captions, or magnification. Someone else might face a temporary limitation or use a device in bright sunlight or a noisy room.
Consider this range of needs when designing, without assuming that one person's experience represents everyone. Adaptability can benefit people in different circumstances, but it does not remove the need to address disability-related barriers.
The four principles of
The W3C Web Content Guidelines (WCAG) organize requirements under four principles, collectively called .
: Present information in ways users can sense. Provide text alternatives for meaningful images, captions for spoken audio, and sufficient contrast. Do not use color alone to communicate meaning; for example, label an error field as well as marking it in red.
: Ensure people can use controls and navigation. Make functionality available from a keyboard, keep focus visible and orderly, and provide enough time to complete tasks. Do not make dragging the only way to move an item; offer buttons or another alternative.
: Use clear content and predictable behavior. Label form fields, give instructions before they are needed, and explain errors with a useful way to correct them. Avoid unexpected changes when someone selects a control.
: Build content to work reliably with browsers and . Use semantic structure and standard controls so, for example, a screen reader can identify a button as a button and communicate its name and state.
WCAG criteria and their limits
provides testable success criteria at Levels A, AA, and AAA. These criteria offer a practical baseline for web . Meeting them does not by itself guarantee that every user can complete every task.
in practice
Make part of the process from the start rather than treating it as a final repair. A useful process considers who may be excluded, provides flexible interactions, makes content and controls clear, involves disabled people, and evaluates designs using multiple methods.
Identify who may be excluded. Consider sensory, motor, speech, and cognitive needs, as well as devices, environments, and language. Examine tasks for barriers. For instance, a sign-in process that depends only on recognizing a distorted image may block some users.
Offer flexible ways to interact. Support keyboard use, touch, and . Provide alternatives when an interaction depends on one ability, such as hearing audio or performing a precise gesture.
Make content and controls clear. Use descriptive headings, meaningful link text, visible focus, consistent layouts, and plain-language instructions. Keep interfaces adaptable to text enlargement and different screen sizes.
Include disabled people in research and testing. Invite people with varied abilities to review early designs and try realistic tasks using their usual tools. Ask about the barriers they encounter; do not assume one person represents everyone.
Combine evaluation methods. Automated checks can detect some technical issues, but cannot establish that an experience is or usable. Pair them with manual checks, such as keyboard navigation and screen-reader review, and task-based sessions with disabled participants. Fix barriers and test again.
Evaluating the experience
and usability reinforce each other, but a general usability review may miss barriers tied to disability or assistive technology. Including criteria and disabled participants in design and evaluation helps teams assess both technical access and the actual experience of using a product.