Legal · Last updated 04 June 2026
Accessibility statement
A press release a journalist cannot read is not a press release. This statement sets out how the wire is built for access, what we have tested it against, and — openly — what is still wrong.
The short version. This site aims at WCAG 2.2 Level AA and currently meets it, with the known exceptions listed below. Everything works without JavaScript, without a mouse, and without CSS. If something does not work for you, tell us and we will fix it — and we will tell you when we have.
1. Our commitment
A press release that a journalist cannot read is not a press release. Accessibility here is not a compliance exercise bolted onto a finished site; it is the reason the site is built the way it is — semantic HTML first, then CSS, then a small amount of JavaScript that only ever adds. We target WCAG 2.2 Level AA across every page, including the release template, the archive tables and the forms.
2. How the site is built for access
- It works without JavaScript. Every release, asset and link is present in the HTML. The category filter is progressive enhancement: with scripting off, the chips are ordinary links and the full feed stays visible.
- Keyboard complete. Every control is reachable and operable by keyboard, focus is always visible, and focus is never trapped.
- Contrast. All text meets 4.5:1; large text and interface components meet 3:1.
- Not colour alone. The embargo state is carried by the word “Embargoed”, a distinct chip and a stated lift time, not by amber alone.
- Motion. The only animation is a small status dot, which stops entirely under reduced-motion preferences, along with every transition.
- Reflow. The layout is fluid rather than breakpoint-driven; it reflows from 280 px upward with no horizontal scrolling and survives 400% zoom.
- Forms. Every field has a visible, persistent label, a programmatic association, and hint text linked correctly. Errors are described in words, never by colour alone.
- Print. Releases have a dedicated print stylesheet, because journalists print them.
3. What we have tested
Testing covers NVDA with Firefox, JAWS with Chrome, VoiceOver on macOS and iOS, TalkBack on Android, keyboard-only operation, Windows High Contrast and voice control. It is carried out by the web team together with two accredited journalists who use screen readers daily. Automated checks run on every page at build; they catch perhaps a third of what matters, which is why we also test by hand.
4. Known problems
We would rather list these than pretend they do not exist. Wide archive tables scroll horizontally on very narrow screens; the table sits in its own labelled scrolling region so the page itself never scrolls sideways. Downloadable documents are not yet tagged for screen readers, though every figure in them is also published as HTML on the media kit page.
5. Tell us
If any part of this wire is difficult or impossible for you to use, we want to hear about it. We acknowledge within two working days and give a substantive answer, with a fix or a date, within ten. If you need a release in another format — large print, plain text, braille or audio — ask and we will supply it free of charge.
6. If we do not put it right
Complaints we have not resolved may be taken to the national equality and access regulator. Doing so does not affect your accreditation, your access to the wire, or anything else about your relationship with the group.
7. Status of this statement
This statement was prepared on 4 June 2026 following a self-assessment against WCAG 2.2 Level AA, supported by external review of the release template and the accreditation form. It is reviewed every six months and on any material change to the site.