AODA & WCAG 2.0 AA for Ontario websites
Real AODA website compliance, fixed in your code.
We test your website by hand, repair the actual HTML, CSS and JavaScript, then re-test every single fix the way real people browse. No overlay widget. No duct tape. And no monthly fee for a patch that doesn't hold.
- 20+ years of hands-on web work
- WAVE + axe + manual testing
- Fixed, upfront pricing
- 1Image has no alt textAlt text written by a person
- 2Text contrast is 2.1:1Text contrast is 9.4:1
- 3Form field has no labelField is properly labelled
- 4Button can't be reached by keyboardKeyboard focus is visible
An illustration of the kind of issues we find and fix. Flip the switch.
- 47days until the December 31, 2026 compliance report deadline for organizations with 20+ employees
- 2021WCAG 2.0 Level AA has been required for Ontario organizations with 50+ employees since January 1
- $100,000maximum fine per day for a corporation convicted of an offence under the Act
- 95.9%of the web's top home pages still have detectable WCAG failures
Sources: Government of Ontario; Accessibility for Ontarians with Disabilities Act, 2005; WebAIM Million 2026.
Quick check
Does the AODA apply to your website?
Pick the option that fits your organization in Ontario.
The AODA applies, but the website rule and the report don't.
Organizations with fewer than 20 employees don't file a compliance report, and the WCAG website requirement starts at 50 employees. Other AODA standards, like accessible customer service, still apply to you, and Ontario encourages every business to have an accessible site. It's also the cheapest time to get it right, before you grow into the requirement.
You have a report to file by December 31, 2026.
Businesses and non-profits with 20 or more employees must file an accessibility compliance report every three years. The WCAG 2.0 AA website requirement itself starts at 50 employees, so if you're growing, now is the smart time to fix your site.
Yes. Your public website must meet WCAG 2.0 Level AA.
That has been the rule since January 1, 2021, and you also need to file a compliance report by December 31, 2026 confirming you meet your obligations. If you're not sure your site passes, ask us for a quote and we'll tell you where it stands.
Yes, regardless of size.
Designated public sector organizations must meet WCAG 2.0 Level AA and file a compliance report every two years. The most recent deadline was December 31, 2025, and a late report still has to be filed.
General information only, not legal advice. Employee counts mean employees in Ontario. For the official wording, see Ontario's accessibility rules for businesses and non-profits (opens in a new tab).
Overlays vs. real fixes
A widget can't fix what it can't see.
Overlay plugins like accessiBe, UserWay and similar tools add a script and a little icon on top of your site. Your code underneath stays exactly as broken as it was. Here's the difference.
| What we're comparing | Overlay widget | Our code fixes |
|---|---|---|
| What actually changes | A script paints over the page after it loads. Your source code is untouched. | We repair the real HTML, CSS and JavaScript, so the fix is part of your site. |
| How issues are found | Automated detection only, which misses a large share of WCAG problems. | WAVE and axe scans, plus keyboard and screen reader testing by a person. |
| Screen reader users | Often get in the way of the assistive tech people already rely on. | Your site works with their own tools, the way they have them set up. |
| If the script is blocked or fails | Every "fix" disappears instantly. | Nothing to load, nothing to fail. The fixes are permanent. |
| What you pay | A subscription, every month, for as long as the site is live. | One fixed quote. Optional upkeep only if you want it. |
| Proof for your compliance report | A vendor badge that says you're covered. | A page-by-page record of what was tested, fixed and re-tested. |
This isn't just our opinion. In April 2025 the U.S. Federal Trade Commission finalized an order requiring accessiBe to pay $1 million over claims that its AI widget could make any website WCAG compliant. More than 800 accessibility professionals have signed the Overlay Fact Sheet advising against overlays. Read the full story on our blog.
How it works
Scan, test by hand, fix, then test it again.
We scan every template
WAVE and axe run across your pages to catch what machines are good at catching: contrast, missing alt text, unlabelled fields, broken ARIA.
We test it like a person would
Then we put the mouse away. We tab through menus, forms, popups and checkouts, and listen to your site with a screen reader. This is where the real problems show up.
We fix the actual code
Every issue is repaired at the source, in your theme, templates, styles and scripts. Nothing is layered on top, and your design stays the way you like it.
We re-test every fix
Each fix is checked again, by scan and by hand, before we sign off. You get a plain-English report of what we found, what we changed and how it tested.
Every fix re-tested by keyboard
What we fix
The issues that stop real people, mapped to the WCAG rule behind each one.
Colour contrast
Text and buttons people with low vision can actually read, without wrecking your brand colours.
Image alt text
Descriptions written by a human who looked at the picture, not guessed by a robot.
Keyboard access
Menus, sliders, popups and checkouts that work without a mouse, with no keyboard traps.
Visible focus
A clear outline that shows keyboard users exactly where they are on the page.
Forms and labels
Every field labelled, every error explained, so people can actually contact you or check out.
Headings and structure
Proper headings, lists and landmarks so screen reader users can skim your page like everyone else.
Names, roles and ARIA
Buttons that say what they do. Broken or unnecessary ARIA cleaned up or removed.
Zoom and text resize
Pages that stay usable at 200% zoom, with nothing cut off or overlapping.
Recent result
232 accessibility issues to zero, in 17 days.
An industrial e-commerce site needed proof for its December 2026 compliance report. We fixed the code on every template customers use, then tested each one by hand.
- 232 → 0category page issues (axe)
- 20 → 0homepage errors (WAVE)
- 11templates tested by tool and by hand
- 0real issues remaining at sign-off
Pricing
A real fix, priced to beat the quotes you've been given.
Big agencies bill for layers of project management. Overlay companies bill you every month, forever. We're a hands-on specialist team, so you pay for the work and nothing else. Got a written quote for a manual audit and code-level fixes? Send it over and we'll do our best to beat it.
- One fixed price, in writingQuoted from your actual site, before any work starts.
- No monthly widget feeThe fixes live in your code. You own them.
- Priced by template, not by pageFixing one template fixes every page that uses it.
Why hands-on matters
Passing a scan isn't the same as working for a person.
A scanner can tell you an image has alt text. It can't tell you the alt text says "IMG_4471." It can confirm a button exists, but not whether someone using only a keyboard can ever reach it.
- Every page template tabbed through, start to finish
- Forms, menus and checkouts tested with a screen reader
- Each fix re-tested in a real browser before sign-off
FAQ
Straight answers about AODA website compliance
What is AODA website compliance?
The Accessibility for Ontarians with Disabilities Act (AODA) requires designated public sector organizations, and businesses and non-profits with 50 or more employees in Ontario, to make their public websites and web content meet WCAG 2.0 Level AA. In plain terms, people with disabilities need to be able to read, navigate and use your site.
Who has to comply?
Designated public sector organizations of any size, plus private businesses and non-profits with 50 or more employees in Ontario. Organizations with 20 or more employees also have to file an accessibility compliance report every three years. The next one is due December 31, 2026.
Which version of WCAG does the AODA require?
The regulation names WCAG 2.0 Level AA, with two exceptions: live captions and pre-recorded audio descriptions. We test against the newer WCAG 2.1 and 2.2 criteria as well, because meeting those covers 2.0 and makes your site better for more people.
What happens if my website isn't compliant?
Ontario can audit organizations, issue compliance orders and apply administrative penalties. For offences under the Act, the maximum fine is $100,000 per day for corporations and $50,000 per day for individuals, including directors and officers. In practice, enforcement usually starts with notices and orders. There's also the cost you don't see: customers who simply can't use your site. We've written a full breakdown here.
Can't I just install an accessibility plugin like accessiBe?
You can, but it won't make you compliant. Overlay widgets don't change your source code, they only catch what automated detection can find, and they often interfere with the screen readers people already use. In 2025 the FTC ordered accessiBe to pay $1 million over claims that its widget could make any website WCAG compliant. Real compliance means fixing the code.
How much does AODA website compliance cost?
It depends on how many unique templates your site has and how complex its forms, menus and checkout are, not on your page count. We give you one fixed quote before any work starts, and we work hard to come in under what agencies charge for the same manual scope. Here's what drives the price.
How long does it take?
That depends on the size of your site and how many issues we find. A typical small business site moves much faster than a large store with a custom checkout. You'll get a timeline with your quote, and if you have a reporting deadline coming up, tell us and we'll plan around it.
Will fixing accessibility change how my site looks?
Barely. Most fixes are invisible: labels, structure, keyboard behaviour. Where something visible has to change, usually contrast, we find the closest accessible match to your brand and show you before it goes live.
Do you give me a certificate?
There's no official AODA or WCAG certificate, and anyone selling one is selling a badge. What you get from us is more useful: a written conformance report listing what was tested, what was fixed and how each fix was verified, plus an accessibility statement for your site. It's the evidence you'd want on hand when you file your compliance report.
Ready when you are
Find out where your site stands.
Send us your web address. We'll take a look and come back with a fixed quote and a plain-English plan. No pressure and no jargon.