AODA website compliance, tested by hand and fixed in the code
We check your website against WCAG 2.0 Level AA the way W3C recommends, fix what fails, and hand you a plain-English report your senior officer can actually read before signing anything.
No overlay widget, no "certified" badge, no pretending a scan is an audit. Just a site that works with a keyboard and a screen reader, and the paperwork to show it. Founder-led, from Guelph, for businesses across Ontario.
Get a free review
Tell us a bit about your business. No pressure, no obligation.
Usually answered within 24 hours on business days.
AODA compliance reports are due December 31, 2026.
Applies to Ontario businesses and non-profits with 20 or more employees.
What the AODA asks of your website
If your Ontario business or non-profit has 50 or more employees, your public website and web content published after January 1, 2012 must meet WCAG 2.0 Level AA, except live captions and pre-recorded audio description. That has been the rule since January 1, 2021, and it applies whether you built the site or paid someone else to.
Most sites are not there yet. WebAIM's 2026 scan of the top million home pages found detectable WCAG failures on 95.9 percent of them, and that only counts what a machine can find. The rest takes a person, a keyboard and a screen reader.
New to the rules? Start with the AODA compliance guide.
Four ways we help, depending on where your site is
Most businesses start with a check and fix. Some sites are better rebuilt. Either way, the first look is free.
Check and fix your current site
We test your site against WCAG 2.0 Level AA, fix what fails in the code or CMS, re-test the fixes and give you a plain-English report of what we found and changed.
Accessible rebuild
When the old site would cost more to patch than to replace, we rebuild it to WCAG 2.0 Level AA, the Ontario requirement, and design toward WCAG 2.2 Level AA where it is practical.
Ongoing accessibility care
New pages, PDFs, plugins and chat widgets are where barriers creep back in. On a care plan we re-check after changes so the site stays where we left it.
Compliance report prep
For businesses with 20 or more employees filing by December 31, 2026: a written summary of what was tested and fixed on the website, for your records and your certifying officer. Not legal advice.
How we test: tools first, people second, and people decide
W3C, which writes WCAG, puts it plainly: evaluation tools "can not determine accessibility, they can only assist in doing so." So the scanners go first and the humans have the final word.
Scope the site the W3C way
We follow W3C's WCAG Evaluation Methodology (WCAG-EM): agree what is in scope, explore the site, and pick a representative sample of pages plus complete processes like your contact form, booking or checkout.
Run automated scans
axe-core and Lighthouse on every sampled page. They catch the mechanical problems fast, like missing labels or low contrast. They are a starting point, not a verdict.
Test with a keyboard only
Every link, menu, form and dialog, without a mouse. We look for keyboard traps, a visible focus indicator and a sensible tab order.
Test with screen readers
NVDA on Windows, VoiceOver on Mac and iPhone, and TalkBack on Android. We check headings, landmarks, link names, form errors and that dynamic content is announced.
Check zoom, reflow, contrast and media
Text at 200 percent, layouts at 320 CSS pixels wide, text spacing overrides, colour contrast, captions, transcripts and the PDFs you link to.
Report, fix and re-test
Every issue is mapped to the WCAG success criterion it fails, with a severity and a fix. We fix, test again, and record what passed.
Why we do not install accessibility overlays
An overlay sits on top of the page and adjusts what it can see. It cannot rewrite a form that was never labelled or a menu that traps the keyboard. That is the code's job.
In April 2025 the U.S. Federal Trade Commission finalized an order requiring overlay vendor accessiBe to pay $1 million and barring it from claiming its automated products can make any website WCAG-compliant without evidence. We would rather fix the site than explain a widget to a regulator.
What you get
- Issue log mapped to WCAG 2.0 success criteria, with severity and the page it was found on
- The fixes themselves, in your site's code or CMS
- Re-test results for every fix
- A plain-English summary for your records and your compliance report
- An accessibility statement and accessible formats notice drafted for your site
- A short list of what to watch when you add new content
A good fit if
- Ontario businesses and non-profits with 50 or more employees, where the WCAG 2.0 AA rule applies
- Businesses with 20 or more employees getting ready for the December 31, 2026 report
- Smaller businesses that want a site every customer can use, or that sell to organizations that ask about accessibility
- Sites built on WordPress, Shopify, Squarespace, Wix or custom code
Probably not for you if
- You want a badge that says "AODA certified". We have not found an Ontario program that certifies websites, and we will not pretend to be one
- You want an overlay widget installed. We fix the site instead
- You need legal advice on your obligations. Talk to a lawyer; we will happily work alongside them
Straight answers before you book a call
What does an AODA website check include?
We pick a representative sample of pages and processes using W3C's evaluation method, run automated scans, then test by hand: keyboard only, screen readers, zoom and reflow, contrast, forms and media. You get a plain-English report that maps every issue to a WCAG success criterion and says how to fix it.
Can you guarantee AODA compliance?
No honest provider can promise that, because compliance depends on every page, document and future update. What we do is fix the issues we find to WCAG 2.0 Level AA, re-test the fixes, document the work and keep checking it if you are on a care plan.
Do you install accessibility overlays or widgets?
No. Overlays do not repair the underlying code, and the FTC fined one well-known overlay vendor over claims that its tool made sites compliant. We fix the site itself.
Can you help with our December 31, 2026 compliance report?
Yes, with the website side. We check the site, fix what we can, and give you a written summary of what was tested and fixed for your records. The report itself is certified by a senior officer of your organization, and we do not give legal advice.
We have fewer than 50 employees. Is this for us?
It can be. The WCAG website rule only applies at 50 or more employees, but every business must provide accessible formats on request, and an inaccessible site loses customers regardless of headcount. We will tell you honestly if a full check is more than you need.
Which platforms do you work with?
Custom-coded sites, WordPress, and hosted builders like Shopify, Squarespace and Wix. Where a platform or theme blocks a fix, we say so plainly and give you options, including a rebuild if that is the cheaper route.
What does the free first look include?
We review a handful of your key pages, such as the homepage, a service page and your contact form, and send back the most important barriers we found and a quote for the full check and fixes. No obligation.
Free AODA guides, if you would rather read first
AODA compliance guide
What the law asks of your business, sorted by size.
Read the guide
AODA compliance report 2026
Who files by December 31 and how.
Read the guide
AODA compliance examples
Before-and-after website fixes mapped to WCAG.
Read the guide
AODA fines and penalties
The real penalty schedule from the regulation.
Read the guide
AODA website requirements
Who the WCAG 2.0 AA rule applies to.
Read the guide
Website accessibility checklist
A free first pass you can run yourself.
Read the guide
Related: website design and development and website care plans.
Find out where your site stands before December 31
Send us your URL. We review a handful of key pages, send back the barriers that matter most and a quote for the rest. No obligation, and no widget sales pitch.
Get a free AODA first look