Skip to content
Accessibility

Accessibility Statement

Statement Last updated:

Our commitment

We want this site to be usable by everyone, including people who rely on screen readers, keyboard navigation, voice control, or other assistive technology. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

Accessibility is something we keep working on rather than a box we tick once. If something on the site gets in your way, please tell us — details are in the “How to report a problem” section below.

What we have done

The following accessibility features are in place across the site today:

  • A “skip to content” link in the header so keyboard and screen-reader users can bypass the navigation.
  • Semantic HTML with a single h1 per page and a consistent h2/h3 hierarchy, plus landmarks (header, nav, main, footer).
  • Visible focus indicators on every interactive element — links, buttons, form fields and menu items.
  • Descriptive alt text on all meaningful images; decorative images are marked so assistive tech can skip them.
  • A keyboard-navigable mobile menu with focus trapping and Escape to close.
  • Reduced motion is respected via prefers-reduced-motion— animations are shortened or removed when your device requests it.
  • Body text meets WCAG AA colour contrast ratios against its background.
  • ARIA labels on icon-only buttons (WhatsApp, social links, the mobile menu toggle, the back-to-top button and similar).
  • Form fields have visible, programmatically-associated labels; error messages are announced to assistive tech.
  • Page titles, language (lang="en-GB"), canonical URLs and breadcrumb structured data are set on every page.

Known issues

We want to be straight with you about what is not perfect yet:

  • Some animation timings may still feel fast for some users. We will keep tuning these and continue to honour prefers-reduced-motion.
  • The interactive Leaflet maps on our location pages have limited keyboard accessibility because they come from a third-party widget. Where a map is shown, the same address and coverage information is also provided as plain text alongside it, and phone and email contact details are always available.
  • A small number of older portfolio photos do not yet have detailed alt text. We are working through these as we update each page.

If you spot something else, please tell us — we treat accessibility reports as priority fixes.

How to report a problem

If you find something on the site that is hard to use, or content you cannot access, please contact us directly:

When you contact us, it helps if you can include the page URL, a short description of the problem, and the device, browser or assistive technology you are using. We aim to respond within 5 working days.

Compliance status

This website is partially compliant with WCAG 2.2 level AA. The non-compliance is set out in the “Known issues” section above.

PureRend is a one-person business. We do not claim full WCAG AAA conformance and we have not paid for an external accessibility audit. We do, however, test the site regularly ourselves and we fix issues as they are found or reported.

Enforcement

If you contact us about an accessibility problem on this site and you are not happy with how we respond, users in the UK can contact the Equality and Human Rights Commission (EHRC). The EHRC is responsible for enforcing the Equality Act 2010 in relation to service providers.

You can find their advice and contact routes on the Equality Advisory and Support Service (EASS) website.

How we test

We test the site ourselves using a mix of automated and manual checks:

  • VoiceOver on Safari (macOS and iOS) for screen reader sanity checks.
  • Keyboard-only navigation— every page is walked using only Tab, Shift+Tab, Enter, Space and the arrow keys.
  • Lighthouse accessibility audits in Chrome DevTools.
  • axe DevTools automated rule checks against each template.

Site last accessibility-tested Last tested: . We re-test before any significant change to the site.