AODA website accessibility 2026 requirements apply to any organisation that falls under the Integrated Accessibility Standards Regulation. Ontario’s reporting portal confirms December 31, 2026 as the deadline for businesses and non-profits. If your website is not accessible, this is the year to fix the foundation, not the week before you file.
This is a practical guide for business owners, non-profits, and organisations in Toronto and Ottawa who want to understand what to check, what to fix, and how to reduce risk without getting lost in technical language.
GET YOUR WEBSITE READY AHEAD OF TIME
Want help turning this information into a clean, documented remediation plan?
What is the AODA Accessibility Compliance Report, and who files it?
Ontario provides a formal Accessibility Compliance Report process and the Accessibility Compliance Reporting Portalwhere organisations submit their report. Start with Ontario’s guide and portal here:
- Guide: https://www.ontario.ca/page/completing-your-accessibility-compliance-report
- Portal: https://accessibilityreporting.ontario.ca/
Ontario’s portal also states the next reporting deadline for businesses and non-profits as December 31, 2026.
The key practical point for your website work
- Filing a report is not the same thing as making your website accessible.
- A website accessibility overlay is not the same thing as remediation.
- If you are asked to confirm compliance, you want evidence: an audit summary, a fix backlog, what changed, and validation notes.
If you are not sure where your organisation stands, start with an accessibility audit that maps issues to:
- Templates (header, footer, navigation, page builder sections)
- Forms (contact, booking, checkout, quote)
- PDFs and downloads
- Third-party embeds (maps, booking widgets, chat widgets, payment tools)
What does Ontario require for websites and web content?
Ontario’s Integrated Accessibility Standards Regulation (IASR) includes requirements for accessible websites and web content. The regulation text is published by Ontario:
https://www.ontario.ca/laws/regulation/110191
The regulation includes explicit WCAG conformance language, including WCAG 2.0 Level AA for websites and web content.
In practice, most remediation projects use WCAG success criteria as the testable checklist. WCAG is published by the W3C:
https://www.w3.org/WAI/standards-guidelines/wcag/
A useful way to think about it
- WCAG defines testable outcomes, not “nice to have” design preferences.
- Accessibility is a system problem. If one template pattern is broken, dozens of pages inherit the problem.
- You will usually get better, faster results by fixing templates and reusable components first.
The fastest way to assess your risk, a 15-minute triage anyone can do
You can learn a lot about your risk level without special tools. Here is a quick triage:
1) Can you use your site with only a keyboard?
Try this in Chrome or Safari:
- Press Tab to move forward through links and controls.
- Press Shift + Tab to move backward.
- Use Enter or Space to activate buttons and controls.
Red flags:
- You cannot reach a menu item or button.
- A popup opens and you cannot exit it without a mouse.
- Focus is “invisible”, you cannot see where you are.
2) Are your forms label-safe and error-safe?
Open your contact form or booking form and check:
- Does every field have a visible label, not just placeholder text?
- If you submit with missing required fields, are errors specific and tied to the right field?
- Can you submit using only a keyboard?
Forms are one of the most common failure points because they are also the most customised part of many sites.
3) Do your key pages pass basic contrast checks?
Look at:
- Buttons on banners and hero sections
- Text over images
- Low-contrast grey text
- Navigation links in headers and footers
Contrast failures often appear after a redesign, brand refresh, or theme update.
4) Are your PDFs readable with assistive tech?
If you upload PDFs like menus, brochures, application forms, or onboarding packages, test one:
- Can you select text in a normal reading order?
- Are headings obvious?
- Is it a scanned image, or real text?
PDFs can easily become an accessibility liability even when the website looks fine.
5) Are embedded maps, booking tools, and third-party widgets accessible?
Common embeds:
- Appointment booking widgets
- Chat widgets
- Store locators and maps
- Payment or donation widgets
If accessibility breaks inside an embed, users still experience the failure on your site.
If any of these tests fail, plan remediation as a real project with a backlog and validation. Patchwork usually does not hold up.
Website accessibility checklist for WordPress and custom builds (AODA-focused)
Use this as your implementation plan for developers and content editors. Accessibility problems are often recurring template issues, so consistency matters more than one-off fixes.Structure and navigation
- One H1 per page, logical H2 and H3 structure.
- Menus, dropdowns, and mobile navigation work with keyboard and do not trap focus.
- A visible focus state exists for links, buttons, and form fields.
- A skip-to-content link exists where appropriate.
- Page builder sections do not break heading structure.
Forms and conversion pages
- Every input has a label, and the label is programmatically associated with the input.
- Required fields are clearly indicated and errors are specific.
- Validation errors are announced in a way users can understand.
- Buttons are real buttons, not divs styled like buttons.
- CAPTCHA solutions do not block real users, and alternatives exist where possible.
Images and media
- Informational images have meaningful alt text.
- Decorative images use empty alt text so screen readers skip them.
- Icons that convey meaning have accessible names.
- Videos have captions where appropriate, especially for core content or instructions.
Content and design
- Link text makes sense out of context, avoid “click here”.
- Colour is not the only way meaning is conveyed, for example error messages.
- Tables are used only for data, with headers defined.
- Lists are real lists, not paragraphs forced into list-looking shapes.
PDFs and documents
- PDFs are tagged properly with headings and reading order.
- Scanned PDFs are remediated or replaced.
- Download links indicate file type, for example PDF, and ideally file size.
Technical items that often get missed
- ARIA is used carefully and only when needed, because incorrect ARIA can make things worse.
- Modals do not trap keyboard focus.
- Sliders and carousels can be paused and do not hijack focus.
- Cookie consent banners are keyboard-usable and readable.
If you want these fixes to stick, implement them at the template and component level, then create a short publishing checklist for anyone adding pages, posts, or PDFs.
Common mistakes we see in Toronto and Ottawa websites
“We installed an accessibility plugin, so we’re done”
Plugins and overlays can flag issues, but they do not fix underlying template problems. Many accessibility failures live in:
- Navigation and menus
- Forms and validation
- Popups and modals
- PDF workflows
- Page builder content structure
“Our theme is accessible”
Themes can help, but custom sections, page builder layouts, popups, and third-party widgets often introduce failures even on a good theme.
“Accessibility is only for public sector”
Ontario’s reporting portal and guidance explicitly cover businesses and non-profits, and the next reporting deadline is stated as December 31, 2026
How to get compliant without blowing up your site or your schedule
A realistic approach is phased. This reduces risk and prevents the “big redesign that breaks everything” problem.
Phase 1, audit and prioritise (typical range: 1 to 2 weeks)
Deliverables that matter:
- A list of issues grouped by severity and template type
- Reproduction steps and recommended fixes
- Affected URLs and page templates
- A remediation backlog you can assign to a developer
Practical priority order:
- Conversion blockers: forms, booking, checkout, donation
- Template elements used everywhere: header, footer, navigation, buttons
- High-traffic pages: home, services, contact, top landing pages
- PDFs and downloads
- Third-party embeds
Phase 2, remediation sprint (typical range: 2 to 6 weeks)
The fastest wins usually come from template-level fixes:
- Heading structure and components
- Keyboard navigation patterns
- Form labels and error handling
- Contrast fixes for UI elements
Then move to content-level fixes:
- Alt text rules and cleanup
- Link text improvements
- PDF remediation workflow
Phase 3, validation and ongoing checks (monthly)
Accessibility regressions happen after:
- Theme updates
- Plugin changes
- Page builder edits
- New content uploads, especially PDFs
Set up a basic monthly check that includes:
- Keyboard-only test of key templates
- Spot checks on forms
- Review of new PDFs uploaded in the last 30 days
If you also run marketing campaigns, it is worth validating tracking after remediation. If you want a single internal link for that, use:
Affordable SEO, PPC, Google Ads, Social Media
Need help? AODA and WCAG remediation support from iWEBAPP
If you want a clear plan with practical deliverables, iWEBAPP can help with:
- Website accessibility audit and remediation roadmap
- WordPress and custom theme remediation
- Forms, booking, and checkout accessibility fixes
- PDF and content remediation workflow
- Technical SEO and performance checks while changes are deployed
Toronto: https://www.iwebapp.ca/toronto-website-design-company/
Ottawa: https://www.iwebapp.ca/agency/ottawa-web-design-company/
Frequently Asked Questions
We would love the opportunity to work with you, but we understand that you may have some additional questions. This quick Q&A covers a lot of the basics. If you have any additional questions, don’t hesitate to reach out.
When is the AODA Accessibility Compliance Report due for businesses and non-profits?
Ontario’s guidance and the Accessibility Compliance Reporting Portal state that the next reporting deadline for businesses and non-profit organisations is December 31, 2026. Start by reviewing Ontario’s instructions, then file using the reporting portal.
Guidance: https://www.ontario.ca/page/completing-your-accessibility-compliance-report
Where do we file the AODA report?
Ontario provides the Accessibility Compliance Reporting Portal where organisations submit their Accessibility Compliance Report and manage drafts and previously submitted reports. You can access it here:
What standard is used to evaluate whether a website is accessible?
For website remediation work, teams typically use WCAG success criteria as the testable standard because WCAG defines how to make web content more accessible and provides measurable conformance outcomes. WCAG is published by the W3C here:
https://www.w3.org/WAI/standards-guidelines/wcag/
Ontario’s IASR regulation references WCAG 2.0 Level AA conformance for websites and web content:
Does an accessibility overlay solve AODA website compliance?
What parts of a website usually fail accessibility checks first?
- Navigation patterns that do not work by keyboard
- Forms with missing labels, unclear errors, or focus issues
- Low-contrast buttons and text over images
- Popups and modals that trap focus
- PDFs that are not tagged or are scanned images
This is why template-level remediation usually delivers the fastest improvement.
We use WordPress and a page builder, is accessibility still possible?
How long does accessibility remediation take?
- 1 to 2 weeks for audit and a prioritised backlog
- 2 to 6 weeks for remediation, starting with templates and forms
- Monthly validation checks to prevent regressions
If your site has a large PDF library or many third-party widgets, plan extra time for those items.
What should we ask for in an accessibility audit deliverable?
Ask for deliverables that your developer can act on:
- Issues grouped by severity and by template type
- Clear reproduction steps
- Recommended fix approach, not just a tool screenshot
- List of affected URLs
- A remediation log format for tracking what changed and when
Can we fix accessibility without redesigning the whole site?
- Navigation and focus behaviour
- Forms and validation
- Contrast and typography choices
- Component markup
- PDF tagging workflows
A redesign can help, but it is not required to get meaningful accessibility improvements.
Turn your website into a search-driven growth engine
Boost Your Rankings with AI-Powered Semantic SEO
Take the next step toward higher visibility and stronger conversions.
