Accessibility statement

Our target

We aim for WCAG 2.2 Level AA in the newsletters Pressroom produces, in the pages readers use and in the Pressroom workspace. None of them meets that target in full yet, nor the WCAG 2.1 Level AA that the U.S. Department of Justice’s ADA Title II rule requires of state and local governments from April 2027 or April 2028, depending on the government’s size, and none has yet been tested with a screen reader. This page says where we are and what is still missing.

What this statement covers

Newsletter emails

The emails Pressroom sends, their plain-text version, and the same editions read on the web (the public archive and the “view in browser” page). We assessed these against WCAG 2.2 ourselves and wrote up the result as an Accessibility Conformance Report. Its summary is below.

Reader pages

The pages readers reach from a newsletter: sign-up and confirmation, the archive, subscription preferences and unsubscribe, polls, and this statement.

The Pressroom workspace

The web app editors and contributors use. An audit in September 2026 found that it did not conform: some dialogs and drag-and-drop boards could not be used with a keyboard, and many controls gave assistive technology no name, role or state. Most of those problems are fixed; the rest are listed below with the work still to do.

We assessed the reader pages and the workspace ourselves and wrote up the result as a second conformance report, dated 1 November 2026. Its summary is below. Nobody has yet tested either with a screen reader; that is still to do.

Email conformance summary

Each WCAG 2.2 success criterion at Level A and AA, as rated in our report for the email output (last reviewed 9 October 2026).

“Not applicable” mostly means the email has no audio, video, forms or sign-in. Read the full report: email accessibility conformance report.

Workspace and reader pages conformance summary

Each WCAG 2.2 success criterion at Level A and AA, as rated in our application report. “Not evaluated” means we have not yet tested that criterion.

The full report gives the evidence for each rating and a target date for each gap. Read it: application accessibility conformance report.

Known limitations

In newsletter emails:

• 1.1.1 Non-text Content: alt text is required and checked, but its quality depends on the editor.
• 1.3.1 Info and Relationships: heading rules stop generation on one template only; others report them.
• 1.4.1 Use of Color: some links are told apart by layout rather than underline, and nothing checks this.
• 2.4.4 Link Purpose (In Context): generic link text is caught from a fixed list of phrases, and a finding can be overridden.
• 2.2.2 Pause, Stop, Hide: animated images an editor uploads are not detected.
• 2.3.1 Three Flashes: uploaded animated images are not analysed for flashing.
• 1.4.3 Contrast (Minimum): checked in light and dark mode, but partial colour inversion in some apps is unverified.
• 1.4.5 Images of Text: uploaded graphics containing text are not detected.
• 1.4.10 Reflow: checked at 360px, not the 320px the criterion uses.
• 1.4.11 Non-text Contrast: button and icon contrast is not measured.
• 1.4.12 Text Spacing: not tested.
• 2.5.8 Target Size (Minimum): small links are reported as a warning that can be overridden.
• 3.1.2 Language of Parts: there is no way to mark a passage in another language.

On reader pages:

• 3.1.2 Language of Parts: there is no way to mark a passage in another language.

In the Pressroom workspace:

• 1.4.10 Reflow: the workspace has not been measured at the narrow width the criterion uses.
• 3.1.2 Language of Parts: there is no way to mark a passage in another language.

Not yet tested in the workspace or on reader pages:

• 1.4.4 Resize Text (workspace and reader pages)
• 1.4.12 Text Spacing (workspace and reader pages)
• 1.4.13 Content on Hover or Focus (workspace)
• 2.4.5 Multiple Ways (reader pages)
• 2.4.11 Focus Not Obscured (Minimum) (workspace)
• 3.2.3 Consistent Navigation (reader pages)
• 3.2.6 Consistent Help (workspace and reader pages)
• 3.3.7 Redundant Entry (workspace)

More generally:

• Newsletter emails declare English as their language. All current newsletters publish in English; one written in another language would not meet WCAG 3.1.1 until a language setting exists.
• Publishers write the words and choose the images. Pressroom checks alt text, link text, headings and contrast before an edition can be signed off, but an editor can override a finding and send anyway.
• Your email app decides how much of the design it shows. We test with simulated Outlook, Gmail and Apple Mail rendering, not with real apps or screen readers.
• Nobody has yet tested the workspace or the reader pages with a screen reader. Our checks use automated scans, scripted keyboard walks and a reading of the code.

Feedback and contact

If something in a newsletter or in Pressroom is hard to use, tell us what you were trying to do and where.

• About Pressroom: contact support (opens in a new tab)