wherewise

Accessibility

How these pages are built to be usable, what is known not to work well, and how to tell us when something does not.

Wherewise aims to meet WCAG 2.2 level AA. That is an aim rather than a certified claim: the site has not been independently audited.

What is built in

  • Every page works without JavaScript. The pages are plain HTML written ahead of time; scripts only add the map and the search shortcut. With scripts off, nothing on a page becomes unreachable.
  • Keyboard navigation throughout, with a skip link to the main content as the first focusable element and a visible focus outline on every control.
  • Real text, not images of text, which means it reflows, it scales when you zoom, and a screen reader can read all of it.
  • Light and dark follow your system setting, and both are checked for contrast.
  • Reduced motion is respected: if your system asks for less movement, transitions are removed.
  • Ratings are never a bare number. An Ofsted grade and a hygiene rating run in opposite directions, so both are written in words, and colour is never the only thing carrying the meaning.
  • Nothing loads from anyone else, so pages stay usable on a slow or filtered connection.

Known problems

  • The map is not accessible. It is drawn on a canvas, and a screen reader cannot read it. Everything the map shows is also in the lists on the page, with names and walking distances in text - the map adds no information of its own. It can be skipped entirely.
  • Long postcode listings on a district page can run to several hundred links, which is a lot to move through with a keyboard or a screen reader. The search box in the header goes straight to a postcode and avoids them.
  • Some source data is written in capitals or abbreviated by the body that published it. Where it is reproduced as published, a screen reader may read it letter by letter.

Tell us

If something here does not work for you, please write to hello@wherewise.co.uk and say what you were trying to do, what happened, and what you were using. Accessibility problems are treated as faults, not requests.

This statement is not made under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which do not apply to this site. It is published because the standard is worth holding ourselves to regardless.

Last reviewed 25 September 2026.