Opsium aims to meet WCAG 2.2 Level AA. This statement records what is tested automatically on every change, what we know still falls short, and how to tell us about a barrier.
The European Accessibility Act has applied since 28 June 2025. This statement follows the form it describes, and it is written to be useful rather than to be compliant-looking: it says what is actually tested, and what is not.
The standard we hold ourselves to
WCAG 2.2 Level AA, in both the light and dark themes.
What is tested automatically, on every change
This website’s accessibility is not an occasional audit; it is a build gate. On every change, in continuous integration:
- axe-core runs against every page, in both themes, at two viewports, against the WCAG 2.0 A, 2.0 AA and 2.2 AA rule sets. A single violation fails the build.
- Every page is checked for exactly one
<h1>and for heading levels that do not skip: a jump fromh1toh3fails the build. - Every route is walked by keyboard, and the mobile menu is checked for a working
focus trap and for closing on
Escape. - Motion honours
prefers-reduced-motionglobally: scroll reveals and the product animations resolve to their finished state instead of animating.
What we know is not conformant
Publishing an accessibility statement with no known issues usually means nobody looked. These are the ones we know about:
- The footer brand watermark has a contrast ratio of roughly 2.3:1. It is
decorative, marked
aria-hidden, and exempt from the contrast requirement as a logotype under WCAG 1.4.3, but if you are reading the page at high magnification it may still be visible and unreadable, and we would rather say so. - The product illustrations on the homepage are drawings of the Opsium app built from page elements. They are hidden from screen readers, because a planning grid cannot be usefully read aloud cell by cell; the headings and text beside each one say what it shows, and the hero window is a labelled region. The screenshots in the documentation carry the name of the step they illustrate as their alternative text, and the step’s text describes what to do.
- Automated testing is not the same as human testing. No part of this site has yet been reviewed by someone using a screen reader daily. That review is outstanding, and it will find things the tooling does not.
The product, as distinct from this website
This statement covers opsium.io. The Opsium application at app.opsium.io is
held to the same standard, but it is not yet covered by the automated gates above
and has not been separately audited. If accessibility conformance is part of your
procurement, ask us and we will tell you where the application currently stands
rather than send you a certificate.
Telling us about a barrier
If something on this site or in the product blocks you, please tell us. We aim to reply within five working days, and to say either when it will be fixed or why it will not be.
Use the contact form, or the feedback link in the footer.
If our answer does not satisfy you, you have the right to escalate to the accessibility enforcement body in your country. In Austria this is the Sozialministeriumservice.