Accessibility

Last updated: October 13, 2026

glp1.how is meant to be usable by everyone, including readers who use a screen reader, navigate by keyboard only, enlarge text, or prefer reduced motion. This page says what we aim for, how we check it, and where we know we fall short.

Standard

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the public site and the signed-in account pages.

How we test

• Our automated test suite includes a WCAG 2.2 AA check (axe-core) against the homepage, pillar pages, an article, the glossary, FAQ, evidence index, search, login, and the policy pages, in both light and dark themes. It runs on every pull request, and we do not merge a change that fails it.
• Signed-in pages (account settings, bookmarks, and the editor) are checked the same way on a narrow phone-sized viewport, including that the first Tab press lands on a visible control and that nothing scrolls sideways.
• Every public page has a “Skip to content” link as the first focusable element, visible focus rings, and a semantic heading outline.
• We review new interface components by keyboard before they ship.

Known limitations

• Embedded videos. YouTube and TikTok players are third-party embeds; their controls, captions and keyboard behaviour are theirs. Each embed is labelled with the video’s caption, but we cannot guarantee the video itself is captioned.
• Diagrams. Some articles include rendered diagrams (Mermaid). Each carries an accessible label, and the surrounding text explains it, but the diagram’s nodes are not navigable with a screen reader.
• Editor-written content. Articles are written in Markdown by editors and contributors. We check headings and image alt text in review, but an occasional missing alt text or unlabeled link can slip through. Please tell us.

Report a barrier

If something on glp1.how is hard or impossible for you to use, email hello@glp1.how with the page address and what went wrong. You can also use the “Report an error or suggest an improvement” control at the bottom of any article. We aim to reply within five working days and to fix confirmed WCAG AA failures as a priority.