Accessible websites, tested rather than claimed

The Integrated Accessibility Standards Regulation under the Accessibility for Ontarians with Disabilities Act requires internet websites and web content of organisations with 50 or more employees, and of public sector organisations, to conform with WCAG 2.0 Level AA. Small private businesses under that threshold are not caught by the website requirement — but the accessibility reporting and customer-service obligations under AODA are broader, so it is worth checking your own obligations rather than assuming.

That the site can be operated without a mouse, read by a screen reader in a sensible order, understood without relying on colour alone, and used at 200% zoom without content disappearing. Concretely: text with sufficient contrast, real headings in order, labelled form fields, meaningful link text, visible focus outlines, alt text on images that carry meaning, and captions on video.

No. Overlay widgets that promise instant compliance have been the subject of repeated criticism from accessibility practitioners and disability advocates, and they have not prevented complaints or claims. They sit on top of the problem rather than fixing it, and screen reader users frequently report that they make sites harder to use. Accessibility is a property of the markup, not a script added afterwards.

Automated testing with axe-core against WCAG 2.1 and 2.2 A and AA across every page state, plus a keyboard-only pass through the real journeys — navigation, forms, menus, dialogs. Automated tools catch roughly a third to a half of real issues, which is why the keyboard pass is not optional. This site is tested that way on every build — every page template, at desktop and mobile widths, in its default state and with menus and form errors open — at zero issues at any severity.

Neither, and the trade-off is usually imaginary. Sufficient contrast, real headings, labelled fields and visible focus states are design decisions rather than compromises, and a page built with semantic markup is typically lighter than one built from nested containers. Accessibility work overlaps almost entirely with what makes a site fast, crawlable and quotable.

Our business websites start at C$2,490, and most business projects land between C$2,490–C$4,990. Online stores start at C$3,990, with larger stores typically C$5,900–C$8,900+. What moves a project up the range is page count, custom functionality, integrations, whether we write the content, and multilingual requirements. You get a fixed price in writing before any work starts.

A straightforward business website is usually three to five weeks from approved scope to launch. Larger sites and online stores typically run six to ten weeks. The single biggest factor is how quickly content and feedback come back from your side — we will tell you the honest timeline for your project before you commit, not an optimistic one.

Every site we build includes the technical foundations: page titles, meta descriptions, canonical URLs, structured data, a sitemap submitted to Google Search Console, fast loading, and a sensible page structure. That is what makes a site eligible to rank. Ongoing SEO — content, links, local listings — is separate work, and we will tell you honestly whether you need it or whether InceptiCode should point you at Google Ads instead.