Category: WCAG Principles and Conformance

Accessibility Supported

Simply put

"Accessibility supported" describes a way of using a web technology (such as a specific HTML feature, scripting method, or media format) that reliably works with assistive technologies like screen readers and with the accessibility features built into browsers and operating systems. In practice, it means that when you rely on a technology to meet accessibility requirements, users with disabilities can actually access the content or functionality it provides. If a technology is not used in an accessibility-supported way, the same information or functionality generally needs to be offered through another method that is.

Formal definition

In WCAG terminology, a way of using a technology is "accessibility supported" when it is supported by users' assistive technologies and by the accessibility features of the browsers and user agents they use. WCAG relies on this concept as a precondition for conformance: only technologies used in an accessibility-supported way can be relied upon to satisfy success criteria. Where content or functionality is provided in a way that is not accessibility supported, that content or functionality is expected to also be available in a way that is accessibility supported. The W3C does not centrally define or certify which specific technology uses qualify as accessibility supported; this determination generally depends on the assistive technologies and user agents in use within a given context, and may vary across environments, languages, and over time. Verifying accessibility support typically requires testing with real assistive technologies, since automated checks alone cannot confirm it. This entry describes a technical WCAG concept and is not legal advice; consult qualified counsel or current agency guidance regarding compliance obligations.

Why it matters

Accessibility support is a foundational precondition in WCAG: a way of using a web technology can only be relied upon to meet success criteria if it is actually supported by the assistive technologies and browser accessibility features people use. Without this concept, a site could technically implement a feature that appears correct in markup but fails to reach users with disabilities because their screen readers or browsers cannot interpret it. Treating accessibility support as a threshold helps ensure that conformance claims reflect real-world access rather than theoretical correctness.

This matters because meeting WCAG success criteria on paper does not guarantee an accessible experience if the underlying technologies are not accessibility supported in the environments your users rely on. As guidance from section508.gov notes, when information or functionality is provided in a way that is not accessibility supported, that same information or functionality is expected to also be available in a way that is. In practice this means teams may need to provide alternative methods when a chosen technique cannot be depended on to work with common assistive technologies.

Accessibility support also connects directly to the broader goal of equal access and social inclusion. As the W3C describes, accessibility benefits people with disabilities as well as others such as older people and people in rural or developing areas. Ensuring that the technologies you depend on genuinely work with assistive technologies is what turns a conformance target into usable access. This entry describes a technical WCAG concept and is not legal advice; organizations should consult qualified counsel or current agency guidance regarding specific compliance obligations.

Who it's relevant to

Accessibility Engineers and Developers

Developers deciding which HTML features, scripting methods, or media formats to use for accessible content need to confirm those techniques are accessibility supported in the assistive technologies and browsers their users rely on. When a technique cannot be depended on, they are generally expected to provide the same information or functionality through an alternative method that is accessibility supported.

QA and Testing Teams

Because accessibility support cannot be confirmed by automated checks alone, testers should validate features using real assistive technologies such as screen readers and the accessibility features built into browsers and operating systems. This helps ensure that conformance claims reflect actual access rather than markup that only appears correct.

Compliance Officers and Legal Counsel

Those evaluating conformance claims should understand that WCAG treats accessibility support as a precondition for relying on a technology to meet success criteria. Because the W3C does not centrally certify specific technology uses, and because support varies by environment and over time, conformance assessments depend on context. This entry is not legal advice; consult qualified counsel or current agency guidance regarding specific obligations.

UX Designers and Content Authors

Designers and authors choosing formats and interaction patterns benefit from confirming that their chosen approaches work with the assistive technologies their audiences use. When a preferred design relies on a technology that is not accessibility supported, planning an accessible alternative up front helps preserve equal access to the same content and functionality.

Inside Accessibility Supported

Definition under WCAG

A term used in the Web Content Accessibility Guidelines to describe the requirement that the ways in which web content uses technologies (such as HTML, ARIA, CSS, or scripting) must be supported by users' assistive technologies and by the accessibility features of browsers and other user agents.

Dual condition

For a use of a technology to be considered accessibility supported, it generally must satisfy two conditions: the technology feature must work with assistive technologies, and it must be supported by the accessibility features of widely available user agents in the user's natural language.

Relationship to WCAG conformance

Accessibility support is a foundational concept for WCAG conformance claims, because content can only conform using technologies that are relied upon in an accessibility-supported way. Technologies not used in an accessibility-supported manner generally must not interfere with the user's ability to access the page.

