A task becomes inaccessible when the interface puts a barrier between a person and their goal. An error shown only in color may be missed; a video without captions may be unusable. Digital accessibility means removing such barriers so people can perceive, understand, and use content and functionality across different abilities, circumstances, and technologies. The problem is the barrier in the product, not a person’s impairment. section 1.1 section 2.1
Needs change with context. Strong contrast helps someone with low vision and someone reading outdoors; captions help a deaf viewer and someone in a noisy room. An accessible web app does not assume one input method, screen size, orientation, or way of viewing content. It can support keyboard use, larger fonts, screen readers, magnification, voice control, and other setups without making accessibility a separate mode. section 1.0 section 1.1
Make status visible beyond color
Suppose a dashboard marks an error only by turning a value red. A person with red-green color blindness may miss it. Add text, an icon, or a pattern so the status is available without relying on color alone. Ask the same question of every essential signal: can someone still recognize it when their viewing conditions or tools change? section 2.1
Build accessibility into ordinary product decisions:
- Define whose tasks must work, including people using keyboards, assistive technologies, larger text, or minimal styling. section 1.1
- Choose semantic, standards-based code and check intended interactions, rather than treating accessibility as a late visual fix. section 1.1 section 1.2
- Share responsibility: requirements, design, implementation, testing, content, and support all affect whether people can complete a task. section 1.2
Table 2.3 User personas with physical access needs. The table summarizes common barriers and the technologies or strategies used to access digital products.
|
Person
|
About
|
Challenges
|
|
Steve
|
Steve is a right-handed student who is recovering from a broken arm. During recovery, Steve is finding it exceptionally hard to complete basic operations, especially since he can only use his left hand for now. Writing essays, managing assignments, and navigating school portals have become frustrating. Dragging files, tabbing through dense forms, and typing with one hand is slowing his progress significantly. Steve is using voice typing to draft essays and increasingly relies on auto-saved form data. Keyboard accessible sites have become critical for Steve's studies.
|
Motor (broken arm)
|
|
Sally
|
Sally is a pediatrician who has recently been diagnosed with Parkinson's. Sally experiences hand tremors that make precise clicking difficult and typing slow and tedious. Tiny buttons or hover-only menus are especially problematic. Furthermore, accidental clicks may result in the unwanted submission of incorrect information. Interfaces that offer larger click areas, undo options, and time flexibility help Sally stay productive with patient records and digital forms. Keyboard-only access is also becoming increasingly useful.
|
Motor (fine-motor control)
|
|
Luna
|
Luna is a data analyst with cerebral palsy and limited fine motor control. Small targets, such as buttons or links, especially when close together, are difficult to use with a mouse or touchscreen. Drag-and-drop tasks can be difficult, and typing can be time-consuming. Luna values websites that are keyboard accessible, support autocomplete in forms, offer timeout extensions, and provide alternatives to certain advanced functionality that relies on fine motor control.
|
Motor (cerebral palsy)
|
These physical-access personas connect motor barriers, such as difficult dragging or dense forms, with the ways people actually navigate and enter information. section 2.1
NOTE: Guidelines provide a common technical reference, not a substitute for thinking about users. WCAG 2.2 organizes testable success criteria under four principles and three conformance levels. Conformance is ongoing: keep checking accessibility as products and content change. The practical goal is straightforward—people should be able to complete their tasks without the interface getting in their way. section 1.7 section 1.0











