Legal
Accessibility
Everyone who works a case should be able to use the controls to do it. We build to WCAG 2.2 level AA and we hold to the duties that the Accessible Canada Act and the Accessible British Columbia Act set.
We have not completed a formal conformance audit. We do not claim a certificate. What follows is a plain account of what is in place today, what is not, and how to reach us when a barrier appears.
Target
What we aim for
WCAG 2.2 level AA is the target for the marketing site and the application. New parts are built to that bar. Older parts are brought into line as we touch them.
The law matters too. The Accessible Canada Act sets federal duties to identify and remove barriers. The Accessible British Columbia Act sets provincial duties with the same intent. IMECore is a Canadian product and we plan for both.
We do not treat accessibility as a separate layer. It is part of the page structure, the keyboard path, and the copy.
In place today
What is done
The controls that are live on the marketing site and in the application shell today.
Keyboard navigation
You can reach every control with the keyboard. Order follows the visual order. No trap. Menus, dialogs, and forms use native elements that carry focus as expected.
Visible focus
Focus has a visible ring with enough contrast to see. If you move by keyboard, you can tell where you are.
Skip link
Keyboard users can jump past the header to the main content. The link shows on focus.
Semantic headings
Pages use a clear heading order. One h1, then h2 sections, with h3 cards inside. Landmarks mark header, main, and footer.
Reduced-motion support
Reveal and transition effects respect the prefers-reduced-motion setting. If you ask for less motion, you receive it.
Colour contrast
Text, links, and controls aim for the WCAG 2.2 contrast ratios. Colour alone does not carry meaning. Icons carry a label where the shape would otherwise be the clue.
Labelled form fields
Each field has a label linked to the control, a form hint where it helps, and a plain error message where it fails. Error text uses role alert.
Details for FAQ
FAQ sections use native details and summary. They work with JavaScript off and remain readable to answer engines.
Not yet
What is not done yet
An honest list. If a gap below blocks your work, tell us and we will put it near the top.
No formal audit
We have not yet run a third-party WCAG 2.2 audit. The target is level AA, but we do not claim conformance until an independent review says so.
Record PDFs remain hard
Medical record packages arrive as scanned PDFs from many sources. Their accessibility depends on the source. Extracted text in the record view helps, but we have not yet rebuilt the PDF reader to the full AA bar.
Docs and change log
Some older documentation and change log entries carry headings that could be tighter and link text that could be more specific. We fix these as we update the pages.
French language support
The interface is English today. Where we translate, we will use proper language tagging and bilingual labels for form controls.
If you use a screen reader, a keyboard only, voice control, or a high-contrast theme, we want the detail that fails for you. The next section tells you what to include in a note.
Report a barrier
How to reach us
A short note is enough. Include what you tried and what stopped you.
Send a note
Email privacy@imecore.com or hello@imecore.com. Use "Accessibility barrier" in the subject if you can.
Include in your note:
- the page address and the step that failed;
- the browser, operating system, and assistive tool you used;
- what you expected and what happened; and
- whether you need the information in another format.
What we will do
- We will confirm receipt within two business days.
- We will share a plan or a workaround, and a rough time for a fix.
- Where a page blocks a task, we will offer the same information on a call or in an alternative format.
- We will log the barrier against the page so we do not lose it.
If the barrier concerns case data or a specific workspace, do not include claimant names, claim numbers, or medical details in the first note. We will ask for the minimum needed to reproduce the problem.
FAQ
Questions about accessibility
Do you have a third-party conformance audit or a certificate?
No. We have not completed a formal conformance audit and we do not hold a certificate. We build to WCAG 2.2 level AA and we describe openly what is in place and what is not.
How do you handle a barrier that blocks a task?
Email us with the page, the step that failed, and the tool or browser you used. We will confirm receipt within two business days and share a plan or a workaround. You can also ask for the information in another format.
Found a barrier?
Email privacy@imecore.com with the page, the step, and the tool you use. We will answer within two business days.