Accessibility
What is done so this site and this application can be read and driven by something other than a mouse, and what is left to do.
Our target, and how it is checked
This product is built for people who work on phones, in trucks, in clinics, often with one hand busy and rarely in silence. Accessibility is not a separate chapter here: it is the same requirement as being readable on a screen in full sun.
We aim for level AA of the international web accessibility guidelines. Part of that is checked by machine and sits inside our publishing gates; another part is checked by hand, screen by screen, and that part is not finished.
This page states both. What is in place, and what is missing — because an accessibility statement listing only successes helps nobody decide whether the tool suits them.
What is in place on the site
- A skip link leads straight to the content, ahead of the navigation
- The structure is built from real headings and real lists, in the order they are read
- Every page declares its language, in French as in English, so screen readers pronounce it correctly
- A minimum text size is enforced, and no information rests on colour alone
- Main content stays readable without scripts, and navigation collapsed on a phone stays present in the page
What is in place in the workspace
- Screens can be traversed by keyboard, and focus stays visible and recoverable after a panel closes
- A screen a role may not open is absent from the menu rather than greyed out — fewer false choices to explore
- Actions that are unavailable are not dressed up as disabled buttons
- Automated accessibility checks are part of the verifications run before publishing
Phone answering itself
- Every call produces a written transcript the owner can read
- Summaries arrive in writing: someone who prefers reading over listening gets the same information
- Written channels — text message, chat, email — allow a request to be handled without speaking
- The voice slows down, repeats and rephrases when the caller asks
What we hold to
- We treat a reported accessibility barrier as a product defect, not as an enhancement request
- We answer a request for information in another format in writing, at the address below
- We keep the automated checks inside the publishing gates, so a regression blocks the release
- We write on this page what is not done yet
What we do not promise
- No external accessibility audit has been carried out, and we display no attestation.
- Manual verification with a screen reader has not covered every screen of the workspace.
- We publish no remediation date: we would rather promise nothing than miss an announced deadline.
- Phone answering remains a voice channel; for someone who cannot use a phone, the written channels take over.
Reporting a barrier
Write to us with the page or screen, what you were using to navigate, and what blocked you. It is the only address published today, and it is read.