Accessibility statement
How accessible critlab aims to be, what is known to fall short, and how to tell us.
Version 2026-10-02 · Effective
Draft · pending legal review
critlab aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, in its own interface. This statement is voluntary. It describes what we do and where we know we fall short, and it makes no claim about the European Accessibility Act.
What we do
- Contrast and size. Text meets AA contrast, body text is at least 16 pixels, and nothing is smaller than 13.
- Keyboard. Controls can be reached and used from the keyboard, menus and dialogs follow standard keyboard patterns, and focus is always visible.
- Motion. We honour the setting that asks for reduced motion.
- Structure. Pages use headings, landmarks and labelled controls, and state is never shown by colour alone.
- Testing. Every component in our design system is checked with an automated accessibility tool on each change. Automated tests do not catch everything, so we also review by hand.
Where we fall short
- Customers' prototypes. The prototypes people upload are their own content, and we do not control how accessible they are.
- Placing comments. Pinning a new comment to an element is designed around a pointer, and we have not yet verified a full keyboard alternative.
- Voice notes. Recording a voice note needs a microphone.
- Not yet audited. We have not had an independent accessibility audit.
Tell us
If something does not work for you, write to support@critlab.app. Say what you were doing, the page and your assistive technology if you use one, and we will respond and fix what we can.
This statement describes the state of critlab at the version date above.