- Atlas
- Computer Science
- Accessibility
Accessibility
Accessibility, in human–computer interaction (HCI), is the work of making computing systems usable by people with disabilities—and, by extension, by anyone whose body, senses, or situation fall outside what a designer assumed.
10 frameworks, from 1960 to today · Human Computer Interaction · Computer Science
- Assistive technology 1960-Present
- Universal Design 1985-Present
- Legal and Procurement Compliance 1990-Present
- Participatory and User-Centered Accessibility Research 1990-Present
- Inclusive Design 1994-Present
- Accessibility APIs 1995-Present
- Accessibility Evaluation and Conformance Testing 1999-Present
- Web Content Accessibility Guidelines 1999-Present
- Cognitive Accessibility 2000-Present
- Mobile and Post-Desktop Accessibility 2009-Present
Overview
Accessibility, in human–computer interaction (HCI), is the work of making computing systems usable by people with disabilities—and, by extension, by anyone whose body, senses, or situation fall outside what a designer assumed1. Its central insight is that disability is often produced at the interface: a person is not disabled by blindness or a tremor in the abstract, but by a screen that only shows, a form that only accepts a mouse, a video that only speaks. The field's history is therefore a history of arguments about where the barrier really lies—in the person, in the machine, or in the fit between them—and of the tools, standards, laws, and research methods built on each answer.
Assistive technology and the rehabilitation roots
Before accessibility was a design concern, it was a rehabilitation and engineering one. From the mid-twentieth century, engineers built devices that adapted the world to a disabled individual: prosthetics, hearing aids, braille writers, and, as electronics spread, "assistive technology"—any device or system that increases or maintains the functional capabilities of a person with a disability. Early computer access followed this model. In the 1960s and 1970s, researchers and blind programmers built terminals that drove braille embossers or produced synthetic speech, so that a blind person could read a computer's output. The key move was the "screen reader": software that intercepts what a program would display and renders it as speech or braille.
This model treated the disabled user as someone to be equipped. It produced real gains but also a treadmill: every new application had to be specially adapted, and assistive technology often lagged behind mainstream software. The tension between fitting the person to the machine and fitting the machine to the person runs through everything that follows.
The personal computer and the first accessibility APIs
The spread of graphical user interfaces in the 1980s made the problem acute. A screen reader that could parse a stream of text had no way to describe a window full of icons, menus, and overlapping regions. The solution, developed through the late 1980s and 1990s, was the "accessibility application programming interface" (accessibility API): a layer through which an operating system exposes the structure of its interface—what controls exist, their names, states, and relationships—to assistive software. Microsoft's Active Accessibility, introduced in the mid-1990s, and later platform frameworks such as the Mac OS X accessibility API and the open-source AT-SPI on Linux, let a screen reader ask "what is on screen?" in structured terms rather than guessing from pixels. This architecture—an interface tree that assistive technology can query and, in some cases, drive—remains the backbone of desktop accessibility. It also created a lasting division of labor: platform vendors maintain the API, application developers populate it, and assistive-technology vendors consume it.
The Web and the standards turn
The World Wide Web posed the problem again, and more publicly. A web page's visual appearance is produced by markup and styling that assistive technology cannot see; a blind user's browser needs the underlying structure. Through the late 1990s, the World Wide Web Consortium (W3C) convened its Web Accessibility Initiative, which in 1999 published the Web Content Accessibility Guidelines (WCAG) 1.0. WCAG set out checkpoints organized around making content perceivable, operable, and understandable—for example, requiring text alternatives for images and captions for audio. Later versions, WCAG 2.0 (2008) and 2.1 (2018), reorganized these into four principles (perceivable, operable, understandable, robust) and added criteria for newer problems such as keyboard access to complex widgets and support for touch and small screens. WCAG became the reference standard that laws and procurement rules around the world point to, which is why its wording matters far beyond the web.
Alongside the guidelines grew "accessibility evaluation and conformance testing": the practice of checking whether a system meets the criteria. Automated tools can catch some failures—missing alt text, insufficient color contrast—but the field's practitioners have long insisted that automated checks catch only a fraction of real barriers and that testing with disabled users and assistive technology is necessary. This produced a recurring methodological debate between conformance (does it pass the checklist?) and usability (can a person actually accomplish the task?).
Law, procurement, and the compliance era
Accessibility became a legal obligation in many countries, and law reshaped practice. In the United States, the Americans with Disabilities Act of 1990 and, later, Section 508 of the Rehabilitation Act (strengthened in 1998 and refreshed in 2017) required federal agencies and their contractors to make electronic and information technology accessible. In the European Union, the Web Accessibility Directive (2016) and the European Accessibility Act (2019) set requirements for public-sector and consumer products2. Procurement rules—buyers demanding conformance as a condition of purchase—became one of the most effective levers, because they reached vendors who had no other incentive. The compliance era professionalized accessibility: it created auditors, conformance reports, and remediation projects. It also drew criticism that checkbox compliance could satisfy a standard while leaving real users blocked, a tension the field has never fully resolved.
Universal and inclusive design
A parallel strand came from design rather than engineering. "Universal design," a term coined by the architect Ron Mace in the 1980s and formalized in the 1997 book The Universal Design File by the Center for Universal Design at North Carolina State University, argued that products and environments should be usable by all people, to the greatest extent possible, without adaptation. Its seven principles—equitable use, flexibility, simple and intuitive use, perceptible information, tolerance for error, low physical effort, and appropriate size and space—were aimed at the built environment but were taken up by HCI. "Inclusive design," the term more common in the United Kingdom, made a similar argument with an emphasis on the diversity of users and on designing with rather than for excluded groups. Both approaches pushed designers to treat disability as one point on a spectrum of human variation—temporary injuries, aging, situational limits (a noisy train, a bright sun) all create the same barriers—rather than as a special case. The practical claim was that designing for the edges improves the mainstream: captions help in loud rooms, large touch targets help everyone.
Participatory and user-centered research
A methodological shift accompanied these ideas. Rather than testing accessibility on disabled users at the end, researchers began involving them throughout design. "Participatory design," with roots in Scandinavian workplace democracy movements of the 1970s, and the broader "user-centered design" tradition, were adapted into accessibility research: co-design sessions with blind, deaf, and motor-impaired participants; longitudinal studies of assistive-technology use in daily life; and work documenting how people with disabilities develop sophisticated personal strategies—workarounds, custom scripts, combinations of tools—that designers never anticipated. This research reframed disabled users as experts in their own access needs and exposed how often mainstream systems fail not from missing features but from mismatched assumptions.
Cognitive accessibility and the widening of disability
Early accessibility focused heavily on sensory and motor disabilities, where barriers are relatively easy to specify. "Cognitive accessibility"—designing for people with intellectual disabilities, autism, dementia, dyslexia, attention differences, and memory or learning difficulties—proved harder, because the barriers are less about a missing channel than about complexity, unclear language, unpredictable behavior, and memory load. Work in this area pushed for plain language, consistent navigation, reduced cognitive demand, and support for error recovery, and it connected accessibility to the wider HCI concern with cognitive load. It also forced the field to confront that "disability" is not a fixed list of conditions but a relationship between a person's capacities and a task's demands.
Mobile, touch, and the post-desktop problem
The smartphone reset the problem once more. Touchscreens removed the physical keyboard that many motor-impaired users relied on, and small screens and gesture interfaces created new barriers. In response came platform-level accessibility features—screen readers such as VoiceOver (2009) and TalkBack, switch access, voice control, magnification, and adjustable touch timing—and design guidance for large targets, alternative input, and gesture alternatives. Mobile accessibility also exposed how much accessibility depends on the operating system and on app developers correctly using the platform's accessibility APIs, and it made the field confront devices used in every posture and context, blurring the line between disability accommodation and general usability.
The present
Today accessibility in HCI is a mature, multi-front practice. Standards work continues through WCAG's evolution and through accessibility APIs that now span desktop, web, and mobile3. Evaluation combines automated testing, manual inspection, and testing with disabled users and their assistive technology. Legal and procurement pressure remains a major driver, while researchers push back against compliance-only approaches. Universal and inclusive design are taught as design values, and participatory methods are increasingly expected rather than exceptional. Cognitive accessibility and the accessibility of emerging interfaces—voice assistants, augmented and virtual reality, AI-generated content—are active frontiers, raising questions the field has not settled: how to evaluate systems whose output changes each time, how to make machine-generated interfaces describable to assistive technology, and how to keep the lived expertise of disabled users at the center as the technology beneath them keeps changing.
References
- Accessibility, Wikipedia
- European Accessibility Act, Wikipedia
- Web Content Accessibility Guidelines, Wikipedia
The frameworks of Accessibility
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1960-Present
- 1985-Present
- 1990-Present
Legal and Procurement Compliance
What must the law require of accessible technology?
- 1990-Present
Participatory and User-Centered Accessibility Research
How should disabled users shape design research?
- 1994-Present
- 1995-Present
Accessibility APIs
How can software expose its interface to assistive tools?
- 1999-Present
Accessibility Evaluation and Conformance Testing
How do we know whether a system is accessible?
- 1999-Present
Web Content Accessibility Guidelines
What makes web content accessible to everyone?
- 2000-Present
- 2009-Present
Mobile and Post-Desktop Accessibility
How can touchscreens work for disabled users?
How the ideas connect
Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.
Accessibility APIs grew out of Assistive technology
Screen readers and other assistive technology could not interpret graphical user interfaces, so platform vendors built accessibility APIs such as Microsoft Active Accessibility to expose interface structure to them. The API architecture grew directly out of the assistive-technology model of equipping the user with a device that adapts the machine.
Carried by Microsoft Active Accessibility; AT-SPI.
Accessibility Evaluation and Conformance Testing influenced by Legal and Procurement Compliance
Legal requirements such as Section 508 and the ADA created demand for formal checks of whether systems met accessibility criteria, turning conformance testing into a professional practice. Procurement rules that made conformance a condition of purchase were the main engine behind the growth of evaluation methods.
Carried by Section 508; Americans with Disabilities Act (1990).
Accessibility Evaluation and Conformance Testing grew out of Web Content Accessibility Guidelines
Conformance testing grew directly out of WCAG: the checkpoints and success criteria gave evaluators the specific failures to test for, and automated tools were built to detect missing alt text, contrast problems and similar violations. The checklist-versus-usability debate is framed entirely in WCAG's terms.
Carried by Web Content Accessibility Guidelines 1.0 (1999).
Participatory and User-Centered Accessibility Research influenced by Assistive technology
Assistive-technology research had long documented how disabled people actually use devices, and this body of work fed into the later insistence on involving disabled users throughout design rather than testing them at the end. The participatory strand took up the assistive-technology finding that users develop their own workarounds and strategies.
Inclusive Design grew out of Universal Design
Inclusive design in the United Kingdom took up universal design's argument that products should suit the widest range of people without special adaptation, recasting it around user diversity and designing with excluded groups. The seven principles of universal design were a direct reference point for the inclusive-design movement.
Carried by Ron Mace; The Universal Design File (1997).
Web Content Accessibility Guidelines influenced by Legal and Procurement Compliance
Laws and procurement rules needed a technical standard to point to, and WCAG became that reference standard for web content. The compliance era's demand for measurable criteria shaped how the guidelines were written and later revised.
Mobile and Post-Desktop Accessibility influenced by Accessibility APIs
Mobile screen readers such as VoiceOver and TalkBack were built on the same accessibility-API architecture as desktop ones, exposing interface structure to assistive software. The platform-level accessibility features of smartphones carried the API model into touch devices.
Carried by VoiceOver (2009); TalkBack.
Mobile and Post-Desktop Accessibility influenced by Web Content Accessibility Guidelines
WCAG 2.1 added success criteria for touch, small screens and gesture input, responding to the mobile shift and giving post-desktop accessibility a shared standard. Mobile platform features and mobile web practice were assessed against these new criteria.
Carried by Web Content Accessibility Guidelines 2.1 (2018).
Mobile and Post-Desktop Accessibility influenced by Assistive technology
Mobile accessibility features such as switch access, voice control and adjustable touch timing continued the assistive-technology tradition of adapting the device to individual functional needs. The smartphone absorbed functions that had previously been separate assistive devices.
Participatory and User-Centered Accessibility Research influenced by Universal Design
Universal design's claim that disability is one point on a spectrum of human variation gave user-centered accessibility research a rationale for studying situational and temporary limits alongside permanent ones. The design-for-all framing shaped how researchers justified involving diverse users early.
Cognitive Accessibility influenced by Participatory and User-Centered Accessibility Research
User-centered research with disabled participants showed that cognitive barriers arise from complexity, unclear language and memory load rather than a missing sensory channel, which shaped the cognitive-accessibility agenda. The participatory emphasis on users as experts informed how cognitive needs were documented.
Cognitive Accessibility influenced by Inclusive Design
Inclusive design's spectrum-of-variation argument supported extending accessibility beyond sensory and motor conditions to cognitive differences. The design-for-diversity framing gave cognitive accessibility its rationale for treating disability as a relation between capacities and task demands.
Beyond the field
Where Accessibility's ideas came from in other fields, and what they led to there: the strongest 12 of 38 links.
Universal Design led to Inclusive design in Human Computer Interaction
Inclusive design is a direct descendant of universal design, taking its seven principles and reframing them for accessibility in computing.
Carried by Ron Mace.
Universal Design led to Universal Design for Learning in Instructional Design And Pedagogy
Universal Design for Learning was explicitly derived from Ron Mace's architectural universal design principle of designing for the widest range of users from the outset, applied to curricula.
Carried by Ron Mace; David Rose.
Participatory and User-Centered Accessibility Research influenced by Participatory Design in Human Computer Interaction
Scandinavian participatory design, with its cooperative design workshops and trade-union-rooted commitment to user voice, was carried into accessibility research as the method of including disabled participants in design and evaluation.
Carried by Pelle Ehn.
Inclusive Design influenced by Universal Design in Assistive Technology
Universal design as promoted in assistive technology circles supplied the principles and vocabulary that inclusive design adopted and then extended beyond disability to wider human diversity.
Carried by Ron Mace.
Inclusive Design influenced by Universal design in Design Ethics
Universal design's seven principles, formulated at North Carolina State University, were the direct source from which inclusive design in the UK and Europe developed its broader framing around diversity and exclusion.
Carried by Ron Mace.
Web Content Accessibility Guidelines influenced by Universal design in Design Ethics
WCAG's structure of guidelines and checkpoints was shaped by the seven principles of universal design, whose authors were involved in the WAI guidelines process in the late 1990s.
Mobile and Post-Desktop Accessibility influenced by Mobile and Wearable Computing in Ubiquitous Computing
Mobile accessibility guidelines and testing built directly on mobile and wearable computing research, adapting accessibility techniques to small screens, touch input and sensors in the late 2000s.
Mobile and Post-Desktop Accessibility grew out of Digital Accessibility in Assistive Technology
Post-desktop accessibility extended digital accessibility's web guidelines and assistive-technology compatibility work to mobile platforms and native apps in the late 2000s.
Assistive technology led to Augmentative and Alternative Communication in Assistive Technology
Assistive technology provided the communication devices, switches and mounting systems that augmentative and alternative communication practice depends on, and AAC emerged as a specialised branch of assistive technology provision.
Assistive technology influenced Assistive Robotics and Neural Interfaces in Assistive Technology
The assistive technology field supplied the user-needs and device-matching framework that assistive robotics and neural interfaces inherited when they moved from labs to users.
Assistive technology led to Assistive Technology Service Delivery Models in Assistive Technology
The growth of assistive technology as a field created the devices and the provision problems that service delivery models were built to organise, including assessment, matching and follow-up.
Assistive technology influenced Assistive Technology Outcomes Research in Assistive Technology
The assistive technology field defined the devices and service-delivery questions that outcomes research was created to evaluate.

Accessibility is a planet in Nousfarer
Its city has a tower for each of these 10 frameworks. Land, walk in, and climb one concept at a time.
Land on AccessibilityRelated fields
Fields its ideas are linked to
- Assistive Technology 14 links
- Rehabilitation Engineering 4 links
- Design Ethics 3 links
- Design 2 links
- Design Research 2 links
- Human Computer Interaction 2 links
- Design Methods 1 link
- Interaction Design Theory 1 link
- Visual Communication 1 link
- Curatorial Pedagogy And Publics 1 link
- Instructional Design And Pedagogy 1 link
- Ubiquitous Computing 1 link