Skip to content

Accessibility

Accessibility statement

This site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. The badge in the footer is tested on every deploy, not only stated.

How it’s tested

  • axe-core checks the WCAG 2.1 A and AA rules on every case study, the main pages, the 404 page and representative role pages, in a desktop browser and a phone-sized one. The checks run on every pull request and before each deploy from master.
  • Lighthouse’s accessibility score must stay at 0.9 or above, on desktop and on a simulated phone, for the homepage, the CV and a long case study.
  • Hand-written tests cover what automated rules can’t: the skip link, keyboard focus after navigation and in the image viewer, the menus’ expanded state, and that the rotating role on the homepage keeps keyboard focus.

What to expect

  • Everything works from the keyboard, with a visible focus outline, and a “Skip to content” link at the top of every page.
  • Motion respects your system’s reduced-motion setting. The rotating role on the homepage also stops while the pointer or focus is on it.
  • Images have text alternatives, or are marked decorative where the text beside them says the same.
  • Pages read in full without JavaScript, and every page has a single main heading.
  • The CV is also available as plain text and as a Word document, which some screen readers handle better than a PDF.

Known limitations

  • The 3D identity pyramid on the homepage is decorative and hidden from assistive technology. Its content is available as the tabs beside it.
  • Code samples on the Code page are embedded from CodePen and GitHub Gist. Their content comes from those services, outside this site’s control, and the automated checks skip them.
  • The bird ringing licence demo is a GOV.UK Design System example with its own accessibility statement.
  • The motes demo can use a webcam. It works fully without one, on a sample scene.

Feedback

If something on this site doesn’t work for you, email raby@digitalbluebird.com with the page and what went wrong. See also Privacy.

Last reviewed 18 November 2026.