What you should be able to do

We want as many people as possible to use this site. You should be able to:

  • change colours, contrast, and text size using the theme and text-size controls in the header, or your own browser and device settings;
  • zoom in to 400 percent without text spilling off the screen;
  • use every page with a keyboard alone, starting from the “Skip to content” link;
  • use the site with a screen reader, speech recognition, or switch access;
  • choose your language and spelling with the language control in the header.

How accessible this site is

The standard we aim for is WCAG 2.2 level AA. We say we aim for it, not that we meet it: no independent audit has been carried out, so we do not claim conformance at any level.

What is checked: every change is type-checked, including the accessibility checks built into the Svelte compiler, and the site is built with the accessible components of the Lily Design System. Pages use landmarks, one main heading, labelled controls, and table headers.

What we know falls short

  • Screen readers: the site has not yet been tested in full with VoiceOver, NVDA, JAWS, or TalkBack.
  • Themes: the default light theme is designed for good contrast. Other themes are a reader’s choice, and some may not reach the contrast you need.
  • Translations: the Welsh version is a draft translation that a native speaker has not yet reviewed, so some wording may be wrong.
  • Other websites: the projects link to repositories and websites we do not control, which may be less accessible.

Content in another format

Every page is plain HTML, and a plain-text summary of the site is available at llms.txt. If you need something in another form, such as large print, easy read, or audio, open an issue and say what you need. We will reply, and where we can make it, we will.

Report a problem

If something on this site does not work for you, tell us on the issue tracker. “I could not operate this with the keyboard” is a complete report. You do not need to name a WCAG criterion. Please say which page, which browser, and which assistive technology you were using, if you know.

If you are not happy with our reply

Public Projects is a personal, open-source project, not a public sector body, so no statutory accessibility regulation applies to it directly. If a public service uses one of these projects and you have a concern about that service, contact the service and its regulator.

Our plans

  • Automated accessibility checks on every page as part of each build.
  • Screen-reader testing of the main pages, with the results published.
  • Native-speaker review of the Welsh translation.

This statement was last reviewed on 21 November 2026. It will be reviewed again when the site changes in a way that affects accessibility, and at least once a year. See also the privacy policy.