Accessibility statement

We aim for WCAG 2.2 level AA across the site, the panel and the admin. Two known gaps remain, listed below with a date rather than a promise.

PARTIALLY CONFORMANTAssessed 20 August 2026 · self-assessment plus external audit
TARGET
WCAG 2.2 AA
CRITERIA MET
53 / 55
KNOWN GAPS
2
REPLY TIME
5 working days

1 · What works today

  • Every interactive element is reachable and operable by keyboard, in a visible order
  • Focus is always visible, with a 2px outline that meets contrast on both themes
  • Body text meets 4.5:1 and large text 3:1 against its background
  • The admin and panel ship a light and a dark theme, both tested
  • prefers-reduced-motion disables parallax, counters and every looping animation
  • Forms use real labels; errors are announced, not only coloured
  • Five interface languages, with the document language set correctly per page

2 · Known gaps

These are real failures against AA, not edge cases we are relaxed about. Both have a fix date and a workaround.

1.4.11 · AANon-text contrastFIX BY OCT 2026
Uptime bars on the status page fall below 3:1 against their background

The 90-day bars are decorative reinforcement of a value that is also written as a percentage, but the colour pairing still fails. Workaround: the percentage and the incident list carry the same information in text.

1.3.1 · AInfo and relationshipsFIX BY NOV 2026
The certificate chain in a verify result is not announced as a hierarchy

Screen readers read the chain as a flat list, losing the parent relationship between certificate and root. Workaround: the JSON response from the API carries the structure explicitly.

3 · How we test

  • Automatedaxe-core in CI on every pull request
  • KeyboardFull pass per release, no mouse
  • Screen readersNVDA + Firefox, VoiceOver + Safari
  • External auditAnnual, last August 2026
  • Reduced motionAll animation respects the OS setting

4 · A note on colour and verdicts

A verification verdict is the most consequential thing this product says, so colour never carries it alone. Every verdict shows an icon, a machine code such as SIGNED_QUALIFIED, and the state of both trust anchors as filled or outlined badges. A screenshot in greyscale remains readable, and so does an API response.

5 · Feedback and enforcement

Write to [email protected] with the page, what you were trying to do and the assistive technology you use. We reply within five working days. If our answer does not satisfy you, you may contact the national accessibility enforcement body in your member state; in the Netherlands that is the Rijksinspectie Digitale Infrastructuur.

Report a barrierTrust & Security