a11y is a numeronym for "accessibility" - the 11 stands for the eleven letters between the "a" and the "y" - and it refers to the practice of designing and developing digital content so that people with disabilities can perceive, understand, navigate, and interact with it on equal terms.
The term is most commonly used in web development and product design, where accessibility covers a broad spectrum of human variation: visual impairments such as blindness or low vision, hearing loss, motor disabilities that affect keyboard or pointer use, and cognitive differences that influence how people process information. A digital interface that is accessible works not just for the majority, but for users who rely on screen readers, keyboard-only navigation, high-contrast modes, captions, or other assistive technologies.
The technical backbone of web accessibility is the Web Content Accessibility Guidelines, known as WCAG. Published and maintained by the World Wide Web Consortium (W3C), these guidelines organize accessibility requirements into four core principles: content must be Perceivable, Operable, Understandable, and Robust. Each principle contains specific success criteria rated at three conformance levels - A, AA, and AAA - where AA is widely recognized as the baseline for acceptable accessibility in professional and commercial contexts.
In practice, implementing a11y means writing semantic HTML so that assistive technologies can interpret the structure of a page correctly. It means providing text alternatives for images, ensuring sufficient color contrast between text and background, making all interactive elements reachable and operable via keyboard, and structuring forms so that errors are communicated clearly. It also means that video content includes captions, and that dynamic updates to a page are announced to users who cannot see them visually.
Accessibility is increasingly a legal concern as well as a design one. Several jurisdictions, including the European Union and the United States, have legislation that requires digital services to meet accessibility standards, particularly for public sector bodies and larger commercial operators.
Beyond compliance, the case for building accessible products rests on a straightforward argument: removing barriers for users with disabilities tends to improve the experience for everyone. Logical page structure, clear language, and reliable keyboard behavior are qualities that benefit all users, regardless of ability.