Accessibility

These tools are diagnostic pages that front-desk staff and IT run under time pressure, often from the keyboard and sometimes with a screen reader. Accessibility is a working requirement here, not a badge. The target we build to is WCAG 2.1 Level AA.

Conformance target

The standard we build to is WCAG 2.1 Level AA. Where a tool cannot fully meet a criterion because of what it does - a few of them test hardware and visual behavior directly - that gap is stated below rather than papered over.

What is implemented

Semantic HTML: one h1 per page and headings in logical order.
A main landmark and a skip-to-content link on every page.
Visible keyboard focus indicators, and full keyboard operability - every control can be reached and used without a mouse.
Support for prefers-reduced-motion: animations and transitions are cut when the operating system asks for reduced motion.
Color contrast meeting AA in both the light and dark themes.
ARIA labels on icon-only controls, and status regions (aria-live) that announce results as a test runs.
Labelled form controls, so assistive technology announces what each input is for.

Known limitations

Some of these tools test hardware and visual behavior directly, and there are limits to how much of that can be conveyed without sight:

The Keyboard Test and Display Test are inherently visual, hardware-interaction tools. A dead-pixel scan or a key-press keymap carries information through color and position that has no faithful text equivalent.
Some diagnostic output is dense. Detailed system, network, and certificate readouts pack a lot of information into a small space.

These are known gaps, not acceptable ones. We narrow them where the format allows.

Reporting a problem

If something on this site is hard or impossible to use with assistive technology, tell us and it gets fixed. Email [email protected], or open an issue at github.com/tech1k/desktest/issues. Include the page, your browser and assistive technology, and what happened - that is enough to act on.