Web Content Accessibility Guidelines (WCAG) 2.1
WCAG 2.1 provides testable success criteria organized around perceivable, operable, understandable, and robust digital content.
What the authority record establishes
WCAG 2.1 provides testable success criteria organized around perceivable, operable, understandable, and robust digital content.
Technical recommendation; binding effect depends on incorporation by law, regulation, policy, or contract
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
It gives buyers a technical vocabulary for testing applicant, reviewer, payment, map, document, and mobile experiences without treating a vendor statement as proof of conformance.
Affected operating stages
- Requirements
- Design
- Development
- Content
- Testing
- Monitoring
Capabilities to examine
Applicant Portal And Guided Intake
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for applicant portal and guided intake.
Electronic Plan Submission And Version Control
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for electronic plan submission and version control.
Fee Calculation Payments And Reconciliation
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for fee calculation payments and reconciliation.
Public Search Status And Communications
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for public search status and communications.
Mobile And Offline Field Inspections
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for mobile and offline field inspections.
Documents Records Retention And Public Disclosure
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for documents records retention and public disclosure.
Affected buyer audiences
- product teams
- government accessibility teams
- vendors
- testers
- procurement
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
A product statement or automated scan does not establish complete WCAG conformance, legal compliance, usability for every person, or effective communication.