Accessibility Statement

We want RunTheTests to be usable by as many people as possible, and we take the subject seriously enough to ship a WCAG contrast checker of our own. This statement describes where we are and where we fall short.

Our aim

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. That is a target we work toward across the site rather than a certification we claim.

What we do

• Semantic HTML with a single, meaningful heading structure on every page, so screen readers and assistive tech can navigate.
• Keyboard access to interactive controls, with visible focus outlines.
• Light, dark and system themes, and a colour palette we check for contrast.
• Text that reflows and scales, with layouts that adapt from phone to desktop.
• Results announced to assistive technology where a tool updates them dynamically.

Known limitations

Some tools are inherently visual or interactive — a webcam preview, a printed test pattern, a colour picker — and cannot be fully represented to a screen reader. Where a tool depends on seeing or hearing something, that is a limit of the task, not something we can caption away. We describe what each such tool does in text so its purpose is clear even where the interaction is not.

How results are made readable

A diagnostic tool that reports its answer only as a colour has excluded a significant share of its readers before it starts, and the trio of red, amber and green is close to the worst possible choice for anyone with a red-green colour vision deficiency. Every result on this site therefore carries its status three ways at once: as a word, as a distinct glyph, and as a colour. The glyph is the encoding that does the work, and the colour reinforces it — which means a screenshot printed in black and white, or read by someone who sees red and green as the same shade, still says what it said on screen.

The same reasoning shapes the charts and diagrams. Where several series appear on one plot they are direct-labelled and distinguished by line style rather than by colour alone, and dense visualisations — matrix grids, waterfall segments, bit fields — carry a text label or a glyph inside each cell. Every measurement shown in a visual is also present as a number in the telemetry table beneath it, so nothing is available only to someone who can see the picture.

Motion, timing and interruption

Several tools animate by necessity — a latency graph as samples arrive, a countdown, a progress indicator during a benchmark. Where movement is decorative, such as hover states and theme changes, it is suppressed for anyone whose system requests reduced motion; the motion that carries the result is not, because removing it would remove the answer.

Nothing plays sound, opens a camera or a microphone, or reaches a device without an explicit action from you — the browser enforces that for hardware, and we do not work around it for audio. A small number of tools do read something on load, and they are the ones whose entire subject is what a page can see about your connection before you interact with it; that is the finding rather than a side effect, and each says so on the page.

Compatibility

The site is built to work with current versions of the major browsers and with common screen readers. Because the tools run in your browser, your own browser and assistive-technology versions affect the experience.

Reporting a problem

If something on the site is hard to use with assistive technology, or you hit a barrier, please tell us at contact@brightscalelabs.com. Describe the page and what happened, and we will do our best to fix it — accessibility problems are bugs, and we treat them as such.