AccessivePath
Run a free audit

guide

WCAG 2.2 for saas & software: requirements, priorities, and audit checklist

WCAG 2.2 compliance for SaaS products requires applying Web Content Accessibility Guidelines 2.2 to the specific failure points typical of the saas & software industry — including component libraries without semantic markup, modal dialogs that trap focus incorrectly, data tables without programmatic structure.

Lin Chen · IAAP CPACC · Mobile accessibility lead3 min readPublished · Updated

Does WCAG 2.2 apply to SaaS products?

WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.

SaaS & Software accessibility — the lay of the land

SaaS vendors face accessibility through two channels: their own marketing site (subject to ADA Title III), and their product (subject to procurement-driven VPAT requirements and EAA scope for consumer services). Enterprise procurement increasingly requires a current VPAT.

Where WCAG 2.2 bites hardest in SaaS products

• Component libraries without semantic markup

• Modal dialogs that trap focus incorrectly

• Data tables without programmatic structure

• Drag-and-drop without keyboard alternatives

• Status messages not announced to AT (4.1.3)

Remediation priorities

• Core admin / dashboard navigation

• Forms, validation, and error recovery

• Tables, charts, and data export

• Component library (button, input, modal, menu primitives)

• Embedded customer-facing widgets

How to comply with WCAG 2.2 on a SaaS & Software site

1. Establish scope and baseline: Inventory every public-facing digital property. Run an automated baseline scan to detect the ~25–30% of WCAG criteria that machines can reliably check.

2. Manual + assistive-technology audit: Engage IAAP-credentialed auditors to test the remaining ~70% of criteria — keyboard, screen reader (NVDA, JAWS, VoiceOver), zoom and cognitive criteria.

3. Remediate at source: Fix issues in source code, not via overlay widgets. Train developers; integrate axe-core into CI; track open issues in JIRA or Linear.

4. Publish an accessibility statement: Disclose conformance level, known limitations, contact for accessibility feedback, and remediation timelines. Required under EAA and best-practice under ADA.

5. Monitor and re-test: Re-audit quarterly. Re-test before every major release. Keep an internal VPAT/ACR current and post it publicly.

Sources

FAQ

Frequently asked questions

Cited answers. Sourced. Updated as standards and case law change.

  • Does WCAG 2.2 apply to saas & software websites?

    WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.

  • What are the most common WCAG 2.2 failures in SaaS products?

    Component libraries without semantic markup Modal dialogs that trap focus incorrectly Data tables without programmatic structure

  • What conformance level should a saas & software site target?

    WCAG 2.2 Level AA is the consensus target for legal compliance and the level referenced by virtually every national accessibility law.

  • Do SaaS vendors need a VPAT?

    Increasingly yes. Enterprise procurement teams — particularly in higher education, healthcare, government, and large finance — require a current VPAT/ACR before purchase. Federal vendors require Section 508 VPATs explicitly.

  • Is the SaaS marketing site or the product more important for accessibility?

    Both are in scope under different regimes. The marketing site is ADA Title III (public accommodation). The product is procurement-VPAT-driven and increasingly EAA-driven for consumer offerings. A vendor should not treat one as adequate cover for the other.

  • What is the most cost-effective way for a SaaS team to start?

    Three steps: (1) accessibility-instrumented component library so new screens inherit conformance; (2) axe-core in CI for regression; (3) annual manual audit against WCAG 2.2 AA with an IAAP-certified team.

Stop guessing. Get the audit a Fortune 500 a11y team would have written.

Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.

Run a free auditBook a demo

founders@accessivepath.com · +977 9851094056