Accessibility

Accessibility statement

People looking for medication are often unwell, tired or in a hurry. The interface aims to be usable in that state, on a phone, with whatever assistive technology someone relies on.

What we have built in

• Every form control has a visible, permanent label; hints and errors are linked with aria-describedby.
• The whole service works with a keyboard, including the medication suggestions list and the request dialog.
• A skip link jumps straight to the main content, and focus moves to results after a search.
• Results, errors and confirmations are announced through live regions rather than colour alone.
• Availability is always conveyed as text as well as colour.
• Body text meets WCAG 2.2 AA contrast in both light and dark colour schemes, and respects your system choice.
• Text reflows to 320px without horizontal scrolling; touch targets are at least 44px.
• Animation is minimal and honours prefers-reduced-motion, including the custom pointer, which switches itself off entirely for reduced motion and for touch or coarse pointers.

Known gaps

• The map view is a third-party map component. It is keyboard operable, but the list view is the primary interface and carries every detail as text.
• This build has not yet been through an independent audit or testing with screen reader users.
• Content is currently in English only.

Standard we aim for

We are working to WCAG 2.2 level AA. If something here blocks you, tell us what you were trying to do and what got in the way, and we will treat it as a defect rather than a suggestion.