Free homepage scan
Free
- Scope:
- One publicly accessible homepage.
- Method:
- Automated scan against WCAG 2.0 A and AA.
- You get:
- A short plain-English summary of the most important machine-detectable findings.
- Re-scan:
- Not included.
Ontario AODA website accessibility testing
Find WCAG 2.0 A and AA issues on your site, understand who each one shuts out, and hand your developer a prioritized list of fixes.
Ontario’s website accessibility requirement applies to designated public sector organizations and to businesses and non-profits with 50 or more employees. Organizations with 20 or more employees file an Accessibility Compliance Report by 31 December 2026. Website testing supports one part of that work and does not assess the rest of the report.
Example finding
for and id values.Illustrative example, not a real client result.
Every report is built from an automated scan of your pages against WCAG 2.0 Level A and AA, then written up so that a non-specialist can act on it.
Ordered by how much each issue actually obstructs someone, not by how many times it occurs.
What each finding means, who it affects, and what that person experiences on your page.
The failing elements, the relevant success criterion, a recommended fix and an effort estimate.
Automated tools reliably catch a range of code-level problems — missing text alternatives, insufficient colour contrast, unlabelled form controls, invalid ARIA, links with no accessible name. These are real barriers and they make up a large share of what is wrong on a typical site.
They cannot determine whether a site is accessible. The W3C is explicit that automated evaluation tools alone cannot establish conformance and that informed human evaluation is required. A clean scan is a good sign, not a certificate.
The checks below are not included in the automated report. They need a person, and I will tell you when your site looks like it needs them rather than implying a tool covered them.
| Check | Criterion |
|---|---|
| Keyboard reaches every control, with no trap | 2.1.1, 2.1.2 |
| Focus is visible and follows a sensible order | 2.4.7, 2.4.3 |
| Form errors are announced and explained | 3.3.1, 3.3.3 |
| Alt text is useful, not merely present | 1.1.1 |
| Content order still makes sense without styling | 1.3.2 |
Prices are in Canadian dollars. The final quote depends on how many pages and distinct templates are in scope.
Free
$750 – $2,500
$150 – $400 / month
Out of scope for all levels: manual keyboard, screen reader, content and usability testing; native mobile apps; PDFs and other documents; remediation work itself.
Every report is prepared directly by Noam Muscovitch in Toronto, using a repeatable testing process built on axe-core, the open-source engine used inside many commercial accessibility tools.
You deal with me directly, from the first scan through the re-scan afterwards.
No, and nobody can promise that. The Accessibility Compliance Report covers several areas of the AODA. Website accessibility is one part of it for organizations that carry that requirement. This service supports that part by identifying WCAG 2.0 A and AA issues on your site. It does not assess or complete the rest of your obligations.
Under Ontario’s Integrated Accessibility Standards Regulation, the WCAG 2.0 Level AA website requirement applies to designated public sector organizations and to businesses and non-profits with 50 or more employees, and has since 1 January 2021. Organizations with 20 or more employees must file an Accessibility Compliance Report, but those with 20 to 49 employees are not subject to the website requirement.
An automated scan of one publicly accessible homepage against WCAG 2.0 A and AA, and a short plain-English summary of the most important machine-detectable findings. It is yours to keep whether or not you go further.
Automated. The scanning is done by axe-core in a real browser; the interpretation, prioritization and write-up are done by me. Manual accessibility testing — keyboard, screen reader, focus order, content quality — is not included, and the report says so explicitly rather than leaving it ambiguous.
The free scan covers one homepage. For the detailed report, we agree the page and template list before I quote, because a site with one repeated template takes far less work than one with twelve distinct layouts.
That is what it is built for. Each finding names the failing elements, the success criterion, a recommended fix and an effort estimate, so nobody has to go hunting for which image is missing its description.
No. I test and report. Most findings are small changes your existing developer can make, and you are welcome to use the report with whoever you like.
Sometimes, depending on how the environment is secured. Ask, and I will tell you honestly whether the scan can reach it.
The detailed report includes one re-scan so you can see what actually cleared. After that, accessibility tends to regress quietly as content and plugins change, which is what the monthly option is for.
Send me your URL and I will run it and send back the headline findings, no charge and no obligation.
Email noam@accessaudit.ca