AODA-Accessible Website Redesign for Ontario Organisations
Since 1 January 2021, Ontario businesses and non-profits with 50 or more employees have had to make their public websites meet WCAG 2.0 Level AA under the Accessibility for Ontarians with Disabilities Act. For many organisations that means more than a quick plugin. Templates, colours, forms and media often need to be rebuilt.
We redesign and rebuild public websites so they work for keyboard users, screen-reader users and people with low vision, then test them with automated tools and assistive technology. The work is done remotely by our team in India. We can show you how each WCAG criterion was handled, but we do not give legal opinions or compliance guarantees.
Request a WCAG review of your Ontario website
Send your website address, the platform it runs on and any accessibility complaints or audit findings you already have.
What an AODA-focused redesign changes on an Ontario website
These are the areas where public sites most often fall short of WCAG 2.0 AA. Each one is designed in and checked, not left as a fix for after launch.
Keyboard-only navigation
Every menu, slider, accordion, modal and form control can be reached and used with the Tab, Enter, Space and arrow keys. Focus stays visible, and it never gets trapped inside a pop-up.
Colour contrast and readable text
Text and interactive elements meet the AA contrast ratios. The site does not rely on colour alone to show errors or status, and pages still work when users zoom text up to twice its size.
Headings, landmarks and page structure
Each page gets one logical heading outline, plus header, navigation, main and footer landmarks. Screen-reader users can then jump straight to the part they need instead of listening to the whole page.
Meaningful alternative text
Informative images get short descriptions written for their context, and decorative images are hidden from assistive technology. Charts and infographics also get a text equivalent nearby.
Accessible forms and error messages
Every field has a visible label tied to it in code, required fields are announced, and errors are explained in words that say how to correct them.
Captions and media controls
Pre-recorded video gets accurate captions and a transcript where useful. Audio and video never play automatically without a way to pause them.
What the AODA website requirement means in practice
The website rules sit in the Information and Communications Standards of the Integrated Accessibility Standards Regulation (Ontario Regulation 191/11). They apply to designated public sector organisations and to private businesses and non-profits with 50 or more employees in Ontario. The organisation that controls the site, directly or through a contract with a supplier, is the one responsible.
Which content is in scope
Public websites, and web content published after 1 January 2012, must meet WCAG 2.0 Level AA, which also includes every Level A criterion. Two criteria are exempt: live captions (1.2.4) and pre-recorded audio descriptions (1.2.5). Internal intranets and extranets of private organisations do not have to meet the AA criteria, but you still have to provide information in an accessible format when someone asks for it.
Smaller organisations planning ahead
If you have fewer than 50 employees, the website rule does not apply to you yet. Many growing firms still choose to build accessibly from the start. Retrofitting a finished design almost always costs more than getting colour, components and templates right first time.
What this page is not
This is a description of a design and development service, not legal advice. If you are unsure whether your organisation is covered, or how to report on compliance, check the Government of Ontario guidance or speak to an accessibility or legal adviser.
Full redesign or targeted remediation for your Ontario site
A redesign makes more sense when
- The theme or page builder outputs inaccessible markup you cannot change
- Brand colours fail contrast checks across most of the site
- Navigation menus, carousels and pop-ups are built on scripts that ignore the keyboard
- The site is also due for new content, structure or a move to a maintained platform
Remediation may be enough when
- The underlying templates are clean and only some components fail
- Problems are mostly content-level: missing alt text, skipped headings, unlabelled links
- Forms need proper labels and error handling but the layout is sound
- You have a recent audit and want its findings fixed in your current WordPress, Laravel or Next.js build
How an Ontario accessibility redesign project runs
Ontario's guidance recommends agreeing a project plan with your developer before work starts. This is the plan we propose, adjusted to your site.
Baseline review
We scan representative templates with automated tools and then check them by hand with a keyboard and a screen reader. You get a list of issues, each mapped to the WCAG 2.0 success criterion it fails.
Agreed scope and plan
A written plan sets out the target (WCAG 2.0 AA), which pages and documents are in scope, the techniques and software we will use, the testing methods, the deliverables and the dates.
Accessible design system
We design colour palettes, type scales, focus styles and components such as buttons, menus, tabs and forms in UI/UX files, checking contrast and states before any page layouts are drawn.
Build and content fixes
We build the components with semantic HTML, adding ARIA only where native elements fall short. Then we rebuild or repair the templates and fix the content: headings, link text, alt text and captions.
Testing before launch
We repeat the automated and manual checks on staging. We also recommend that people with disabilities try key tasks on the site before it goes live, and we fix what they find.
Handover and upkeep
Your editors get short guidance on keeping new pages accessible, and you get a record of the issues resolved. That record helps you show progress if anyone asks.
Testing methods used before an Ontario site goes live
No single tool can confirm WCAG conformance, so we combine several methods. Each one catches different problems.
| Method | What it is good at finding | What it cannot judge |
|---|---|---|
| Automated scans (axe, Lighthouse) | Missing form labels, low contrast, empty links, invalid ARIA, missing page language | Whether alt text is meaningful or a reading order makes sense |
| Keyboard-only walkthrough | Unreachable controls, invisible focus, keyboard traps, illogical tab order | How content sounds to a screen-reader user |
| Screen-reader testing (NVDA, VoiceOver, TalkBack) | Confusing announcements, unlabelled buttons, unhelpful headings and landmarks | Every combination of browser and assistive technology your visitors use |
| Zoom, reflow and colour checks | Text that overlaps or disappears when enlarged, and information shown by colour alone | Problems inside third-party embeds we cannot edit |
| Testing by people with disabilities | Real usability barriers that pass the technical checks | Nothing in particular; we recommend it, but you arrange who takes part |
Why an overlay widget will not fix your Ontario website
Much of what comes up when you search for AODA website compliance is overlay toolbars or audit-only services. A script-based overlay sits on top of the existing code. It does not repair missing labels, broken heading structures or menus that need a mouse, and some screen-reader users switch overlays off because they get in the way. An audit report is useful, but someone still has to change the templates and content.
Our work is the change itself: accessible design files, rebuilt components and corrected content, tested afterwards.
Illustrative Business Scenario
This is an illustrative example, not a real client. A regional non-profit with 60 staff runs a WordPress site built on a page-builder theme. Its donation form has placeholder text instead of labels, its brand teal fails contrast on white, and the mobile menu cannot be opened with a keyboard. After a baseline review, the sensible plan would be a new accessible theme with a slightly darker teal, a rebuilt form and native button-driven menus. Existing pages would be moved across with corrected headings and alt text.
Working from India with Ontario teams
Our team is in India, which is 9.5 to 10.5 hours ahead of Ontario depending on daylight saving. In practice, feedback you send at the end of your day is usually worked on overnight. We arrange calls for your morning or our late evening, and decisions are written down so that nothing depends on a single meeting.
Hours and monthly retainers are listed on our published rate card. A fixed quotation depends on how many templates, forms and documents are in scope after the baseline review.
Who designs and tests your Ontario website
Appeonix Creative Lab has been working since 2014. We are a micro enterprise registered under Udyam in Thrissur, Kerala, with a further office in Indiranagar, Bengaluru. The business name is also registered in Ontario (BIN 1000946232), but that registration is not a service office: all design, development and testing is done by our team in India. You keep ownership of your hosting, CMS and domain accounts, and you can remove our access whenever you choose.
Related Appeonix services for Ontario organisations
AODA website questions from Ontario organisations
Does our organisation have to meet the AODA website rules?
The requirement applies to designated public sector organisations and to Ontario businesses and non-profits with 50 or more employees, for public websites and web content published after 1 January 2012. If you are close to that threshold or unsure, check the Government of Ontario guidance or ask an adviser. We can build to WCAG 2.0 AA either way.
Will you certify that our website is AODA compliant?
No. We are not a certifying body and we do not give legal guarantees. We give you the issues found, the WCAG criterion each one relates to, what was changed and how it was tested. You can use that record in your own compliance work or hand it to an independent auditor.
Do PDFs and downloadable documents on our site need attention too?
Documents published on a public site are usually treated as web content, so we include them in the baseline review. Often the simplest fix is to turn key documents into accessible web pages. Where a PDF has to stay, we can give you guidance on tagging it and adding headings and alternative text.
Can you fix our existing WordPress site instead of replacing it?
Often, yes. If the theme's markup is sound, we repair the components that fail and correct the content in place. If the theme or page builder produces markup that cannot be made accessible, we will tell you so and explain why a new theme would cost less in the long run.
How do reviews work when your team is 9.5 to 10.5 hours ahead of Ontario?
We share staging links and a written list of changes at the end of each working stage, so you can review during your business day. Your comments are usually picked up overnight. Calls are booked for your morning, and every decision is recorded in writing.
Find out where your Ontario website stands against WCAG 2.0 AA
Send us your website address and the pages that matter most. We will review a sample with a keyboard, a screen reader and automated tools, then reply with the main barriers and whether we think redesign or remediation fits.
Send an enquiry WhatsApp +1 548 388 2040