Accessibility Commitment and Standards
Digital accessibility governs whether web content, applications, and media can be used by people with disabilities — including those who rely on screen readers, keyboard navigation, switch controls, or captioning. This page defines the technical and legal framework governing accessibility commitments, explains how conformance is measured, identifies common failure scenarios, and outlines the decision boundaries that separate compliant from non-compliant practice. Understanding these distinctions matters for any organization publishing at national scale, where the user population spans the full spectrum of ability and assistive technology use.
Definition and scope
Accessibility, in the digital context, refers to the degree to which information and user interface components are perceivable, operable, understandable, and robust — the four principles established in the Web Content Accessibility Guidelines (WCAG) 2.1, published by the World Wide Web Consortium (W3C). WCAG 2.1 replaced the earlier WCAG 2.0 specification and introduced 17 additional success criteria, with particular attention to mobile responsiveness and cognitive accessibility.
In the United States, digital accessibility obligations derive from the Americans with Disabilities Act (ADA) Title III and Section 508 of the Rehabilitation Act (29 U.S.C. § 794d), which applies specifically to federal agencies and federally funded programs. The Department of Justice issued a final rule in March 2024 (DOJ Rule on Web and Mobile Accessibility) establishing WCAG 2.1 Level AA as the compliance benchmark for Title II entities — state and local governments.
The scope of accessibility commitments covers:
- Perceivable content — Text alternatives for non-text content, captions for video, sufficient color contrast (minimum 4.5:1 ratio for normal text per WCAG 2.1 §1.4.3)
- Operable interfaces — Full keyboard navigability, no content that flashes more than 3 times per second, skip navigation links
- Understandable content — Consistent navigation, input error identification, plain language at appropriate reading levels
- Robust technical implementation — Valid HTML/ARIA markup compatible with assistive technologies including JAWS, NVDA, and Apple VoiceOver
Scope extends to third-party widgets, embedded media players, PDF documents, and any interactive form element hosted on the domain.
How it works
Conformance is measured against WCAG 2.1 success criteria at three levels: Level A (minimum), Level AA (standard commercial and government target), and Level AAA (enhanced, typically required only in specialized contexts such as government social services portals).
A Voluntary Product Accessibility Template (VPAT) — now formalized as the Accessibility Conformance Report (ACR) — provides a structured self-assessment documenting which criteria are supported, partially supported, or not applicable. Federal procurement under Section 508 routinely requires an ACR from vendors. The ACR format follows the Information Technology Industry Council (ITI) VPAT® 2.5 template.
Testing methodology combines automated scanning with manual review. Automated tools — Axe, Lighthouse, IBM Equal Access Checker — identify roughly 30 to 40 percent of WCAG failures, according to WebAIM's 2023 analysis of automated testing coverage. The remaining failures require human testers using assistive technology to evaluate focus management, reading order, and dynamic content behavior. Screen reader testing against NVDA on Firefox and JAWS on Chrome represents the baseline combination recommended by the Screen Reader User Survey #10 (WebAIM, 2021).
The editorial standards and data methodology applied across published content inform how accessible information architecture is maintained at the content level, not just at the code level. Accessibility is validated across the technology infrastructure as part of deployment review.
Common scenarios
Image alt text failures remain the most prevalent WCAG 2.1 issue. The WebAIM Million 2024 report found that 54.5 percent of the top 1 million home pages contained detectable missing image alternative text — making it the single most common automated failure for the sixth consecutive year.
Form labeling errors represent a second high-frequency failure category. Unlabeled form controls prevent screen reader users from identifying input purpose, violating WCAG 2.1 Success Criterion 1.3.5 (Identify Input Purpose).
Insufficient color contrast affects users with low vision and color vision deficiencies. A 4.5:1 contrast ratio applies to normal text; 3:1 applies to large text (18pt or 14pt bold per WCAG 2.1 §1.4.3). Failure rates for contrast deficiencies appeared in 81 percent of tested pages in the WebAIM Million 2024 study.
PDF inaccessibility presents a distinct challenge: untagged PDFs, scanned images of text, and documents without reading order metadata are non-compliant with both WCAG 2.1 and PDF/UA (ISO 14289-1:2014). Organizations publishing reports or forms in PDF format must apply tagging, alt text, and logical reading order to each document.
Decision boundaries
The critical distinction in accessibility practice lies between WCAG Level A and WCAG Level AA conformance.
| Criterion | Level A | Level AA |
|---|---|---|
| Color contrast (normal text) | Not addressed | 4.5:1 minimum |
| Captions (live) | Not required | Required |
| Resize text | Not required | 200% without loss of content |
| Focus visible | Required | Enhanced (2.1 adds §2.4.11–2.4.12 in 2.2) |
| Error suggestion | Not required | Required (§3.3.3) |
Level A conformance alone does not meet the DOJ's 2024 Title II standard, the Section 508 baseline, or the accessibility expectations governing national coverage publishing operations. Level AA is the operative floor for any content reaching general public audiences.
A secondary boundary separates reasonable modification from fundamental alteration — a statutory limit under ADA Title III where compliance would alter the nature of the service itself. Courts have applied this defense narrowly; it does not excuse failure to provide text alternatives or keyboard access.
Accessibility remediation timelines also create a decision boundary: the DOJ's 2024 rule grants small Title II entities (fewer than 50,000 population served) until April 26, 2027 to achieve compliance (ADA.gov rule summary), while larger entities face a deadline of April 24, 2026. Private sector entities under Title III operate without a codified federal deadline but face ongoing litigation risk under the ADA, with federal courts filing more than 4,000 web accessibility lawsuits annually as tracked by UsableNet's 2023 ADA Digital Accessibility Lawsuit Report.