Skip to main content
AgentAuditby BlackoutSign in

Accessibility statement

This statement applies to the AgentAudit pages at /agentaudit. It does not cover the wider Blackout Intelligence platform, which is a separate product with a separate interface.

What we are aiming for

WCAG 2.2 level AA. That is the standard the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 hold public sector websites to, and a public body procuring this product inherits the obligation.

What has been done

  • Every colour in the interface was contrast-checked against its background. Body text and interactive labels meet or exceed 4.5:1; the muted grey is a deliberately darker shade than is fashionable for exactly this reason.
  • A skip link is the first element in the tab order on every page.
  • Focus indicators are a 3px high-contrast outline with an offset, rather than the browser default hairline, which disappears against a coloured button.
  • Every form control has a visible, programmatically associated label. Hint text is linked with aria-describedby rather than placed in a placeholder.
  • Results that appear after an action are announced in a live region, so a screen reader user is not left waiting in silence for a verdict that has already rendered.
  • Content is structured with real landmarks and a single, ordered heading hierarchy per page.
  • Colour is never the only carrier of meaning: every status is also stated in words.
  • Motion respects prefers-reduced-motion.
  • Layouts reflow to 320px without horizontal scrolling. Wide tables scroll inside their own container rather than forcing the page sideways.

What has not been done

This is the honest part, and it is here because a compliance product that overstates its own compliance has refuted itself.

  • No independent audit has been carried out. The work above was done by the development team. That is not the same as an accessibility audit, and we do not claim it is.
  • No testing with assistive technology users. The pages have been built to the standard and checked against it, but nobody who relies on a screen reader daily has yet been through them. Their findings would carry more weight than everything in the list above.
  • The assurance report PDF is not tagged for accessibility. It is generated with jsPDF, which does not produce tagged PDF, so a screen reader will read it poorly. Everything the report contains is also available as structured HTML in the console and as JSON from the API, which is the accessible route to the same facts. Improving this is on the roadmap and is not fixed today.
  • Third-party content is not covered. Any page you reach by leaving this product is outside this statement.

If something does not work for you

Tell us and we will fix it. Describe the page, what you were trying to do, and what happened — including the browser and any assistive technology, if you can. Contact details are on the main Blackout Intelligence site.

If you are not satisfied with how we respond, the Equality Advisory and Support Service (EASS) handles complaints about accessibility in the United Kingdom.

Preparation of this statement

Prepared on 7 September 2026, based on a self-assessment of the AgentAudit pages against WCAG 2.2 AA. It will be revised when an independent audit is completed, and the claims above will be updated to match whatever that audit finds rather than the other way round.