Accessibility (a11y)
Accessibility (often shortened to a11y for the 11 letters between the A and the Y) means designing and building digital products that people of all abilities can perceive, understand, navigate, interact with, and contribute to. It is not a feature tier or a special mode. It is a fundamental property of well-built software, no different from security or performance.
§ 1 Definition
Accessibility in web and software development is the practice of removing barriers that prevent interaction with or access to digital products by people with a wide range of physical, cognitive, and sensory abilities. This includes people who are blind or have low vision, who are deaf or hard of hearing, who have motor disabilities affecting keyboard or touch use, who have cognitive disabilities affecting memory or reading, and those who rely on assistive technologies such as screen readers, voice recognition software, switch devices, or alternative input methods. The Web Content Accessibility Guidelines (WCAG) provide the internationally recognised technical standard for web accessibility, organised around four principles: content must be Perceivable, Operable, Understandable, and Robust (POUR). Accessibility is increasingly a legal requirement under laws such as the Americans with Disabilities Act (ADA), Section 508, and the European Accessibility Act (EAA), and it correlates strongly with better SEO, improved usability for all users, and reduced legal risk.
§ 2 Why accessibility matters: beyond compliance
Accessibility is often framed as a compliance checkbox, but treating it as a checklist misses the point. Around 15 percent of the global population experience some form of disability. That is over one billion people. When a website is inaccessible, it is not merely an inconvenience. It is an active barrier to employment, education, commerce, healthcare, and civic participation. Beyond ethics and legality, accessible websites consistently rank higher in search results (clean semantic HTML, proper heading structure, and descriptive alt text are all SEO signals), reach a wider audience, and are more resilient to device and browser diversity. The overlap between accessibility improvements and good UX is so large that accessibility is best understood as a form of quality assurance.
§ 3 The four principles: POUR
WCAG organises accessibility requirements around four principles. Perceivable: users must be able to perceive the content through at least one sense. This means text alternatives for images, captions for audio, and sufficient colour contrast. Operable: users must be able to operate the interface. This means keyboard navigation, enough time to read and use content, and no seizure-inducing flashes. Understandable: users must be able to understand the content and interface. This means readable text, predictable behaviour, and helpful error messages. Robust: content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. This means clean, valid markup that exposes semantics properly.
§ 4 The business case for accessibility
Studies from Google, McKinsey, and the W3C WAI consistently show that accessible organisations outperform their peers. Accessibility reduces maintenance overhead (semantic, well-structured code is easier to maintain), improves SEO rankings (Google uses heading hierarchy and alt text as ranking signals), decreases legal exposure (ADA demand letters and lawsuits are rising yearly), and opens market share among the disability community and an ageing global population. One in four US adults live with a disability, controlling over $490 billion in disposable income. Accessibility is not a cost centre. It is a business multiplier.
§ 5 Common questions
- Q. Is accessibility the same as disability support?
- A. Accessibility benefits everyone, not just people with permanent disabilities. A person with a broken arm, a new parent holding a baby, someone in bright sunlight, or someone with a slow internet connection all benefit from accessible design. This is the curb-cut effect: features designed for one group often improve the experience for everyone.
- Q. Can an accessibility overlay make my site accessible?
- A. No. Accessibility overlays that claim to fix a site with a single line of JavaScript are widely condemned by the disability community and accessibility professionals. They cannot fix underlying structural problems and often introduce new barriers. The W3C's Overlay Fact Sheet, signed by over 1,000 accessibility experts, explains why.
- Q. Is accessibility an SEO ranking factor?
- A. Directly and indirectly, yes. Google uses semantic HTML, heading hierarchy, alt text, and mobile-friendliness as ranking signals, all of which are core accessibility requirements. Beyond that, accessible sites tend to load faster, be easier to crawl, and have lower bounce rates, all of which influence search rankings.
- Accessibility is a fundamental quality requirement, not a feature bolt-on.
- The four WCAG principles are Perceivable, Operable, Understandable, and Robust (POUR).
- Accessibility improvements directly benefit SEO, usability, and legal compliance.
- Over 1 billion people worldwide have some form of disability; exclusion is a design failure.
- Overlays cannot substitute for genuine development work and often make things worse.
Atomic Glue builds accessibility into every project from the ground up, not as a retrofit. Our Web Development services include semantic HTML, keyboard navigation, colour contrast compliance, screen reader testing, and automated auditing with axe-core. Get in touch to learn how we can make your next project accessible, performant, and legally compliant.
Get in touchAccessibility (often shortened to a11y for the 11 letters between the A and the Y) means designing and building digital products that people of all abilities can perceive, understand, navigate, interact with, and contribute to. It is not a feature tier or a special mode. It is a fundamental property of well-built software, no different from security or performance.
Category: Accessibility (also: Web Development, UX)
Author: Atomic Glue Team
## Definition
Accessibility in web and software development is the practice of removing barriers that prevent interaction with or access to digital products by people with a wide range of physical, cognitive, and sensory abilities. This includes people who are blind or have low vision, who are deaf or hard of hearing, who have motor disabilities affecting keyboard or touch use, who have cognitive disabilities affecting memory or reading, and those who rely on assistive technologies such as screen readers, voice recognition software, switch devices, or alternative input methods. The Web Content Accessibility Guidelines (WCAG) provide the internationally recognised technical standard for web accessibility, organised around four principles: content must be Perceivable, Operable, Understandable, and Robust (POUR). Accessibility is increasingly a legal requirement under laws such as the Americans with Disabilities Act (ADA), Section 508, and the European Accessibility Act (EAA), and it correlates strongly with better SEO, improved usability for all users, and reduced legal risk.
## Why accessibility matters: beyond compliance
Accessibility is often framed as a compliance checkbox, but treating it as a checklist misses the point. Around 15 percent of the global population experience some form of disability. That is over one billion people. When a website is inaccessible, it is not merely an inconvenience. It is an active barrier to employment, education, commerce, healthcare, and civic participation. Beyond ethics and legality, accessible websites consistently rank higher in search results (clean semantic HTML, proper heading structure, and descriptive alt text are all SEO signals), reach a wider audience, and are more resilient to device and browser diversity. The overlap between accessibility improvements and good UX is so large that accessibility is best understood as a form of quality assurance.
## The four principles: POUR
WCAG organises accessibility requirements around four principles. Perceivable: users must be able to perceive the content through at least one sense. This means text alternatives for images, captions for audio, and sufficient colour contrast. Operable: users must be able to operate the interface. This means keyboard navigation, enough time to read and use content, and no seizure-inducing flashes. Understandable: users must be able to understand the content and interface. This means readable text, predictable behaviour, and helpful error messages. Robust: content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. This means clean, valid markup that exposes semantics properly.
## The business case for accessibility
Studies from Google, McKinsey, and the W3C WAI consistently show that accessible organisations outperform their peers. Accessibility reduces maintenance overhead (semantic, well-structured code is easier to maintain), improves SEO rankings (Google uses heading hierarchy and alt text as ranking signals), decreases legal exposure (ADA demand letters and lawsuits are rising yearly), and opens market share among the disability community and an ageing global population. One in four US adults live with a disability, controlling over $490 billion in disposable income. Accessibility is not a cost centre. It is a business multiplier.
## Common questions
Q: Is accessibility the same as disability support?
A: Accessibility benefits everyone, not just people with permanent disabilities. A person with a broken arm, a new parent holding a baby, someone in bright sunlight, or someone with a slow internet connection all benefit from accessible design. This is the curb-cut effect: features designed for one group often improve the experience for everyone.
Q: Can an accessibility overlay make my site accessible?
A: No. Accessibility overlays that claim to fix a site with a single line of JavaScript are widely condemned by the disability community and accessibility professionals. They cannot fix underlying structural problems and often introduce new barriers. The W3C's Overlay Fact Sheet, signed by over 1,000 accessibility experts, explains why.
Q: Is accessibility an SEO ranking factor?
A: Directly and indirectly, yes. Google uses semantic HTML, heading hierarchy, alt text, and mobile-friendliness as ranking signals, all of which are core accessibility requirements. Beyond that, accessible sites tend to load faster, be easier to crawl, and have lower bounce rates, all of which influence search rankings.
## Key takeaways
- Accessibility is a fundamental quality requirement, not a feature bolt-on.
- The four WCAG principles are Perceivable, Operable, Understandable, and Robust (POUR).
- Accessibility improvements directly benefit SEO, usability, and legal compliance.
- Over 1 billion people worldwide have some form of disability; exclusion is a design failure.
- Overlays cannot substitute for genuine development work and often make things worse.
## Related entries
- [WCAG (2.1, 2.2)](atomicglue.co/glossary/wcag)
- [Semantic HTML](atomicglue.co/glossary/semantic-html-website-development)
- [ARIA](atomicglue.co/glossary/aria)
- [Accessibility Audit](atomicglue.co/glossary/accessibility-audit)
- [Inclusive Design](atomicglue.co/glossary/inclusive-design)
Last updated July 2026. Permalink: atomicglue.co/glossary/accessibility