Introduction
Accessibility is the practice of designing products so that people with disabilities, including visual, auditory, motor, cognitive, and situational impairments, can perceive, understand, navigate, and use them. It is a legal requirement in many markets, a standard with a name (WCAG), and a research discipline of its own, because the only reliable way to know whether a product works with a screen reader or a switch is to test it with someone who uses one. This article covers what accessibility requires, the standards that define it, and how to build accessibility research into a program that otherwise tests only for the majority.
What is Accessibility?
Accessibility is the degree to which a product can be used by people across the full range of human abilities, including those with permanent disabilities (blindness, deafness, limited mobility, cognitive and learning disabilities), temporary ones (a broken arm, an eye infection), and situational ones (bright sunlight, a noisy room, one hand holding a child). The international standard is the Web Content Accessibility Guidelines (WCAG), maintained by the W3C, organized around four principles: content must be perceivable, operable, understandable, and robust, with testable success criteria at levels A, AA, and AAA. Legislation in many jurisdictions (accessibility laws in the EU, the US, the UK, and elsewhere) references these standards, and the practical bar for most products is WCAG AA. Accessibility is not a feature added for a minority; a large share of any user base has some relevant impairment, and designs that work for assistive technology tend to work better for everyone.
What It Requires in Practice
Perceivable. Text alternatives for images, captions and transcripts for media, sufficient color contrast, content that doesn't rely on color alone, and layouts that reflow at high zoom.
Operable. Everything reachable and usable by keyboard alone, visible focus indicators, no traps, enough time, no seizure-triggering flashes, and touch targets large enough for imprecise motor control.
Understandable. Clear language, predictable navigation, consistent patterns, labeled form fields, and error messages that say what went wrong and how to fix it, the micro-copy discipline with higher stakes.
Robust. Semantic markup and correct use of ARIA so that assistive technologies (screen readers, switch controls, voice control, magnifiers) can interpret the interface.
Researching Accessibility
1. Audit first, test second.
Automated checkers and a manual expert review against WCAG catch the mechanical failures (contrast, missing labels, keyboard traps) quickly; they miss most of what makes an experience unusable, which only testing reveals.
2. Recruit participants who use assistive technology.
Screen reader users, keyboard-only users, people with low vision, motor impairments, and cognitive disabilities, recruited as the audience they are, with screeners on the technology and the tasks they do, and paid for their expertise. Remote unmoderated formats matter here: participants on their own devices with their own configured assistive technology (the setup a Ballpark study leaves untouched) produce far more realistic sessions than a lab with unfamiliar equipment.
3. Run real tasks, and let the recording show the work.
The same scenarios as any usability test; the sessions reveal where a flow breaks for a screen reader (an unlabeled button, a modal that traps focus, a custom control that announces nothing), and the participant's narration explains what they expected.
4. Include accessibility in every study, not a separate one.
A recurring slot for assistive-technology users in ordinary usability rounds normalizes the practice and catches regressions; a single annual accessibility audit finds last year's problems.
5. Measure and track.
Task success and effort for assistive-technology users alongside the general population, as UX metrics reported by segment; the gap is the accessibility debt, made visible.
The Common Failures
Treating an automated scan as compliance. Testing only with sighted, mouse-using participants and declaring the product accessible. Retrofitting at the end, when structural fixes are expensive. Building custom components that look right and announce nothing. And confusing legal compliance with usability: a product can pass WCAG AA and still be exhausting to use with a screen reader, which is why the standard is the floor and the research is the measure.
What to Remember
Accessibility means people across the range of abilities can perceive, operate, understand, and rely on a product, to the standard WCAG defines and the law increasingly requires. Audit for the mechanical failures, then test with participants who use assistive technology, on their own setups, with real tasks, in every round rather than once a year, and track the gap. Compliance is checked by a tool; accessibility is proven by a person.
Further reading
For standards and practice:
Articles:
1. Introduction to Web Accessibility - W3C Web Accessibility Initiative
The authoritative starting point: what accessibility is, why it matters, and how WCAG is organized.
2. Introduction to Web Accessibility - WebAIM
A practical, plain-language guide to disabilities, assistive technologies, and accessible design.
3. The A11Y Project
A community-driven checklist and resource library for accessible development.