Accessibility remediation for websites and web applications in Ontario: developers who fix WCAG failures at the code level — HTML, CSS, ARIA, scripts, templates and CMS — verify each fix with assistive technology, and leave you with evidence of conformance, not a list of tickets.
The fix goes where the barrier lives
An accessibility barrier is a defect. It has a location in the code, a cause, and a fix, and the fix is verified the way any defect fix is verified: by trying the thing that failed and watching it succeed. That is the whole of our method, and it is why we describe remediation as engineering rather than compliance.
Most barriers live in templates and components, which means most fixes are cheaper than the audit made them look. A heading structure fixed once in a page template is fixed on every page; a form component repaired once is repaired on every form. We plan remediation around that: template fixes first, ordered by the journeys they block, quick wins in the first week.
Evidence, not tickets
When the work is done you hold a closed findings register — every barrier, its criterion, its fix, and the assistive technology it was verified with — and a re-test of the full scope. That register is the evidence behind a truthful compliance report, the basis of an Accessibility Conformance Report if a buyer asks for one, and the record you show if anyone ever asks how you know. Overlays and widgets that promise compliance in a line of JavaScript produce none of this; we do not use them, and we will explain why if you are being sold one.
What we remediate
Any stack, any CMS — the fix goes where the barrier lives
Templates and components
Headings, landmarks, names, focus order, keyboard operation, contrast, motion. Fixed once in the template, fixed on every page that uses it.
Forms and errors
Labels, instructions, required fields, error identification and suggestion, timeouts — the criteria most often failed and most costly to the person filling the form.
Scripts and widgets
Menus, tabs, dialogs, carousels, date pickers and the third-party embeds that come with none of it. Replaced or repaired to the ARIA authoring practices, then tested with a screen reader.
Content management systems
WordPress, Drupal, Craft, custom — themes, plugins and editor configuration, so the site stays accessible after the people who publish to it take over.
Media
Captions, transcripts, audio description where required, and the player controls that make them reachable.
Documents
The PDFs, Word and PowerPoint files the site links to, through our document remediation service.
How remediation runs
Start from findings
Yours or ours. If you have an audit report from anyone, we work from it. If you have none, a short audit comes first, because you cannot fix what has not been found.
Plan by impact
Barriers that block a journey first; template fixes before page fixes; the quick wins in the first week so your users feel the difference early.
Fix and verify
Every fix is tested with the assistive technology the barrier affected — screen reader, keyboard, zoom — and recorded against its success criterion.
Hand over with evidence
A closed findings register, a re-test of the whole scope, and if you need it, an Accessibility Conformance Report. Your team gets the patterns and the reasons, so the next feature ships accessible.
Who commissions remediation
Organizations holding an audit report
From us or anyone else. Findings age; a report on a shelf is a liability. We turn it into closed tickets.
Public-sector web teams
Who own the site but not the capacity, and need a vendor who can be procured quickly — we are an Ontario Vendor of Record — and who can work inside their CMS and their change process.
Organizations that received a complaint
A complaint under the Ontario Human Rights Code or a direct request from a user is a deadline. We triage the barrier named, fix it first, and then the rest.
In our clients' words
We worked with Imran and the Cantan Group team to ensure our various websites met the requirements of Ontario’s AODA and U.S. ADA legislations. Imran and his team went above and beyond to ensure all our sites exceeded AODA compliance, while delivering an online experience that’s accessible to all visitors.
Black & McDonald
Cantan Group consistently delivers excellent service and support. We highly recommend Imran and his team to anyone looking to improve their website's performance and accessibility.
Do you need to have done the audit to do the remediation?
No. We work from any competent findings report, and we re-test as we go, so the findings become verified rather than taken on trust. If your report is a scan export with no manual findings, we will tell you what it is missing before we quote.
Will remediation change how the site looks?
Rarely, and never without agreement. Most fixes are invisible: structure, names, keyboard behaviour, code. Where a barrier is a design decision — a colour that fails contrast, text over an image — we propose the smallest visible change that meets the criterion, and your designer decides.
Can you work inside our CMS and our deployment process?
Yes. We remediate inside WordPress, Drupal and Craft themes, inside component libraries, and inside custom applications, through your repository and your review process. We have no interest in owning your site; we want to leave it in a state your team can maintain.
How is remediation priced?
As a fixed fee for a defined scope — a findings register with an agreed list of criteria and pages — or as a retainer for teams that want an accessibility developer on call. Either way the price follows the findings, which is why the audit or your existing report comes first.
What happens after remediation?
Sites regress. New pages, new plugins, new editors. ACHECKS monitors the site continuously and tells your team, with the line number, when something slips. Many clients pair remediation with monitoring so the next compliance report is a formality.