Skip to main content
Accessibility - Ploverloom

Legal

Accessibility statement.

The people who use the software we build include people who use screen readers and keyboards, so we treat accessibility as a basic requirement. This page says how this website meets that standard and what to do if something doesn't.

The standard we build to

This website aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, the international standard for accessible websites. We build to that standard from the start, and we treat anything that falls short as a defect to fix.

Done so far

  • Screen readers can read each page in a sensible order, with clear headings and named regions for navigation.
  • Images that carry meaning have a text description, and decorative images are marked so screen readers skip them.
  • The whole site can be used with a keyboard alone, with a visible marker showing where you are.
  • A "skip to main content" link at the top of each page lets keyboard and screen reader users jump past the navigation.
  • Text and background colours are checked against the WCAG 2.1 AA contrast levels for normal and large text.
  • Form fields have labels, with a hint where extra context helps.
  • The layout adapts to screens from small phones to large monitors, and text can be enlarged in the browser without breaking the page.
  • Nothing plays or flashes on its own, and the one moving strip on the home page stops when your system asks for less motion.

Not tested yet

We test mainly in Chrome on Windows, with phone layouts checked through Chrome's phone preview and automated checks. We have not yet tested directly on Safari on a Mac or on an iPhone, and we're widening that coverage as the business grows. If something on this site misbehaves in a browser we haven't tested, please tell us and we'll fix it first.

Checks keep finding things, and we fix each one.

Reporting a problem

If anything on this site is hard to use with the tools you rely on, please tell us through the contact form and mention "accessibility" in the message. Messages flagged this way go to the top of our list. We aim to reply within one business day and to fix the problem, or explain our plan, within five business days.

Other formats

If you need anything on this site in a different form (larger text, plain text, audio or something else), ask through the contact form and we'll do our best.

The software we build for clients

The same standard applies to the tools we build. Everything we deliver targets WCAG 2.1 AA, and an accessibility finding during a project is handled like any other defect.

Last updated: September 2, 2026. Accessibility is ongoing work, and we update this statement as the site improves.