Back to login

Accessibility Statement

Published · Last reviewed

Our commitment

We're committed to providing a product that is accessible to the widest possible audience, including people with disabilities. The panel is designed and built to conform to the Web Content Accessibility Guidelines (WCAG) version 2.2, Level AA.

Conformance status

We claim partially conformant with WCAG 2.2 Level AA. Every WCAG 2.2 A and AA success criterion either passes or has a documented partial pass with the limitation listed below.

Known limitations

  1. VNC graphical console. The graphical console is inherently visual. VM power actions and a status read-out are reachable from a context bar above the canvas and never require focusing it; for SSH-style text access we recommend using the SFTP / shell sidecar exposed per VM rather than the console.
  2. Customer-uploaded files. The file-browser UI is fully accessible. File contents are user-generated content and WCAG treats those as the customer's responsibility.
  3. Third-party chart library internals. Charts use recharts with accessibilityLayer enabled; each chart is wrapped in a <figure> with a dynamic text summary, and the underlying data can be downloaded as CSV or JSON via the Export button.

Compatibility

Feedback and contact

We take accessibility feedback seriously.

Enforcement

If you are not satisfied with our response, you may contact the competent German market-surveillance authority for the accessibility of products and services, the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF).

Preparation methodology

Automated testing via axe-core (Playwright) on every route and pa11y-ci on public routes. Manual testing via NVDA + Firefox and VoiceOver + Safari, recorded per-route in the public repository under docs/a11y/conformance/. This statement is re-evaluated every 12 months and after any major UI change.