Accessibility statement
This statement covers the R9lab website, the documentation site, and the web app.
How accessible R9lab is
R9lab is pronounced “Relab”. Screen readers may read the name as “R nine lab”.
R9lab aims to meet WCAG 2.2, level AA. It is partially conformant: some of it meets that standard and some has not been assessed.
We target 2.2 because Leiden University’s public sites fall under the EU Web Accessibility Directive through EN 301 549.
This is a self-evaluation by the people who build R9lab. There has been no external audit.
What we check
Every release scans the website and documentation site fully with axe, an accessibility testing tool, against the level A and AA rules for WCAG 2.0, 2.1, and 2.2. The web app is scanned the same way on its public screens and its account screen; colour contrast is excluded from that automated check.
- Every text colour clears 4.5:1 against its background, in both the light and dark themes.
- Buttons, links, and icon controls are at least 24 by 24 CSS pixels, or have equivalent spacing, per WCAG 2.2 success criterion 2.5.8.
- Animations follow your operating system’s “reduce motion” setting.
What we have not checked
These are the gaps we know about.
- Nobody has worked through R9lab by keyboard alone, or with a screen reader.
- Two criteria have no automated test available: 2.4.11 Focus Not Obscured and 2.4.13 Focus Appearance. We check those by hand.
- The app is tested in a browser, so VoiceOver and TalkBack are untested.
- R9lab is in English only.
- Videos are embedded from YouTube. Captions are up to whoever published them.
- The documentation site’s API reference pages use a third-party viewer with two known problems we cannot fix ourselves. Its endpoint lists scroll, but nothing in them takes keyboard focus. One of its MCP links is smaller than 24 by 24 CSS pixels.
Tell us what does not work
If you cannot use something, email info@r9lab.io. Tell us the page you were on and what went wrong.