Category: Compliance and Reporting

Does Not Support

Also known as: Not Supported, Unsupported

Simply put

"Does Not Support" is a conformance rating used to indicate that a product or feature fails to meet a particular accessibility requirement. In accessibility documentation, it signals that the functionality being evaluated does not satisfy the standard in question. The specific evidence provided here does not establish a formal, authoritative definition of this term as used in accessibility conformance reporting.

Formal definition

"Does Not Support" is commonly used as a conformance value in accessibility evaluation documentation to indicate that the majority of a product's functionality does not meet a referenced criterion or standard. It is generally distinguished from ratings such as "Supports," "Partially Supports," or "Not Applicable." Practitioners should note that the exact meaning, permitted values, and reporting conventions depend on the specific reporting framework or template being used, and that the evidence available here is insufficient to authoritatively define the term within a recognized accessibility standard. This entry is not legal advice; consult the applicable conformance methodology and qualified counsel for authoritative guidance.

Why it matters

Conformance ratings such as "Does Not Support" are central to how organizations communicate the accessibility status of their products to purchasers, procurement officers, and end users. When a feature is documented as "Does Not Support" a given requirement, that rating signals a known gap that may prevent people using assistive technologies from completing tasks. For buyers, particularly those in government and enterprise settings who rely on accessibility documentation during procurement, an accurate rating helps set expectations, prioritize remediation, and evaluate whether a product is fit for its intended use.

The integrity of these ratings matters because they inform decisions with real consequences. An overly optimistic rating can lead an organization to deploy a product that excludes users, while an accurate "Does Not Support" rating provides an honest basis for planning workarounds, requesting fixes, or selecting an alternative. Because the term appears in evaluation documentation rather than in the text of any law, it should be read as a statement about a product's measured conformance against a referenced standard, not as a determination of legal compliance.

Who it's relevant to

Procurement and Compliance Officers

Those evaluating products against accessibility requirements rely on conformance ratings to understand where gaps exist. A "Does Not Support" value flags a known failure against a referenced criterion, which can inform purchasing decisions, remediation timelines, and risk assessments. Because the rating reflects measured conformance rather than legal compliance, it should be considered alongside other evaluation methods and, where legal exposure is a concern, with qualified counsel.

Accessibility Engineers and QA Testers

Practitioners producing or reviewing accessibility documentation must apply conformance values consistently against the correct criterion and the correct reporting framework. Assigning "Does Not Support" accurately requires understanding the specific methodology in use, since permitted values and thresholds vary between templates and standards.

Product Managers and Development Teams

A "Does Not Support" rating identifies functionality that fails a requirement and typically warrants a remediation plan. Product teams can use these ratings to prioritize work, set expectations with customers, and track progress across releases against the standard being referenced.

Buyers and End Users of Documentation

Readers of accessibility documentation use conformance values to gauge whether a product meets their needs. A "Does Not Support" entry is a candid indication of a gap, but readers should recognize that ratings describe conformance against a referenced standard and that meeting a standard does not by itself guarantee a fully usable experience for every user.

Inside Does Not Support

Conformance Level Terminology

"Does Not Support" is one of the standard values used in accessibility conformance reporting, most notably in the Voluntary Product Accessibility Template (VPAT) and the resulting Accessibility Conformance Report (ACR). It indicates that a product or feature does not meet the referenced success criterion.

Relationship to WCAG Success Criteria

The rating is typically applied against specific WCAG success criteria (for example, criteria at Level A or AA within WCAG 2.0, 2.1, or 2.2) or against Section 508 requirements, indicating that the evaluated content or functionality fails to satisfy that particular criterion as tested.

Contrast with Other Ratings

"Does Not Support" is distinct from other conformance values such as "Supports," "Partially Supports," and "Not Applicable." It generally signals a more complete failure to meet a criterion than "Partially Supports," which indicates that some functionality conforms while some does not.

Supporting Remarks and Explanations

A "Does Not Support" designation is commonly accompanied by explanatory remarks describing the nature of the failure, affected components, and the basis for the conclusion, which helps procurement teams and remediation teams understand scope.

Basis in Testing Methodology

The rating reflects the outcome of an evaluation that may combine automated tools, manual review, and assistive technology testing. Because automated testing detects only a portion of issues, a defensible "Does Not Support" finding generally relies on manual and assistive technology verification as well.

Common questions

Answers to the questions practitioners most commonly ask about Does Not Support.

