Legal

Accessibility

Last updated: 16 April 2026

1. Our commitment

Plenishd is built for every UK family, which means it has to work for everyone — including people who use screen readers, keyboard navigation, voice control, switch devices, screen magnifiers, or who experience motion sickness, low vision, dyslexia, hearing loss, cognitive differences, or motor impairments.

Our target standard is WCAG 2.1 Level AA for both this website and the Plenishd mobile app.

2. What we have done

2.1 Visual

  • Minimum 4.5:1 contrast ratio for body text against the cream background; 3:1 for large display headings — verified across the amber palette.
  • All interactive elements have visible focus states using a 2-pixel honey-coloured outline (:focus-visible), so keyboard users always know where they are.
  • Text uses relative units (rem, em, clamp()) so it scales correctly when the user changes their browser's default font size.
  • We never rely on colour alone to convey meaning — every coloured indicator has a label, icon, or text cue alongside it.

2.2 Motion

  • All animation respects the operating-system prefers-reduced-motion: reduce preference. When this is set, scroll-driven parallax, particle effects, and decorative motion are disabled in favour of plain fades.
  • No animation that flashes more than three times per second (per WCAG 2.3.1, the photosensitive seizure threshold).

2.3 Keyboard and assistive technology

  • Every interactive element is reachable with the Tab key in a logical order.
  • Skip links and semantic landmarks (<nav>, <main>, <aside>) help screen reader users jump to the part of the page they want.
  • Decorative images use alt="" so screen readers do not announce them; meaningful images have a description.
  • Animated word-stagger effects use a container aria-label so the full sentence is announced as one continuous string instead of word-by-word.
  • Form inputs have programmatic labels.

2.4 Mobile app

  • Voice-first input means users with motor impairments or temporary disabilities (cooking with messy hands) can drive the entire kitchen inventory hands-free.
  • Photo scanning supports VoiceOver and TalkBack with descriptive announcements.
  • Dynamic Type and Display Zoom are honoured throughout the app.

3. Known limitations

We are open about where we know we still need to improve:

  • Animation in feature blocks: the alternating-side reveals on the For Families page are slightly disorienting at very high zoom levels (>200%). We are reworking these.
  • TOC sidebar in legal docs: the Contents sidebar is currently desktop-only. On mobile and tablet, the document still scrolls cleanly but you cannot jump to a specific section. We are adding a collapsible mobile TOC in a future release.
  • Help search: there is currently no full-text search on the Help page. For now, the FAQ accordion lists the most-asked questions; full search is planned.

If you spot something else, please tell us — see contact below.

4. Reporting an accessibility problem

We treat accessibility reports as priority bugs.

If you cannot use part of this website or the Plenishd app because of an accessibility barrier, please email support@plenishd.co.uk with:

  • A description of what you were trying to do
  • Where you got stuck (page URL or app screen)
  • The assistive technology you were using (screen reader and version, switch device, voice control, etc.)
  • Whether you have a workaround or whether the barrier is total

We will reply within 2 working days with an acknowledgement and our plan for fixing it.

5. Independent regulator

This statement is prepared in the spirit of the UK Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. Although Plenishd is a private-sector service and not in scope of those regulations, we use them as a benchmark.

If you contact us about an accessibility barrier and you are not happy with our response, you can contact the Equality Advisory and Support Service at equalityadvisoryservice.com for advice.

6. Updating this statement

We will update this statement when we make significant changes to the website or app, or annually at minimum.