Accessibility Statement

Last reviewed 2026-07-24

People reach this site while unwell, anxious, or managing a condition that affects vision, concentration, or dexterity. Accessibility is not a compliance exercise here — it determines whether someone can get safety information when they need it.

The standard we target

We aim to meet WCAG 2.2 Level AA. We treat that as a floor rather than a finish line, and we test as we build rather than auditing at the end.

What is built in

• Semantic HTML. Real headings in order, landmarks, lists, and tables, so screen readers and keyboard navigation work with the page structure rather than against it.
• Keyboard access. Every interactive element is reachable and operable by keyboard, with a visible amber focus indicator that we never remove. A skip link to the main content is the first focusable element on every page.
• Colour is never the only signal. Every status carries a text label as well as a colour — “Evidence-sourced”, “When to seek medical care” — so meaning survives colour blindness and monochrome printing.
• Contrast. Text and interface colours are chosen to meet AA contrast in both light and dark themes, which are designed separately rather than by inversion.
• Reduced motion. All transitions are disabled for visitors who set prefers-reduced-motion.
• Responsive and zoomable. No page scrolls horizontally at 375px wide, text reflows on zoom, and interactive targets are at least 40×40px.
• Readable by default. Body text is set at a comfortable size with a 65–72 character measure, and the site loads no web fonts, so pages render immediately and respect your font settings.
• Works without JavaScript. Content is server-rendered, so pages are readable even if scripts fail or are blocked. See our Brand Guidelines for the design decisions behind this.

Known limitations

We would rather name gaps than imply we have none. As of the date above:

• The site has not yet been audited by an independent accessibility specialist, nor tested systematically with every major screen reader and assistive technology combination.
• Interactive tools we are building — a cost estimator and a provider finder — will need their own accessibility testing before release, and will not ship until they pass it.
• External sites we link to for source verification are outside our control and may not meet the same standard.

Tell us if something does not work

If any part of this site is difficult or impossible to use, we want to know — a specific report is far more useful to us than a general audit. Email hello@glp1.healthcare and describe the page, what you were trying to do, and the assistive technology or settings you use if relevant. We treat accessibility problems as bugs, not feature requests.

If you need information from this site in a different format in order to use it, ask us and we will do our best to provide it.