Accessibility statement

Last updated: 2026-05-01 · Conformance target: WCAG 2.1 Level AA

Our commitment. Health information should be available to everyone. SupplementScore aims to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across the entire site. We re-test against this standard before every major release and after any structural change.

What works well

Semantic HTML — every page uses proper landmark elements (main, nav, article, aside) so screen readers can navigate by section.
Keyboard navigable — all interactive elements (buttons, links, form fields, modals) are reachable with Tab and operable with Enter / Space.
Visible focus rings — all focusable elements show a visible focus indicator that meets WCAG 2.4.7.
Decorative SVGs hidden from screen readers — all 462 inline icons carry aria-hidden="true" so screen readers don't announce phantom "image" elements.
Modals announce correctly — every modal carries role="dialog" + aria-modal="true" so screen readers trap focus and announce the dialog.
Form inputs have associated labels — either via <label for> or aria-label.
Color is never the sole signifier — tier badges (T1 teal, T2 blue, T3 amber, T4 red) always carry text labels too.
Mobile touch targets meet Apple HIG — minimum 36×36px on the smallest viewport, 44×44pt on standard mobile.
Reduced motion respected — animations honour prefers-reduced-motion: reduce.
Light theme forced — no flash of dark content during page load.
Language declared — <html lang="en"> on every page.
Page titles are unique and descriptive — every page has its own <title>.

Known issues

We're transparent about where we still fall short. Currently tracked:

Heading hierarchy on a few pages — index.html and a handful of other pages have multiple <h1> tags inherited from earlier templates. We're working through these in the next content pass.
Some chip/badge text uses 9–10px fonts — meets contrast minimums but smaller than WCAG-AAA recommends. We're auditing where we can bump these without breaking layout.
Long-form articles inlined into index.html — for assistive-tech users on slow connections, the initial page weight is high. Per-article static pages under /s/ mitigate this for direct linking, but the in-page article reader still loads everything.

Browser & assistive technology compatibility

SupplementScore is tested against the latest two stable releases of:

Chrome (desktop + Android)
Safari (macOS + iOS)
Firefox (desktop)
Edge (desktop)

Common screen readers we test against:

VoiceOver (macOS, iOS)
NVDA (Windows)
TalkBack (Android)

Reporting an accessibility barrier

If you encounter any accessibility issue — anything that prevents you from using a feature on the site — please report it via:

The Accessibility issue template on GitHub
Or by email to the contact in the About page footer with subject "Accessibility"

We aim to acknowledge accessibility reports within 3 business days and to resolve confirmed issues within 30 days. If a fix needs more time, we'll explain why and provide an alternative way for you to access the information.

Standards used

Web Content Accessibility Guidelines (WCAG) 2.1 Level AA
WAI-ARIA 1.2 for ARIA roles, states, and properties
HTML Living Standard for semantic markup

Testing approach

Automated: axe-core via Playwright in CI on every push (see .github/workflows/lighthouse.yml)
Manual: keyboard-only navigation pass on the top 10 pages before each release
Manual: VoiceOver + Safari pass on the top 5 pages before each release
Real-device check at 375 / 390 / 414 px viewports for touch-target sizing

Contact

Accessibility questions, suggestions, or barrier reports: see the contact email in the About page.

About — editorial process, funding, COI policy
Privacy policy
Terms of use
Methodology — how scores are calculated