Does a 'Does Not Support' rating mean the product fails to meet ADA requirements?

Not necessarily. 'Does Not Support' is a conformance term used within accessibility documentation such as an Accessibility Conformance Report (ACR) based on the Voluntary Product Accessibility Template (VPAT). It indicates that a product does not meet a particular WCAG success criterion or applicable standard as evaluated. It is a technical conformance statement, not a legal determination. The ADA is a US civil rights law, and whether a given product creates legal exposure is a separate question that depends on jurisdiction, the applicable Title, regulation, and case law. Conformance findings can inform but do not by themselves establish legal compliance or non-compliance, and this is not legal advice.

If a criterion is marked 'Does Not Support,' does that mean the entire product is inaccessible?

No. 'Does Not Support' generally applies to a specific success criterion or evaluated scope, not to the product as a whole. A product may support many criteria while not supporting others. Reviewers should read the accompanying remarks and the full set of conformance ratings rather than drawing a product-wide conclusion from a single 'Does Not Support' entry. Conformance ratings also reflect the specific version and level (for example WCAG 2.1 Level AA) against which the evaluation was performed.

How is 'Does Not Support' different from 'Partially Supports' in a conformance report?

In the reporting terminology commonly used in VPAT-based reports, 'Does Not Support' generally indicates that the majority of the functionality does not meet the criterion, while 'Partially Supports' indicates that some functionality meets the criterion but not all. Because these terms are applied through evaluator judgment, the accompanying remarks are important for understanding what specifically was or was not met and under what conditions.

What should accompany a 'Does Not Support' rating in an ACR?

A 'Does Not Support' rating should generally be accompanied by explanatory remarks describing what does not meet the criterion, where the issue occurs, and any relevant context such as the platform, assistive technology, or content type tested. Clear remarks help reviewers assess impact and prioritize remediation. The report should also state the standard and version evaluated and the testing methods used.

How should a procurement or accessibility team respond when reviewing a 'Does Not Support' finding?

Teams commonly evaluate the affected criterion's user impact, review the vendor's remarks for scope and severity, ask about remediation plans and timelines, and consider whether workarounds or alternative accessible means exist. Because automated testing detects only a portion of issues, teams may also request evidence of manual and assistive technology testing. Findings should be weighed against organizational requirements, and legal questions should be referred to qualified counsel.

Can a 'Does Not Support' rating change over time?

Yes. Conformance ratings reflect a product's state at the time of evaluation against a specific standard and version. Subsequent remediation, product updates, or re-testing may change a rating, and evaluating against a newer WCAG version (for example moving from 2.1 to 2.2) can also affect results. For this reason, conformance reports should indicate the evaluation date and the standard version, and reviewers should confirm they are working from the current report.

Common misconceptions

"Does Not Support" means the entire product is inaccessible.

The rating is applied per success criterion, not to the product as a whole. A product may show "Does Not Support" for certain criteria while meeting others, so the designation should be read at the level of the specific criterion being reported.

A "Does Not Support" entry in a VPAT or ACR by itself establishes legal non-compliance with the ADA.

A conformance report describes a technical evaluation against WCAG or Section 508 criteria; it is not a legal determination. Whether a shortfall creates legal exposure depends on the applicable authority (such as ADA Title II or Title III, or Section 508) and evolving regulation and case law. Qualified legal counsel should be consulted for compliance conclusions.

Avoiding any "Does Not Support" ratings guarantees an accessible experience.

Meeting WCAG success criteria does not guarantee usability for all users, and a report's accuracy depends on the testing performed. Conformance ratings are one input, not a complete measure of the real-world experience for people using assistive technologies.

Best practices

Apply the "Does Not Support" rating to individual success criteria rather than to a whole product, and reference the specific WCAG version and level (or Section 508 requirement) being evaluated.

Accompany each "Does Not Support" entry with clear remarks identifying the affected components, the observed failure, and how it was detected so remediation and procurement teams can act on it.

Base the rating on a combination of automated, manual, and assistive technology testing, recognizing that automated tools alone detect only a portion of issues.

Distinguish "Does Not Support" from "Partially Supports" carefully, reserving the former for criteria that are not met and documenting the reasoning for the chosen value.

Treat conformance reports as technical documentation rather than legal assurances, and direct compliance questions to qualified legal counsel and current agency rulemaking.

Use "Does Not Support" findings to build a prioritized remediation plan, and re-evaluate and update the report after fixes are verified through repeat testing.