No fixed list from the W3C

The W3C does not publish a definitive list of which technologies or combinations qualify as accessibility supported. Instead, this determination is left to the entity making a conformance claim, and can depend on the assistive technologies and user agents in use within a given context or user base.

Context and audience dependence

Whether a given use of a technology is accessibility supported may vary by the languages, assistive technologies, and user agents relevant to the intended audience, meaning determinations are context-specific rather than universal.

Common questions

Answers to the questions practitioners most commonly ask about Accessibility Supported.

Does 'accessibility supported' mean a web technology only needs to work in one assistive technology to count?

No. The term describes whether users' assistive technologies actually work with a given way of using a web technology, not whether a single tool happens to support it. WCAG frames accessibility support in terms of the assistive technologies available to the relevant users in a given context. Support in one screen reader, for example, does not by itself establish broad accessibility support, and the determination generally depends on what technologies your users can realistically obtain and use.

If a technique is listed in WCAG's supporting documents, is it automatically accessibility supported?

Not automatically. The W3C's techniques are informative and illustrate ways to meet success criteria, but they are not the definition of accessibility support. Whether a particular use of a technology is accessibility supported depends on real-world support by the assistive technologies your users rely on, which can vary by platform, version, and context. The listing of a technique does not guarantee that it behaves reliably in every environment.

How can a team determine whether a specific technology is accessibility supported for its users?

Teams commonly evaluate accessibility support by identifying the assistive technologies and browsers their users are likely to use, then testing the specific ways they use a web technology against those combinations. This generally involves manual testing with screen readers, magnifiers, voice control, and keyboard-only navigation, rather than relying on automated checks alone. Because support varies, documenting the tested combinations helps clarify the basis for any support claim.

What role does accessibility support play in claiming WCAG conformance?

Under WCAG, only ways of using technologies that are accessibility supported can be relied upon to meet success criteria for a conformance claim. If a technique depends on features that users' assistive technologies do not support, it generally cannot be counted toward conformance. This is why conformance claims often describe the technologies and versions assumed to be supported.

Does meeting accessibility support requirements guarantee an accessible experience or legal compliance?

No. Accessibility support is one component of WCAG conformance, and conformance itself does not guarantee a fully usable experience for every user or immunity from legal claims. Automated testing detects only a portion of issues, so manual and assistive technology testing are generally needed. This entry is not legal advice, and obligations can evolve through regulation and case law; consult qualified legal counsel for your situation.

How should teams handle assistive technologies that are outdated or used by a small portion of users?

Decisions about which assistive technology versions to support generally reflect what the relevant users can realistically obtain and use in a given context, which may exclude very old or rarely used tools. Because there is no single universal list, teams often document their assumptions about supported technologies and revisit them over time as usage patterns and tool support change. What is appropriate can vary by audience and jurisdiction.

Common misconceptions

The W3C maintains an official list of technologies that are accessibility supported.

The W3C does not provide a definitive or authoritative list. The responsibility for determining whether a technology is used in an accessibility-supported way generally rests with the party making a conformance claim, based on the assistive technologies and user agents relevant to their audience.

If a technology can technically produce accessible output, it is automatically accessibility supported.

Accessibility support depends on whether assistive technologies and the accessibility features of user agents actually support that use of the technology in practice for the relevant audience, not merely on whether the technology is theoretically capable of accessible output.

Meeting the accessibility-supported requirement guarantees an accessible experience or legal compliance.

Accessibility support is one prerequisite for a WCAG conformance claim, but conformance itself does not guarantee a usable experience for all users, nor does it guarantee immunity from legal claims. Manual and assistive technology testing remain necessary, and legal obligations are determined by applicable law and case developments. This is not legal advice.

Best practices

Identify the assistive technologies and user agents most relevant to your intended audience before deciding which technologies and features you will rely on in an accessibility-supported way.

Test content with actual assistive technologies and user agents rather than assuming a feature is supported based solely on specifications or automated checks, which detect only a portion of issues.

Document the basis for your accessibility-support determinations, including which technology features you rely upon and the assistive technology and user agent combinations considered, to support any WCAG conformance claim.

Ensure that any technologies not used in an accessibility-supported way do not interfere with users' ability to access the rest of the page.

Reassess accessibility-support determinations periodically, as assistive technology and browser support evolve over time and across user populations.

Consult qualified legal counsel and monitor current agency guidance and case law before treating accessibility support or WCAG conformance as evidence of legal compliance.