Accessibility Statement
This statement applies to this deployment — the sign-in pages and the workspace served from this address. It says how accessible we believe it to be, what we already know is not accessible, and how to tell us when something stops you.
Conformance status
We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This deployment is not compliant with WCAG 2.1 Level AA. Barriers at that level are recorded as open defects against this product, and the main ones are described in the next section. We do not state a proportion of the standard that is met: no evaluation establishing one has been carried out, so any such figure would be invented.
Statement prepared
This is a self-assessment. It is based on this product's own record of open accessibility defects and on testing by the people who build it. It is not an independent audit and has not been reviewed by an external accessibility body.
Known limitations
The barriers below are the ones we know about. This list changes as they are fixed and as new ones are found, and it is not a schedule — it does not promise when any of them will be resolved. Finding something that is not listed here does not mean it is acceptable: please report it.
- Signing in: parts of the sign-in card have been reported as hard to operate with a screen reader or with the keyboard alone, and some of its waiting and error messages are not announced.
- Small screens and enlarged text: some pages scroll sideways or cut content off at a 320 pixel width, or at 200% text size (WCAG 1.4.4 Resize Text and 1.4.10 Reflow).
- Components we did not write: signing in is handled by Keycloak, and some content is rendered by third-party libraries. Removing a barrier in those means an upstream fix, an upgrade or a replacement rather than an edit to our own code, so they can take longer than barriers we own outright.
Reporting a barrier
The organization that operates this deployment has published no address here, so this page cannot give you one. Until it does, report barriers through whoever gave you access to this service.
If you get no answer
Answering is the responsibility of the organization that operates this deployment, not of the people who write this software — it is self-hosted, and the operator holds the relationship with you. If you receive no reply, or the reply does not remove the barrier, take it to that organization's own complaints or equality-of-access procedure; in a hospital or employer deployment that is normally the body that bought this service. This statement names no enforcement body: which one, if any, can take your complaint depends on where you and this deployment are, and only the operator knows that. Ask them, or ask your own national accessibility or equality body.