Report-ready data
Evidence your plan team can quote
Per-page scan results, date-stamped and exportable as PDFs. Plan owners can pull barrier-removal evidence and progress numbers without going back to engineering.
Exportable PDF evidence
The Accessible Canada Act (S.C. 2019, c. 10) requires federally regulated organisations and the Government of Canada to identify, remove, and prevent accessibility barriers, including in their digital services. Each entity in scope publishes an accessibility plan, follows up with progress reports in the in-between years, and refreshes the plan on a three-year cycle. The first plans were due by 1 June 2023, putting the next plan refresh on or before 1 June 2026.
The Act itself doesn't prescribe a specific web standard, but most ACA accessibility plans align with WCAG 2.1 Level AA in practice. It's the bar federal web teams and contractors tend to use, the standard cited in the Government of Canada's own Standard on Web Accessibility, and the standard A11y Pulse scans against by default.
Enforcement sits with the Accessibility Commissioner under the Canadian Human Rights Commission. The Commissioner can issue compliance orders, conduct inspections, and impose administrative monetary penalties of up to $250,000 per violation. Plans and progress reports are public documents, so they're scrutinised by advocacy groups and the Canadian disability community alongside the Commissioner's office.
The ACA is a federal statute covering federal jurisdiction only. Provincially regulated organisations sit under separate regimes that have grown up over the past two decades: the Accessibility for Ontarians with Disabilities Act (AODA), the Accessibility for Manitobans Act, Nova Scotia's Accessibility Act, and British Columbia's Accessible BC Act. Most of these point at WCAG 2.0 or 2.1 AA for the web content piece, so the same A11y Pulse scan history supports a provincial filing as well as a federal one.
Why teams switch to A11y Pulse
Filing a plan or progress report is easier when you can point at a continuous record of what's been scanned, what's been fixed, and what's still in progress.
Report-ready data
Per-page scan results, date-stamped and exportable as PDFs. Plan owners can pull barrier-removal evidence and progress numbers without going back to engineering.
Exportable PDF evidence
WCAG 2.1 AA scanning
A11y Pulse scans against WCAG 2.1 Level AA, the practical bar that most accessibility plans across the ACA cohort align with. Daily scanning across every page catches the issues a one-off sample audit misses.
WCAG 2.1 AA by default
Between filings
A barrier can creep back in months before your next plan refresh — Slack and Microsoft Teams alerts surface it while the change is still fresh in the commit log.
Slack and Teams alerts
Side by side
Two ways to gather evidence for an ACA plan or progress report. A11y Pulse is built for the continuous one.
Where we fit
A11y Pulse runs axe-core daily across your full sitemap, including authenticated and JavaScript-rendered pages. Findings come with the WCAG criterion, element selector, screenshot, and plain-English remediation guidance. Exportable PDF reports give your accessibility plan owners report-ready evidence on demand.