Last reviewed

The standard we build to

We aim to meet WCAG 2.2 Level AA. We treat that as a floor rather than a finish line — many of the people who need health information most are those with a disability, a temporary impairment, or simply a bad connection and an old phone.

What we have built in

  • Keyboard access.Every interactive element can be reached and operated with a keyboard, focus is always visible, and a “skip to content” link is the first thing you reach.
  • Semantic structure. Real headings in order, landmark regions, lists that are lists, and buttons that are buttons — so screen readers can navigate by structure.
  • Contrast. Body text and interface colours are chosen to meet AA contrast ratios.
  • Reduced motion. If your system asks for less motion, animations and count-ups are switched off rather than merely shortened.
  • Resizable text. Layouts use relative units and stay usable at 200% zoom without horizontal scrolling.
  • Plain language. Clinical terms are explained on first use. This is an accessibility feature, not just a style choice.
  • Descriptive links.Link text says where it goes, instead of “click here”.

Known limitations

We would rather list these than claim perfection:

  • Some data tables sourced from drug labelling are dense and scroll horizontally on small screens.
  • Third-party advertising is outside our control and may not meet the same standard as our own interface.
  • We are still improving descriptive alternatives for complex diagrams.

Tell us about a barrier

If any part of PocketsInfo is difficult or impossible for you to use, please write to hello@pocketsinfo.com. Tell us the page and what happened; the assistive technology and browser you use is helpful but not required.

We aim to acknowledge accessibility reports within 3 working days and to fix genuine barriers as a priority. If something cannot be fixed quickly, we will offer the information in another format in the meantime.