Accessibility

Last updated: July 2026 (Beta)

Our target

We build DociCA to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard the Accessibility for Ontarians with Disabilities Act (AODA) points to. Ontario is a core jurisdiction for us, so accessible drafting and review is a requirement, not an afterthought.

What is in place

• Automated testing on every change. An accessibility engine (axe-core) runs against our Create, Review, and Trust surfaces in continuous integration, so a new semantic regression — a missing label, name, role, or ARIA state — fails the build before it ships.
• Keyboard operability. Core flows — drafting a document, working through review findings, and navigating the Trust pages — are operable without a mouse.
• Semantic HTML. Headings, landmarks, lists, form labels, and button/link semantics are used so assistive technology can convey structure.

What is not done yet

We are not independently audited or certified for WCAG 2.1 AA, and we do not claim to be. Automated tools catch a large share of issues but not all of them — some AA criteria (colour contrast on live pages, focus order on complex widgets, meaningful sequence) need human judgement, and that review is ongoing. We will state conformance honestly here as it progresses.

Requesting an accommodation

If any part of DociCA is difficult to use with your assistive technology, or you need a document or review provided in an alternate format, email support@docica.cawith “Accessibility” in the subject. Tell us the page and what you were trying to do, and we will help and prioritise a fix. We aim to acknowledge accessibility requests within two business days.