What Does A11y Mean? Web Accessibility Explained
A11y means accessibility. Learn what the term means for websites, how it relates to WCAG, and what accessible web experiences need to support.
A11y means accessibility. It is a numeronym: the “a” and “y” are the first and last letters of “accessibility,” and 11 stands for the eleven letters between them. In web development, accessibility means building websites and tools so people with disabilities can perceive, understand, navigate, interact with, and contribute to the web.
The U.S. Department of Health and Human Services lists A11y as an abbreviation for accessibility. The shorthand itself does not describe a specific technique or guarantee that a site conforms to a standard.
1. What web accessibility means
Web accessibility is whether people with different abilities can use web content and tools. The W3C describes access in terms of perceiving, understanding, navigating, and interacting with the web, and contributing to it. That includes the content itself and the technologies people use to access it.
Accessibility applies to many disability types, including auditory, cognitive, neurological, physical, speech, and visual disabilities. A design that improves access can also help people without disabilities, such as someone using a small screen or an older person experiencing changes in ability.
Accessibility is not only a visual-design concern and is not only about screen readers. It can involve content, interaction, code, media, and whether a person can complete a task through the input and output methods available to them.
2. What accessibility looks like in a website
Practical examples include:
- Providing text alternatives for informative images so their meaning is available when the image cannot be perceived.
- Giving buttons and other controls useful accessible names, and ensuring code exposes their names, roles, and values to browsers and assistive technologies.
- Using more than color alone to communicate meaning, such as pairing a color-coded error with text or an icon.
- Maintaining sufficient contrast between foreground content and its background.
- Allowing text to resize and content to reflow without losing information or functionality.
- Making controls and navigation usable from a keyboard.
These examples illustrate common accessibility considerations; they are not a complete checklist and do not establish conformance by themselves.
3. How WCAG relates to a11y
The Web Content Accessibility Guidelines (WCAG) are a technical standard for web content within the broader field of accessibility. WCAG 2.2 organizes its guidance around four principles:
- Perceivable: People must be able to perceive the information and interface.
- Operable: People must be able to operate the controls and navigation.
- Understandable: Information and interface behavior must be understandable.
- Robust: Content must work with a range of user agents, including assistive technologies.
WCAG 2.2 has 13 guidelines under these four principles. Its success criteria are testable and grouped into conformance levels A, AA, and AAA. The criteria, rather than a handful of example fixes, determine whether content conforms. WCAG also applies to dynamic content, multimedia, mobile web, and AI web interfaces.
4. Accessibility is a system, not a single component
Web accessibility depends on parts of the web working together. Web content includes text, images, forms, multimedia, markup, scripts, and applications. People access that content through user agents such as browsers, often alongside assistive technologies. Authoring tools are the software and services used to produce content.
W3C standards address different parts of this system: WCAG covers web content; UAAG covers user agents; ATAG covers authoring tools; and WAI-ARIA provides ways to make dynamic content and advanced interface controls more accessible. These standards have related but distinct purposes.
5. Accessibility, usability, and inclusion
These ideas overlap, but they do not mean the same thing:
| Concept | Main focus |
|---|---|
| Accessibility | Equivalent access and experience for people with disabilities. |
| Usability | How effectively, efficiently, and satisfactorily people can use a product overall. |
| Inclusion | Broader participation conditions, which can include disability access as well as connectivity, skills, economic situation, education, geography, culture, age, and language. |
Teams can coordinate accessibility, usability, and inclusion work while keeping the specific focus of each clear. A product can be usable for many people and still have barriers for people with disabilities.
6. A developer’s starting checklist
- Check content alternatives. Confirm informative images have appropriate text alternatives and that meaning is not conveyed through visuals alone.
- Check controls and names. Make sure interactive controls can be identified and their purpose is clear to users and assistive technology.
- Check keyboard interaction. Navigate the page and operate its controls without relying on a pointer.
- Check readability and layout changes. Review contrast, text resizing, and reflow at narrow screen widths.
- Check the applicable WCAG success criteria. Use the criteria relevant to your content and target conformance level; a quick visual review is not a conformance determination.
A screenshot can help a team inspect visual properties such as contrast, clipping, and responsive layout. It cannot establish whether keyboard interaction works, whether accessible names are exposed correctly, or whether a page conforms to WCAG. Combine visual review with appropriate interaction and accessibility evaluation.
7. Capture a page for visual review
For a one-off visual check, capture the page at the viewport and state you want to inspect. For example, this browser-based JavaScript snippet uses Playwright to save a screenshot after the page loads. Install Playwright with npm install playwright and ensure a supported browser is installed for your environment.
const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch();
const page = await browser.newPage({ viewport: { width: 1280, height: 900 } });
try {
await page.goto('https://example.com', { waitUntil: 'networkidle', timeout: 30000 });
await page.screenshot({ path: 'accessibility-review.png', fullPage: true });
} finally {
await browser.close();
}
})();Use screenshots as one input to review. A static image cannot test focus order, keyboard behavior, screen-reader output, or conformance across the applicable criteria.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. Its one-request API can capture a page as an image or PDF. See the ScreenshotNeo API documentation for options and setup.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers report the page verdict and billing status. Its MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000 screenshots.
Sign up free for 1,000 screenshots a month, with no card required.
8. Common misunderstandings
- “A11y is a standard.” A11y is shorthand for accessibility; WCAG is a technical standard for web content.
- “Accessibility means adding screen-reader support.” Screen-reader access is one concern among many; accessibility also involves other disabilities, interaction needs, content, and technologies.
- “A few fixes mean the site conforms.” Examples such as adding alt text or improving contrast do not alone establish WCAG conformance. Evaluate the applicable success criteria.
- “Accessibility and usability are interchangeable.” They are connected, but accessibility focuses on access for people with disabilities while usability concerns the overall effectiveness, efficiency, and satisfaction of use.
9. FAQ
What does the 11 stand for in A11y?
It represents the eleven letters between the first “a” and last “y” in “accessibility.”
Is A11y the same as WCAG?
No. A11y means accessibility. WCAG is one technical standard used to specify testable accessibility requirements for web content.
Does accessibility help people without disabilities?
It can. W3C notes that accessible design may also benefit people using small-screen devices and older people experiencing changes in ability.
Does a screenshot prove a page is accessible?
No. A screenshot can support visual review, but it does not show whether keyboard operation, assistive-technology output, or all relevant WCAG criteria work.
