Accessibility statement
Where we stand, and how to tell us when something blocks you.
This page is being prepared. What follows is a draft, not the final text — do not rely on it for a legal or contractual decision.
Key points
- The target is WCAG 2.1 level AA for the public site and the admin console.
- Much of the app interface comes from upstream open source projects.
- Tell us what blocked you — include the page and what you were doing.
1Our target
We aim for WCAG 2.1 level AA on the marketing site and the admin console: sufficient contrast, full keyboard operation, and clear labelling for screen readers.
2Current state
Some areas have not been independently audited, and the apps in the suite differ in how accessible they are because they come from different open source projects. Audit results will be published here as they arrive.
3Feedback
If you hit a barrier, describe the page, what you were trying to do and which assistive technology you use. Reports of things that block use entirely are handled first.
4Assistive technology
The interface is built from semantic HTML, so it works with common screen readers and keyboard navigation. Custom components such as menus and dialogs carry ARIA labels and close with Escape.
Related pages