Press Release For Business
Accessibility

Accessibility statement

We build this site to be usable by everyone who needs to read or publish on it. Where we fall short, we want to hear about it.

Permanent canonical URL Dated & attributed Structured for retrieval From $19.99

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We are not claiming certification — we are stating the standard we build against and inviting correction where we miss it.

What we have implemented

Structure

  • A keyboard-reachable skip link at the top of every page
  • Headings used for structure in a logical order, not for visual size
  • Header, navigation, main and footer marked as landmarks
  • Current page indicated programmatically, not by color alone

Keyboard and focus

  • Every interactive element is reachable and operable by keyboard
  • Focus indicators are visible; we have not removed outlines
  • Search, filters, share controls and the mobile menu all work without a mouse

Reading

  • Release body text set at 17.5px with generous line height, scaling with browser text-size settings rather than locked
  • Color combinations chosen to exceed the 4.5:1 contrast ratio for body text
  • Layouts reflow to a single column without horizontal scrolling down to 320px
  • Releases carry a print stylesheet that strips navigation and advertising

Motion

  • Animated backgrounds and advertising units are suppressed when your system indicates a preference for reduced motion
  • Nothing on this site flashes more than three times per second

Forms

  • Every field has a visible, programmatically associated label
  • Required fields are marked and errors are communicated as text
  • Forms do not time out
Known limitations When payment processing is active, checkout is handled by a third-party processor whose internal accessibility is outside our control. Decorative illustrations carry supporting rather than essential information; where an illustration conveys something essential, it is also stated in the surrounding text.

Tell us where we fail

Accessibility problems are bugs and we treat them as bugs. Email with the page address and what went wrong — including, if you are willing, what you were using to read it. We answer accessibility reports and prioritise them above feature work.

If you need a release in a different format, or need help submitting one, ask and we will arrange it.

Last reviewed September 2026.