Accessibility
Version 2026-11-20, last updated 2026-11-20
This statement says how accessible zdr.sh is, what we are doing about the parts that are not, and how to tell us when something gets in your way. It covers the website and the dashboard.
1. What we work to#
The harmonised standard EN 301 549, whose web requirements are the Web Content Accessibility Guidelines version 2.1 at level AA.
2. Where we stand#
Partially conformant. The service has been built and checked against those guidelines in part, and no independent audit against the whole standard has been carried out. We would rather say this plainly than claim a level we have not verified.
What is already in place: every interactive control has an accessible name, the interface is operable from the keyboard, the colour contrast of the text meets the level AA ratios, the layout reflows to a narrow screen and to 200 per cent zoom, and animations respect the reduced motion setting of your system.
3. What is not fully conformant#
- Table semantics in the price board on the landing page: its rows, cells and headers are marked with accessibility roles rather than native table elements. Screen readers announce it correctly, and the pattern is deliberate, but it is not the markup the guidelines prefer. The account tables and the price list on the pricing page use native table elements.
- Some form controls use accessibility roles for radio buttons and checkboxes instead of a native input. The announcements are correct; the markup is flagged for review.
- Some fields take focus when a screen opens, which is what a dialog asks for but can move you without warning.
- No independent audit has been carried out. Until one is, this section can only list what we know about ourselves.
4. Telling us about a problem#
Write to support@rackduck.com and describe what you were doing and what got in your way. We answer within five working days, and we will tell you what we intend to do about it, or why we cannot.
5. If you are not satisfied#
If our answer does not resolve the problem, you can complain to the authority that enforces accessibility in the country where you live, through the procedure that authority publishes.
6. Third-party notices#
The website and dashboard include third-party software and fonts. Their licences and copyright notices are listed in the third-party notices; the file is served with the site, so it can be read without JavaScript.