guide
AODA for saas & software: requirements, priorities, and audit checklist
AODA compliance for SaaS products requires applying Accessibility for Ontarians with Disabilities Act 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.
Does AODA apply to SaaS products?
The Accessibility for Ontarians with Disabilities Act (AODA) is a 2005 Ontario law that mandates accessibility for the public, private, and not-for-profit sectors operating in Ontario — including a digital requirement that public-facing websites conform to WCAG 2.0 Level AA.
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 AODA 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 AODA on a SaaS & Software site
1. File a multi-year accessibility plan: Public-sector and large organisations must publish a plan and update at least every five years.
2. Conform to WCAG 2.0 AA: Applies to public websites and web content published after 1 Jan 2012.
3. File compliance reports: Designated public-sector every 2 years; private/non-profit every 3 years.
4. Train staff: Required AODA training for all employees, volunteers and contractors.
Sources
- AODA — Government of Ontario — Government of Ontario
- Section508.gov VPAT — GSA
FAQ
Frequently asked questions
Cited answers. Sourced. Updated as standards and case law change.
Does AODA apply to saas & software websites?
The Accessibility for Ontarians with Disabilities Act (AODA) is a 2005 Ontario law that mandates accessibility for the public, private, and not-for-profit sectors operating in Ontario — including a digital requirement that public-facing websites conform to WCAG 2.0 Level AA.
What are the most common AODA 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.
founders@accessivepath.com · +977 9851094056