Web accessibility and AODA
Find the barriers on your site, fix them, and give your team a way to keep them from coming back.
What is included
The usual scope. We adjust it to your systems, team and budget, in writing, before work starts.
- A WCAG 2.2 AA review using keyboard, screen reader and automated checks
- A prioritized list of issues, written in plain language
- Remediation in your theme, templates and content
- Accessible components and patterns your team can reuse
- Guidance for editors on headings, links, images and documents
A straight answer
An automated scan alone cannot confirm compliance, and this is not legal advice. What applies to you under AODA depends on your organization.
How it runs
Understand
We agree on your audience, goals, constraints and what success has to look like before anything is designed.
Plan
You get a page structure, a written scope and a delivery sequence, so you know what is being built and in what order.
Build
We work in visible increments with a working preview you can click through, and review points along the way.
Launch and improve
We check the launch, watch the essentials, and agree the next improvement based on what the numbers show.
Accessibility: common questions
Is an accessibility overlay enough?
No. Overlays do not fix the underlying code and can make things worse for screen reader users. We fix the site itself.
Do we need to comply with AODA?
Many Ontario organizations do, depending on size and sector. Check your obligations with the Ontario government guidance or a legal adviser. We handle the technical work.
How do we keep the site accessible after the fixes?
Through accessible templates, an editor checklist, and a review whenever new components are added.
Web design and development
Website maintenance
Headless WordPressBring us the problem, not a polished brief
Tell us what needs to work better. We reply with useful questions and a clear next step, including whether we are the right fit.