Last updated: October 26, 2026. Prices reflect publicly posted vendor pricing as of that date. We'll revise this guide after the December 31, 2026 reporting deadline.
What does an AODA website audit cost in 2026? A proper manual AODA website audit typically runs $1,500 to $8,000 CAD for a small or mid-sized Ontario business. Fixing what the audit finds often costs as much again, or more. You'll also see AODA audits advertised for $299, which is where most of the confusion starts. This guide explains what you get at each price point, who is legally required to do any of it, and when it's smarter to rebuild than to patch.
AODA website audit cost in 2026: the short answer
These ranges are based on publicly posted vendor pricing and market ranges available as of October 2026. They are illustrative, not quotes.
| What you're buying | Typical 2026 cost (CAD) | What it really is |
|---|---|---|
| Automated scan or light review | $300–$1,000 | A tool run across your pages, sometimes with a short summary |
| Focused manual audit, small brochure site | $1,500–$3,500 | A person testing key pages by keyboard and screen reader |
| Full manual AODA/WCAG audit | $3,000–$8,000 | Templates, forms and user flows tested against WCAG success criteria |
| Complex site, e-commerce or portal audit | $6,000–$15,000+ | Checkout, filters, logged-in areas, dynamic components |
| Audit plus remediation | $5,000–$25,000 | Audit, developer fixes and retesting |
A quote under $500 is almost never the same product as a full manual audit. It can be a useful first look. It can't tell you whether someone using a screen reader can book an appointment on your site.
One more thing to keep in mind as you compare prices: no vendor can guarantee legal compliance from an audit alone. What you're paying for is documented testing, evidence of remediation and a plan you can defend.
Why AODA audit quotes range from $299 to $15,000+
The market sells very different products under the same label. Lead Web Studio advertises a $299 audit. aoda-training.ca puts a professional compliance audit at $3,000 to $8,000. Accessibility Partners cites $2,500 to $15,000. Other Canadian firms quote up to $25,000 once fixes are included.
These numbers aren't necessarily dishonest. They describe different amounts of human testing, different scopes and different deliverables. The right spend depends on three things:
- how much legal and commercial risk you carry
- how large and interactive your site is
- what you plan to do with the findings
Automated scan vs. manual audit vs. audit-plus-fixes
| Automated scan | Manual audit | Audit + remediation | Ongoing monitoring | |
|---|---|---|---|---|
| What it checks | Missing alt attributes, contrast ratios, empty links, some missing labels | Keyboard flow, screen-reader output, focus order, forms, modals, context | Everything in a manual audit, plus the fixes and a retest | New pages and regressions over time |
| What it misses | Most real usability barriers, such as whether alt text makes sense or menus trap focus | Anything that changes after the audit date | Future content your team adds | Deeper manual issues, if it relies on tools only |
| Typical cost | $300–$1,000 | $1,500–$15,000+ | $5,000–$25,000+ | Monthly fee, often tool-based |
| Best for | A quick baseline or triage | Understanding real scope and risk | Organizations that need the site fixed | Sites that publish often |
| Not enough when | You need evidence of conformance | Nobody is assigned to fix the issues | The platform itself is the problem | It's your only accessibility effort |
Automated tools are good at a narrow set of checks. Here's what they can't do:
- tell whether a mobile menu opens with the keyboard
- hear whether a screen reader announces a form error
- spot a cookie banner that traps focus
- notice a checkout button labelled only "Click here"
Those are the barriers that stop real people, and only a person can find them.
Templates matter more than page count
Good auditors price by templates and components, not just URLs. A 200-page site built on five clean templates can be cheaper to audit than a 40-page site with a dozen unique layouts, three form plugins, an embedded booking widget and a custom product configurator.
Once a blog post template has been tested, the 150 posts that use it add very little work. Each unique interactive component, on the other hand, is new work. Accessible.org prices this way: $100 to $250 USD per primary page or screen, and $25 to $100 for lighter ones.
What a proper AODA website audit should include
Use this list to judge any quote. A solid manual audit should include:
- Every issue mapped to a specific WCAG success criterion
- Keyboard-only testing of navigation, menus, forms and modals
- Screen-reader checks, for example NVDA or JAWS on Windows and VoiceOver on Mac and iOS
- Colour contrast for text, buttons, focus states and form fields
- Heading structure and landmarks (header, nav, main, footer)
- Form labels, instructions and error messages
- The quality of alternative text, not just whether it exists
- PDF, video and audio review, if in scope
- Responsive and mobile checks, including zoom to 200% and reflow
- A prioritized issue log with screenshots, severity ratings and remediation guidance
Testing standard: WCAG 2.0 AA, 2.1 AA or 2.2 AA?
Ontario's AODA website requirement names WCAG 2.0 Level AA, with two exceptions: live captions and pre-recorded audio description. That's the legal bar.
Many modern audits test against WCAG 2.1 AA or 2.2 AA instead. These newer versions add criteria for mobile, low vision and cognitive accessibility, such as reflow, target size and focus visibility. Testing to a newer version gives you better risk reduction.
It also lines up with US practice. WCAG 2.1 AA is referenced by the US Justice Department's Title II rule for state and local governments, and WCAG is the common practical benchmark in US accessibility work.
Ask each vendor which version they test against, and why.
Audit reports developers can actually use
A 90-page PDF full of generic WCAG quotations is hard to act on. The most useful deliverable is a spreadsheet or ticket backlog where each row includes:
- the affected URL or component
- the WCAG criterion
- evidence, such as a screenshot or recording
- a severity rating
- a recommended fix
- an owner
Your developers can work straight from that. If you don't have developers, a web development team that can audit, fix or rebuild your site can take the backlog and close it out.
Do you legally need an AODA-compliant website?
Here's the plain-English version. This is general information, not legal advice. Confirm current requirements on Ontario.ca and the Accessibility Compliance Reporting Portal, and speak to a lawyer if your situation is unclear. For a broader look at what compliance involves, see our guide to AODA-compliant websites in Toronto before 31 December 2026.
The 50-employee website rule
Under O. Reg. 191/11, private and non-profit organizations with 50 or more employees in Ontario must make their public websites and web content conform to WCAG 2.0 Level AA. This has applied since January 1, 2021.
The rule has limits:
- It covers websites and content you control directly, or through a contract that lets you modify the product.
- The live captions and audio description exceptions apply.
- The regulation includes language for cases where meeting the requirement is not practicable. That is a narrow carve-out, not a general opt-out.
The 20-employee reporting rule and the December 31, 2026 deadline
Reporting is a separate obligation. Businesses and non-profits with 20 or more Ontario employees must file an accessibility compliance report every three years. The next report is due December 31, 2026.
As of this update on October 26, 2026, that's a little over nine weeks away. There's no need to panic, but there's no slack either. You still have time to scope the work, audit, fix the worst issues and document a plan.
The report is a self-declaration about whether you're meeting your obligations. You want to know where you actually stand before you sign it.
What if you have fewer than 50 employees?
Under AODA's website-specific WCAG rule, organizations with fewer than 50 Ontario employees don't have the same legal obligation to make their websites conform to WCAG. We won't pretend otherwise. If you have 20 to 49 employees, the reporting rule above may still apply to you.
Accessibility can still be worth doing for business reasons:
- Accessible sites tend to be cleaner for search engines, which supports your SEO and digital marketing.
- Clearer forms and better contrast usually convert better.
- Larger clients and public-sector buyers increasingly ask about accessibility during procurement.
Depending on your situation, contracts or human rights obligations may also come into play. Treat it as a business decision, not a legal emergency.
AODA website audit cost by site type: four examples
These figures are illustrative, not quotes. Real numbers depend on what the audit finds.
Example 1: 10-page service business website
- Audit: $1,500–$3,500
- Audit plus fixes: $3,000–$8,000
Common issues:
- low-contrast text and buttons
- skipped heading levels
- missing or useless alt text
- unlabelled contact form fields
- invisible focus states
- a mobile menu you can't open with a keyboard
- vague calls to action
On WordPress, fixes often happen in the theme. On Webflow or Framer, most issues can be fixed in the designer, but some built-in components have limits you'll need to work around.
Example 2: WordPress or Webflow site with blog and forms
- Audit: $2,500–$6,000
- Audit plus fixes: $5,000–$12,000
The cost goes up because of things you didn't build yourself:
- theme markup you can't easily change
- form plugins with poor error handling
- cookie banners that trap focus
- embedded maps, chat widgets and booking tools
- templates that drifted apart over years of edits
Example 3: Shopify or WooCommerce store
- Audit: $4,000–$10,000
- Audit plus fixes: $8,000–$20,000+
Stores have a lot of interactive parts. Frequent problem areas include:
- product filters
- variant selectors, such as size and colour swatches
- cart drawers
- review widgets
- subscription apps
- discount popups
Third-party apps are the wild card, because you can't always fix their code. Sometimes the answer is to replace the app.
Example 4: Portal, web app or logged-in experience
- Audit: $6,000–$15,000+
- Audit plus fixes: $15,000–$50,000+
Dashboards, dynamic React components, modals, data tables, authentication flows and role-based views all need testing, often across several user types. Error messages that appear and disappear without being announced to screen readers are a classic barrier.
This work sits between web development and custom software development for portals and complex web applications. If you're planning a new portal, our breakdown of customer portal development cost in Canada shows how to budget for it. Accessible patterns start at the design stage, which is where UI/UX design for accessible, keyboard-friendly interfaces pays off.
What drives AODA audit pricing
To predict a quote, look at these variables:
- Unique templates and components. This is the biggest single factor.
- Interactive features. Menus, sliders, tabs, accordions and modals all add testing time.
- E-commerce. Product pages, filters, cart and account areas.
- Forms. Especially multi-step forms and custom validation.
- PDFs and media. Document remediation is often priced separately.
- Third-party tools. Booking, chat, payments and reviews.
- Design system maturity. With consistent components, you fix something once and it's fixed everywhere.
- Code quality and CMS or theme constraints.
- Urgency. Rush timelines cost more.
- Reporting format. A ticket backlog takes more work to prepare than a summary.
- Who fixes the issues. Your team or the vendor.
Audit-only, monitoring or remediation: what to buy
When an audit-only engagement is enough
An audit on its own makes sense in a few situations:
- You have an in-house dev team.
- You need a document for procurement or legal review.
- You want to understand the scope before setting a budget.
Be clear on one point: an audit does not make your site compliant. It tells you what's wrong. Nothing changes until someone fixes it.
When to buy audit plus remediation
This is the right path when your platform is fundamentally sound and the issues are fixable.
Fix blockers first: navigation, forms, checkout and your key conversion pages. Then document three things:
- what you've fixed
- what's scheduled
- what depends on third parties
That record is useful evidence when you prepare your compliance report.
Monitoring is a sensible add-on afterwards, especially if your team publishes often. It catches regressions. It doesn't replace periodic manual testing.
When a rebuild is cheaper than patching
Sometimes the audit shows that the problem is the foundation itself. Rebuilding often costs less than patching if you have:
- an old WordPress theme carrying 30 plugins
- a Shopify store with brittle custom code layered on a dated theme
- a slow front end where every component needs rework
When the remediation estimate gets close to the cost of a new site, a new site usually wins. A rebuild also gives you speed, SEO and conversion improvements that patching won't. If you're weighing the options, independent technology consultancy can help you make the call before you commit budget.
We build with accessibility in scope from the start, then test and remediate against the agreed WCAG target. Depending on budget and needs, that might be Next.js, WordPress, Shopify, Webflow or Framer. Paired with web design that makes the next step obvious, accessibility becomes part of the build rather than an afterthought.
Do overlays or badges make you AODA compliant?
Not on their own. Overlays and widgets are the toolbar icons that promise instant compliance. An overlay alone is not evidence of WCAG 2.0 AA conformance. It doesn't fix the underlying code, content, keyboard traps, forms or checkout flows, and overlays have a poor track record with many screen-reader users.
A site that uses a widget can still be accessible, but only if the underlying site has been fixed. In that case, the widget isn't what makes it accessible.
Badges deserve the same scepticism. AODA has no official "certified" badge. A badge may signal good intentions, but it doesn't prove that people with disabilities can use your site. Spend the money on real fixes.
AODA penalties: the real risk
The commonly cited maximums are up to $100,000 per day for organizations and up to $50,000 per day for individuals, including directors and officers (aoda-training.ca). These are ceilings, not typical outcomes. Confirm the current figures on Ontario.ca.
Some sources report that actual penalties are much lower. Accessibility.works suggests a typical range of $500 to $15,000 and says the daily maximum has never been applied. We haven't independently verified those figures, so treat them as indicative.
For most businesses, the more immediate risks are practical ones:
- a lost procurement bid
- a customer complaint
- a frustrated user who goes to a competitor
AODA vs. ADA vs. Accessible Canada Act
| Law | Applies to | Web standard referenced |
|---|---|---|
| AODA | Ontario organizations. Website rule at 50+ employees, reporting at 20+ | WCAG 2.0 AA, with exceptions |
| Accessible Canada Act | Federally regulated entities such as banks, telecoms and interprovincial transport | Accessibility plans, progress reports and federal standards |
| ADA (US) | Title II's WCAG 2.1 AA rule applies to state and local governments. For private businesses, website obligations depend on context, court decisions and DOJ guidance | WCAG 2.1 AA for Title II. WCAG is the common benchmark elsewhere. Check current Title II dates on ADA.gov |
If you sell into both countries, WCAG 2.1 or 2.2 AA is a sensible common testing benchmark. It's not a substitute for checking the rules that apply to you.
How to compare AODA audit quotes
Ask every vendor the same questions:
- Which WCAG version and level are you testing against?
- Is testing automated, manual or both? How many hours are manual?
- Which pages and templates are in scope?
- Which devices, browsers and screen readers do you use?
- Are PDFs and media included?
- Is remediation included? If not, who fixes the issues?
- Is there a retest after fixes?
- Do we get developer-ready tickets, or only a PDF?
- What's explicitly excluded?
- How do you handle third-party tools that fail and that we can't change?
If a vendor can't answer these clearly, that tells you a lot.
A practical timeline before the December 31, 2026 deadline
Starting in late October, a realistic plan looks like this:
- Week 1: Agree on scope and a representative sample of templates and key user flows.
- Weeks 2–3: Run the audit and produce the issue backlog.
- Weeks 4–6: Fix high-priority blockers in navigation, forms, checkout and key pages.
- Weeks 7–8: Retest, and document what's fixed and what's scheduled.
- Final week: Gather your evidence and prepare the report.
An audit and partial remediation don't guarantee anything about your filing. They do give you an accurate picture and a credible plan, which beats signing a declaration on a guess.
How Eskore can help
Whatever your AODA website audit costs, it's only worth paying for if it leads to fixes. We're a web development studio, not an overlay vendor. We can help you in three ways:
- scope your audit
- fix your existing site
- rebuild it, when that's the better business decision
Whichever route you take, we'll look for speed and search improvements along the way.
We work in Next.js, React, WordPress, Shopify, WooCommerce, Webflow, Framer, Tailwind and Vercel, so the recommendation follows your site, not our preferences. You can see our web and software work for examples.
If you're not sure whether you need a scan, an audit, fixes or a new site, book a free 30-minute scoping call. We'll look at your site, tell you honestly what we'd do, and give you a realistic number for the AODA audit and remediation before the year-end deadline.
