Skip to main content
Accessibility.com, LLC
Category: Compliance and Reporting

Supports

Simply put

In the context of accessibility conformance reporting, 'Supports' is a term used to indicate that a product or feature meets a given accessibility requirement without any exceptions. More generally, 'support' refers to the aid, resources, or assistance provided to help a person accomplish a task or meet a need. The evidence available here reflects general-language and educational uses of the term rather than a single technical definition.

Formal definition

The general-language sense of 'support' is 'to promote the interests or cause of especially by action or aid' or 'to provide someone with money or physical things that are needed.' In grammar, 'supports' is the singular present-tense form of the verb, agreeing with a singular subject. In an educational context, 'supports' denotes instructional methods, educational services, or school resources used to accelerate learner progress. Note: the evidence packet does not contain accessibility-specific authoritative definitions (for example, W3C or VPAT/ITI conformance language), so a practitioner-level accessibility definition cannot be substantiated from these sources alone; consult recognized standards documentation for domain-specific usage.

Why it matters

The word "supports" carries different meanings across the contexts in which accessibility practitioners encounter it, and conflating them can lead to confusion or overstated claims. In accessibility conformance reporting, the term is commonly used as a status label to indicate that a product or feature meets a given requirement, though the evidence available here does not include authoritative accessibility documentation (such as W3C or VPAT/ITI conformance language) to substantiate a precise technical definition. As a result, readers should treat any conformance-specific usage as requiring confirmation against the recognized standards documentation that actually governs it.

Getting the meaning right matters because conformance status terminology often drives procurement, compliance, and product decisions. A label indicating a requirement is met is not, on its own, a guarantee of an accessible experience for every user, nor does it confer legal immunity. Accurate use of terms like "supports" helps stakeholders avoid reading more assurance into a report than the underlying evidence provides.

Because the sources gathered here reflect general-language and educational uses of the word rather than a single accessibility definition, this entry does not attempt to state an authoritative conformance meaning. Practitioners relying on the term in a compliance context should consult the current, domain-specific standards and, where legal exposure is a concern, qualified legal counsel. This entry is informational and is not legal advice.

Who it's relevant to

Procurement and compliance officers
Those evaluating conformance reports may see "supports" used as a status label. Because the general-language meaning and any framework-specific meaning can differ, officers should confirm the definition against the applicable standards documentation and avoid treating a status label as a guarantee of full accessibility or legal compliance.
Accessibility engineers and testers
Practitioners describing whether a feature meets a requirement should use precise, standards-aligned terminology. Where a conformance framework defines "supports" formally, engineers should apply that definition rather than the everyday sense, and should remember that meeting a requirement does not, by itself, ensure an accessible experience for all users.
Content writers and editors
Writers producing accessibility documentation should be aware of the grammatical distinction: "supports" is the singular present-tense verb form and must agree with a singular subject. Consistent, accurate usage helps prevent ambiguity in technical and conformance text.
Educators and instructional staff
In educational settings, "supports" refers to instructional methods, educational services, or school resources used to accelerate learner progress. This usage is distinct from any conformance-reporting sense and should not be conflated with it.

Inside Supports

Conformance claim language
"Supports" is a value used in accessibility conformance reporting (such as in a Voluntary Product Accessibility Template, or VPAT, based on the Accessibility Conformance Report format) to indicate that functionality of a product meets an applicable criterion without noted exceptions.
Relationship to specific criteria
The term is applied on a per-criterion basis, for example against individual WCAG success criteria or Section 508 requirements, rather than as a blanket statement about an entire product.
Graduated conformance terms
"Supports" sits alongside related reporting values commonly used in these templates, such as "Partially Supports," "Does Not Support," and "Not Applicable," each describing a different degree to which a criterion is met.
Supporting explanation
A conformance report generally pairs a "Supports" rating with a remarks or explanation column that describes how the product meets the criterion, providing context for the claim.
Scope of applicability
The value is typically tied to a defined product version, evaluation date, and the standard being reported against (for example WCAG 2.0, 2.1, or 2.2 at a stated conformance level, or specific Section 508 provisions).

