Accessible to
every visitor.
In Canada, accessibility complaints and human rights claims related to websites are increasing. WCAG 2.1 Level AA compliance reduces that risk and makes your site usable by the roughly 22% of Canadians who have a disability. We audit, report, and fix.
Everything you need, none of the upsell.
Real deliverables, with the boundaries written down. So you know what you're paying for and what counts as extra.
Automated and manual review.
Automated scan to find obvious issues, followed by a manual review for context-dependent failures that scanners miss. Both required for a complete picture.
The Canadian standard.
Level AA is the benchmark referenced in Canadian accessibility legislation and procurement requirements. We test and report against AA, not just Level A.
Fix the issues, not just the report.
Issues fixed in your CMS, templates, or codebase. Not just noted in a report and left to your developer.
Retested after fixes.
Post-fix testing to confirm issues are resolved and no new ones were introduced. Written verification report for your records.
The order we work in.
A clear sequence so you can budget time, money, and risk against the work.
Audit.
Automated scan plus manual review of key page templates, forms, and interactive elements.
Report.
Issues documented by WCAG criterion, severity, and page location. Prioritised by impact.
Remediate.
Fixes applied to templates first for the broadest impact, then to individual pages.
Verify.
Retested against the original issue list. Written verification report issued.
More software services
Common questions.
Are we legally required to make our website accessible?
It depends who you are. Federally regulated organisations and Ontario businesses under the AODA have explicit obligations, and BC has been developing requirements under the Accessible British Columbia Act. Many private businesses have no direct statutory duty, but human rights obligations still apply and public sector procurement usually requires it.
What standard should we work to?
WCAG 2.2 at level AA is the practical benchmark and what most legislation references. Level AAA is not expected for general use and some of it is impractical for most sites.
What are the most common failures?
Insufficient colour contrast, images without meaningful alternative text, forms whose fields are not labelled, and interfaces that cannot be operated by keyboard alone. Those four account for the large majority of what an audit finds.
Can accessibility be added afterwards?
Much of it, yes, and retrofitting is normal. What is expensive is a site built on components that were never keyboard-operable, where fixing means replacing rather than adjusting. Building it in is cheaper than adding it, as usual.
Get a quote on web accessibility (wcag).
Tell us a bit about your environment and we'll come back with a scoped proposal in two business days. No obligation, no pressure.
Request a Quote Back to Software