Accessibility
An interface that is hard to operate is a safety problem
Discharge planning is done under time pressure, often by people who have been at a screen all day. That makes accessibility a clinical concern here, not a preference.
Practice
What we do
- Semantic HTML, with headings in order and landmarks on every page.
- Everything operable by keyboard, with a visible focus indicator and a skip link.
- Status carried by text as well as colour, so meaning survives greyscale and a screen reader.
- Colour contrast measured against WCAG AA and pinned by automated tests, so a palette change cannot quietly break it.
- Automated accessibility checks on every release, run against the pages a user actually reaches.
- Form fields labelled properly, with errors summarised and linked to the field they belong to.
- Motion honours
prefers-reduced-motion, so transitions can be switched off at the operating system.
Honestly
What we have not finished
Automated checks catch a minority of accessibility problems. Publishing a conformance claim on the strength of them would be the same mistake as a compliance badge.
No manual AT audit yet
We have not completed a manual audit with assistive technology, and we do not claim conformance to a WCAG level.
High-contrast mode designed, not shipped
A distinct high-contrast token set is specified and not yet built.
No VPAT
If your procurement needs one, tell us — it is a reasonable thing to ask for and we would rather know it is blocking than guess.
Tell us
If something blocks you, we want to know
Accessibility reports go to the front of the queue.