Policies
Accessibility Statement
How this site is built for accessibility, what has been tested, and how to report a problem.
Last reviewed
This website is built to be usable with a keyboard, with a screen reader, at increased text sizes, and with reduced motion enabled. We treat accessibility as part of the build rather than as a later correction.
What has been implemented
- Semantic HTML with a single main landmark and a correct heading order on every page.
- A skip link to the main content as the first focusable element.
- Visible focus indicators throughout, never suppressed.
- Dialogs, menus, and accordions built on accessible primitives with focus management and escape handling.
- A before-and-after comparison control that works with mouse, touch, and arrow keys, and that respects reduced-motion preferences.
- Form fields with associated labels, described-by help text, inline error messages, and an error summary that receives focus on failed submission.
- Descriptive alternative text for every image, and decorative images marked as such.
- Text and interface colours checked against WCAG 2.2 AA contrast ratios.
- Touch targets of at least 44 by 44 CSS pixels for primary interactive elements.
Testing performed
Automated accessibility linting runs as part of the build. Keyboard navigation, focus order, and reduced-motion behaviour have been checked manually on desktop and mobile viewports. Formal third-party audit and assistive-technology testing across multiple screen readers have not yet been carried out.
Known limitations
Where third-party services are embedded — payment processing, for example — their accessibility is determined by the provider rather than by us. We will state any known issue here as we become aware of it.
Reporting a problem
If any part of this site is difficult to use, please tell us through the contact page and describe what you were trying to do. We will respond and, where we can, fix it.