Common questions

Answers to the questions practitioners most commonly ask about Supports.

Does a rating of "Supports" mean a product is fully accessible?
No. "Supports" is a conformance rating term used in accessibility documentation such as an Accessibility Conformance Report (ACR) based on the Voluntary Product Accessibility Template (VPAT). It indicates that the functionality of the product meets the applicable criterion, but a per-criterion rating does not establish that the entire product is accessible, usable by all people with disabilities, or legally compliant. Conformance is distinct from real-world usability and from legal compliance, and readers should evaluate the full report rather than a single rating.
Is "Supports" the same as passing automated accessibility testing?
No. A "Supports" rating reflects an evaluation against a specific criterion and generally should be based on a combination of methods, including manual review and testing with assistive technology. Automated testing detects only a portion of potential issues, so a rating derived from automated checks alone may not be reliable. The rating term itself does not specify the testing method used, which is why the surrounding documentation and evaluation methodology matter.
How does "Supports" differ from "Partially Supports" and "Does Not Support"?
In the conformance rating scale commonly used in VPAT-based reports, "Supports" indicates the functionality meets the criterion, "Partially Supports" indicates some functionality meets the criterion while some does not, and "Does Not Support" indicates the majority of functionality does not meet the criterion. Each rating is typically accompanied by remarks and explanations describing how the product behaves against that specific criterion.
What supporting information should accompany a "Supports" rating in a report?
A rating is generally expected to be paired with remarks and explanations that describe how the product meets the criterion, along with the scope of what was evaluated and the methodology used. Providing this context helps reviewers understand what was tested, under what conditions, and whether the rating applies to all relevant parts of the product or only to certain features.
How should a procurement team use "Supports" ratings when evaluating a product?
Procurement teams commonly review the full conformance report rather than relying on individual ratings in isolation. Because a rating applies to a specific criterion under stated conditions, teams may verify the scope, request the evaluation methodology, and consider independent or hands-on testing with assistive technology for functions critical to their users. A rating supports a purchasing decision but generally should not be treated as the sole basis for one.
Does a "Supports" rating remain accurate over time?
Not necessarily. A rating reflects the product version and evaluation conditions at the time the report was prepared. Product updates, changes in the evaluated criteria or standard version, and evolving testing practices can affect accuracy, so organizations may check the report date and version and request current documentation when relying on it. This guidance is not legal advice, and organizations should consult qualified counsel and current agency rulemaking where legal obligations are involved.

Common misconceptions

A "Supports" rating means the product is fully accessible and legally compliant.
"Supports" is a vendor-provided conformance statement about specific criteria, not a guarantee of an accessible experience for all users or of immunity from legal claims. Conformance, usability, and legal compliance are distinct, and requirements evolve through regulation and case law. This is not legal advice; consult qualified counsel for compliance questions.
"Supports" is an objective, independently verified certification.
Conformance reports are commonly self-authored by the vendor or its representatives and reflect the evaluation methods and date stated in the document. A "Supports" value should be reviewed critically, verified through independent testing where possible, and interpreted alongside its remarks and stated scope.
A "Supports" claim can be established through automated testing alone.
Automated tools detect only a portion of potential accessibility issues. Substantiating that a criterion is supported generally also requires manual review and testing with assistive technologies, so an accurate rating depends on the evaluation methodology used.

Best practices

Read "Supports" ratings at the criterion level and review the accompanying remarks column rather than relying on a single overall impression of the report.
Confirm the report's stated scope, including product version, evaluation date, and the exact standard and conformance level being reported against (for example a specific WCAG version and the AA level).
Treat vendor conformance claims as a starting point and, where feasible, validate them through your own manual and assistive-technology testing rather than automated checks alone.
Compare "Supports" against the report's other values such as "Partially Supports" and "Does Not Support" to understand where gaps or exceptions remain.
Ask vendors for the evaluation methodology behind a "Supports" rating and request updated reports as products change or standards are revised.
Document that a favorable conformance report does not by itself establish legal compliance, and consult qualified legal counsel and current agency rulemaking for decisions with regulatory implications.