Accessibility
What has been tested, what has been fixed, and — the part most statements leave out — what has not been assessed.
Effective date: 18 August 2026
Conformance status: not formally assessed
Coira has not been audited against WCAG 2.1, and this page does not claim conformance to any level. No external evaluation has been carried out and no assistive-technology testing has been done with real users.
That is stated first because the alternative — a conformance claim with no evidence behind it — is the thing that makes these statements worthless. If you need a conformance claim you can rely on for a public-sector bid, ask us and we will tell you plainly that one does not exist yet rather than let you repeat ours.
What has been found and fixed
- Keyboard access to file uploads. Four upload controls were hidden in a way that removed them from the keyboard tab order as well as from view, so they could be operated with a mouse and not reached at all without one. They are now reachable by keyboard, and a check fails the build if that pattern returns. This is WCAG 2.1 Success Criterion 2.1.1 (Keyboard), and it was a real barrier rather than a theoretical one.
- Visible focus. Interactive elements show a focus outline when reached by keyboard, including the upload controls above, where the element the user can see is not the element that receives focus.
- Reduced motion. Animation is suppressed for anyone whose system is set to reduce motion.
- Page language. Pages declare their language, so a screen reader pronounces them correctly.
Known gaps
These are not the only gaps — without an audit, nobody can say what the full list is. They are the ones we know about:
- Dense data tables. Tender comparisons and adjudication matrices carry a lot of columns. They have not been tested with a screen reader, and table semantics have not been reviewed.
- Colour contrast has not been measured across the interface.
- Uploaded documents are passed through as they arrive. A tender pack is supplied by a contracting authority and is frequently a scanned PDF with no text layer. Coira does not make those documents accessible and cannot: the accessibility of a tender pack is a matter for whoever published it.
If something is not usable
Tell us what you were trying to do and what got in the way, and we will treat it as a defect rather than a request. A control that cannot be reached is a bug in the same sense as one that returns the wrong number.