Accessibility statement

What we are aiming for

The target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. The site has not been independently audited against them and has not been tested across a full matrix of assistive technologies, so this is a statement of where the work stands, not a claim of conformance. Where the two differ, the list of limitations below is the honest part.

What is in place

• Structure. Every page is ordinary HTML with real landmarks — a header, a main region and named navigation — and headings that name each section, so a screen reader can move through a report by its parts rather than line by line.
• Keyboard. Everything that does something is a button or a link, so it can be reached and operated by keyboard. Saved scans in History take focus with a visible outline, and both dialogs — the sample report and the issue form — close on Esc, with focus returned to the button that opened the issue form.
• Forms. Fields carry real labels rather than placeholder text standing in for one, and the character counts and hints beside them are part of the page rather than a hover tooltip.
• Things that change on their own. A running scan announces its progress, and a finished report announces its arrival, through polite live regions; errors are announced as alerts. A scan takes minutes, and it should not need watching to know it moved.
• Colour and contrast. Light and dark are both supported, the dark theme follows your system setting unless you choose otherwise, and contrast in it has been corrected where a label was found sitting too faint against its card. Colour is never the only carrier of meaning: overlap and status are labelled in words as well as tinted.
• Motion. The pulsing marker on a running step and the progress bar’s animation stop when your system asks for reduced motion.
• Zoom and small screens. Layouts are built in relative units and reflow to a single column, so the site can be magnified or used on a narrow window without content being cut off sideways.
• Decoration is silent. Icons and ornamental marks are hidden from assistive technology instead of being read out as unnamed graphics.

Known limitations

These are the gaps we know about. They are being worked on rather than defended.

• No skip link. There is no “skip to content” control, so keyboard users pass through the header on every page.
• Focus indicators are uneven. Most controls rely on the browser’s default focus ring, and a few inputs replace it with a coloured border and glow, which can be hard to see in forced-colours or high-contrast modes.
• Dialogs do not trap focus. The sample report and issue form open as dialogs and close on Esc, but keyboard focus can still move to the page behind them.
• In-page links scroll smoothly regardless. Jumping to a section on this page animates the scroll even when your system asks for reduced motion.
• Dense report rows. The prior-work and contribution rows in a report carry several columns and become cramped at very high magnification.
• The interface is English only. Submissions in other languages are accepted and scanned, but the surrounding pages are not translated.
• No audit, no formal test matrix. Nothing here has been verified by an external reviewer or against a documented set of screen reader and browser pairs.

Adjusting the site to you

• The sun and moon control in the header switches between light and dark, and the choice is remembered on that device. Left alone, the site follows your system setting.
• Browser zoom and page text scaling both work; the layout reflows rather than scrolling sideways.
• A system “reduce motion” setting is honoured by the animations on the scan progress view.

Reporting a barrier

If something on this site kept you from doing what you came to do, please say so — a barrier nobody reports is one nobody can see from here. Use Report an issue, which sits beside the scan form, inside every finished report, and on a scan that failed.

Reports are read, and this page is updated as things are fixed. If a page is unusable for you and you need the same information another way, ask and we will find one.