Accessibility statement

Our commitment

We endeavour to meet Level AA of the Web Content Accessibility Guidelines (WCAG) 2.1⁠ (opens in a new tab) across this website. We test it with both automated and manual workflows so we stay compliant as the site changes, and we fix issues as soon as we find them and are able to do so.

WCAG sets out how to make websites usable by people with disabilities, at three levels: A, AA and AAA. Level AA is the standard most organisations and public bodies work to.

What we’ve built in

Colour contrast meets Level AA for text, including muted text and inactive tabs.
Text alternatives: images that carry meaning have alt text, and photos of people describe the person.
Keyboard access: you can reach and use links, buttons, menus, tabs and form fields with a keyboard, with a visible focus outline. Scrollable areas, such as code samples and wide tables in blog posts, can be focused and scrolled with the arrow keys.
Skip link: “Skip to content” is the first thing you reach with the keyboard on every page.
Structure: pages use headings, landmarks, labelled form fields and table headers, so screen readers can describe them and you can move around them.
Reduced motion: if your device asks for reduced motion, animations and scrolling effects are switched off and the content shows straight away.
Plain text versions: every page also has a Markdown version at the same address with .md added (for example, /contact.md).

How we check

Automated testing. We test every page against WCAG 2.1 Level AA with pa11y⁠ (opens in a new tab), which runs two independent engines, axe and HTML_CodeSniffer. Google Lighthouse also audits every page, including how well it works for assistive technology. These checks run regularly and before significant changes go live. On 30 October 2026, all 172 pages passed the automated WCAG 2.1 AA checks.

Manual testing. Automated tools only find some kinds of barrier, so we also test by hand. We use new and changed features with a keyboard alone and with screen readers, and check that content makes sense when it’s read aloud.

Fixing issues. When either workflow finds an issue, we log it and fix it as soon as we’re able to.

Known limitations

Some content comes from other services and isn’t fully under our control:

Booking calendar: the calendar for booking a call is provided by Calendly. If you have difficulty using it, email or phone us and we’ll arrange a time with you.
Cookie banner and declaration: the cookie banner, and the list of cookies on our cookies page, are provided by Consentify.
Web experiments: the CodePen demos on our experiments page are provided by CodePen. They load as you scroll to them, if you allow marketing cookies.
Embedded videos and browser support tables: a few blog posts embed a YouTube video or a support table from Can I use. Both load as you scroll to them, and each has a link under it to the original. Videos load only if you allow marketing cookies; until then a notice takes their place, with a button to change your cookie settings.
PDF downloads may not yet be fully optimised for screen readers. Ask us for the content in another format.

If you find a barrier that isn’t listed here, please tell us.

Compatibility

This website is designed to work with current versions of major browsers, with screen readers such as NVDA, JAWS and VoiceOver, and with keyboard navigation (Tab, Shift+Tab, Enter, Space and the arrow keys).

Feedback and other formats

If you find an accessibility barrier on our website, or need information in a different format, please contact us:

Phone: 020 3743 0888
Email: hello@pivale.co
Post or visit: BASE Bordon Innovation Centre, 60 Barbados Road, Bordon, Hampshire, GU35 0FX, United Kingdom

We try to respond to feedback within 2 business days.

About this statement

We last reviewed this statement on 30 October 2026, and we update it when we make significant changes to the website or how we test it.