Our commitment to accessibility on the interfaces Zevonix builds, and an honest account of where that commitment ends.
Two different things, often confused. This statement covers our interfaces: zevonix.cloud and My Cloud Manager. It does not cover the websites we host for customers. Those are built and controlled by you, and their accessibility is your responsibility.
1. Our commitment
We aim to make our own interfaces usable by as many people as possible, including people using screen readers, keyboard-only navigation, magnification, or who need reduced motion. We treat accessibility as part of building the thing, not a pass afterwards.
2. What we do
- Semantic HTML, so headings, lists, tables and landmarks mean what they say to assistive technology.
- Every interactive control reachable and operable by keyboard, with a visible focus indicator.
- Text contrast checked against WCAG 2.1 AA; our interface colours are chosen for measured contrast ratios rather than by eye.
- Form fields with real labels, and errors reported in text next to the field rather than by colour alone.
- Icon-only controls carry an accessible name, so a screen reader announces the action and not just “button”.
- Charts and status indicators pair colour with a label or shape, so they do not depend on colour vision.
- Decorative motion respects
prefers-reduced-motionand stops for anyone who has asked their system to reduce it. - Layouts work at phone width without horizontal scrolling, and reflow rather than break when text is enlarged.
3. Conformance status
We target WCAG 2.1 Level AA for zevonix.cloud and My Cloud Manager. We describe this as partially conformant: most of the interface meets the standard, and we have not completed a formal third-party audit of every screen. We would rather say that plainly than claim a certification we do not hold.
4. Known limitations
- Some data-dense tables in the management console are difficult to navigate on a small screen.
- A few historical screens predate our current standards and are being revised as they are touched.
- Third-party embedded components, such as a bot challenge or an authenticator QR code, follow their vendors' accessibility behaviour, which we do not control. Where one exists, we provide an alternative path, such as a text key you can enter by hand instead of scanning.
5. Your website
The accessibility of a website we host for you depends on its theme, its content, its images and the code your developers write. Hosting a site does not make us responsible for whether it conforms.
As stated in your Service Agreement, unless expressly contracted as a separate service, Zevonix does not warrant or guarantee compliance with the Americans with Disabilities Act, Section 508, the Web Content Accessibility Guidelines, or similar standards for the websites we host. You are responsible for obtaining appropriate guidance for your own site.
If accessibility remediation is something you want help with, it can be scoped as separate work. Ask us.
6. Feedback
If you hit a barrier on one of our interfaces, please tell us what you were trying to do, the page you were on, and the assistive technology you were using. Reports about specific barriers are far more useful than general ones, and we treat them as defects.
Email [email protected] or use the contact form. We will acknowledge your report and tell you what we intend to do about it.