Get the Friday briefing

Accessibility statement

How this site is built for keyboard, screen reader and phone use, what is not finished, and how to tell us about a problem.

By
Edited by Dale
Updated
[PLACEHOLDER: date]
Article text

Conformance status

Software Review Source is partially conformant with WCAG 2.2 level AA. Some parts do not yet meet the standard. A full audit is pending.

Feedback

If you find an access problem, tell us at [PLACEHOLDER: contact address]. Give the page address and say what you were trying to do.

What is built into the design

  • Every link, button and field is designed to work with a keyboard, with a visible focus ring. A skip link takes you past the navigation to the content.
  • Touch targets are at least 44 pixels tall in the designs.
  • On phones, the Sections menu closes with Escape and returns focus to its button.
  • The smallest text colour is at least 8 to 1 against its background in the designs.
  • Motion is limited. The one animation on each page runs once and does not loop. People who set reduced motion see every element in its final state.
  • Article text can be dark or light, so readers can choose the contrast they prefer.

What is not finished

  • A full audit by an outside tester is pending. This statement will change when the audit is done.
  • Not every page has been tested with a screen reader.
  • Testing before launch covers Chromium-based browsers and Safari. Other browsers are not yet tested.

How we check

We have run automated checks on the designs for headings, target sizes and horizontal scrolling, at widths from 320 to 1920 pixels. The live site gets the same checks before launch, plus keyboard tests.

Technology

The site uses HTML, CSS and one small JavaScript file, with no client-side framework. The script runs the Sections menu, the article text setting and the newsletter form.