Understand the Rules.
Build for Accessibility.
Accessibility requirements can come from laws, regulations and technical standards. WebXS helps organizations understand the requirements that apply to their digital products — then audit, remediate and document accessibility accordingly.
Equal access for businesses serving the public.
Accessibility requirements for covered federal ICT.
Widely used accessibility criteria for digital content.
Newer WCAG success criteria and accessibility guidance.
Four Names. Different Roles.
ADA Title III and Section 508 are U.S. legal and regulatory frameworks. WCAG 2.1 and WCAG 2.2 are technical accessibility standards used to evaluate digital content and technology. Understanding the difference matters when determining what your organization actually needs.
ADA Title III
Title III of the ADA prohibits discrimination on the basis of disability by covered public accommodations and requires equal access to their goods, services, facilities and advantages.
For digital businesses, accessibility can be relevant when inaccessible websites or digital services create barriers to accessing a public accommodation's goods or services.
- Applies to covered businesses and organizations
- Focuses on equal access and nondiscrimination
- Digital services can be part of the accessibility analysis
- Specific obligations depend on the entity and circumstances
Section 508
Section 508 of the Rehabilitation Act establishes accessibility requirements for information and communication technology covered by federal agencies.
The Revised Section 508 Standards incorporate WCAG 2.0 Level A and AA success criteria for applicable electronic content and technology.
- Primarily relevant to U.S. federal agencies and covered ICT
- Applies to applicable web and non-web electronic content
- Uses WCAG 2.0 Level A and AA criteria
- Relevant to federal procurement and technology requirements
WCAG 2.1
WCAG 2.1 is an international technical standard developed by the W3C Web Accessibility Initiative to make web content more accessible to people with disabilities.
WCAG 2.1 added accessibility requirements beyond WCAG 2.0, including criteria addressing mobile accessibility, low vision and cognitive or learning-related needs.
- International technical accessibility standard
- Applies to websites, web applications and digital content
- Uses Level A, AA and AAA conformance levels
- Common technical reference for accessibility evaluation
WCAG 2.2
WCAG 2.2 builds on WCAG 2.1 while adding nine additional success criteria. It is designed to remain backwards compatible with earlier WCAG 2 versions.
New criteria include areas such as focus visibility, dragging movements, target size, consistent help, redundant entry and accessible authentication.
- Latest published WCAG 2 recommendation
- Adds nine success criteria compared with WCAG 2.1
- Includes improvements around navigation and interaction
- WCAG 2.2 conformance also satisfies WCAG 2.1 requirements
Which One Applies to You?
The answer depends on your organization, audience, contracts, procurement requirements and the digital products you provide.
| Framework / Standard | What It Is | Typical Relevance | Technical Reference |
|---|---|---|---|
| ADA Title III | U.S. federal civil rights law addressing discrimination by covered public accommodations. | Businesses and organizations serving the public. | ADA Title III regulations and applicable guidance. |
| Section 508 | U.S. federal accessibility requirements for covered information and communication technology. | Federal agencies, federal ICT procurement and covered technology. | WCAG 2.0 Level A & AA for applicable electronic content. |
| WCAG 2.1 | International technical accessibility standard. | Websites, web applications and digital content. | Level A, AA and AAA success criteria. |
| WCAG 2.2 | Newer WCAG 2 technical standard with additional success criteria. | Organizations seeking a current WCAG 2 reference. | Level A, AA and AAA success criteria. |
WCAG Is the Technical Language of Accessibility.
WCAG organizes accessibility requirements around four core principles. A website or application should be perceivable, operable, understandable and robust. Within these principles, WCAG defines testable success criteria at Levels A, AA and AAA.
Perceivable
Information and user interface components must be presented in ways users can perceive.
Operable
Users must be able to operate interface components and navigate through the experience.
Understandable
Information and operation of the user interface should be understandable and predictable.
Robust
Content should work reliably with current and future user agents and assistive technologies.
Regulations Tell You What Matters.
We Help You Find What Needs Fixing.
WebXS combines automated coverage with human accessibility expertise to identify issues, guide remediation, verify fixes and prepare accessibility documentation.
Scope
Identify the digital products, templates, user journeys and standards relevant to your project.
Audit
Combine automated checks with human-led accessibility testing where required.
Remediate
Turn findings into practical, code-level remediation guidance and fixes where included.
Verify
Re-test resolved findings and verify the accessibility work against the agreed scope.
Document
Produce appropriate accessibility documentation such as VPAT/ACR deliverables when included in the engagement.
The applicability of an accessibility requirement depends on the organization, jurisdiction, digital product, contract and other circumstances. This page is provided for general informational purposes and is not legal advice. WebXS recommends obtaining qualified legal advice when determining specific legal obligations.
Not Sure Which Requirements Apply?
Tell us about your website, application or procurement requirement. We'll help you understand the accessibility path that makes sense for your project.