Accessibility

Accessibility.

We design for clinicians and operators — people who often use software at the limits of attention, lighting, and time. Our own site has to live up to that. This page documents where we stand on accessibility and how to flag anything that fails you.

Last updated: 2026-05-13

Conformance target

wiserframe.com targets WCAG 2.1 Level AA conformance. We measure against the success criteria published by the W3C Web Accessibility Initiative and review the site whenever we ship significant design changes.

The standalone resources hosted under this domain — the Component Library, the Clinical Interface Glossary, and the Supervision Queue documentation — share the same target.

What's implemented

  • Skip-to-main-content link on every page, keyboard-discoverable.
  • Semantic landmarks (<main>, <nav>, <footer>) so screen readers can jump structure.
  • Visible :focus-visible outlines on every interactive element.
  • Decorative icons marked aria-hidden="true"; meaningful icons paired with text labels.
  • Alt text on every <img>; aria-labels on icon-only buttons.
  • Text contrast meets WCAG AA: ≥4.5:1 for body copy, ≥3:1 for large text and non-text graphics. Where we use white text on brand blue, we use #0066CC (5.18:1) rather than the lighter #0083FF.
  • Nav hamburger announces state via aria-expanded; mobile menu traps focus while open.
  • prefers-reduced-motion respected — the loader, the dot-grid shimmer, the rotating compliance ticker, and the closing-CTA call-ripple all freeze for users who request reduced motion.
  • Cookieless analytics; no consent banner needed and nothing tracks individuals across sites.
  • Native HTML controls (<details>/<summary> on FAQ) so screen readers and keyboards get standard behaviour for free.

What we're still working on

  • Programmatic colour-vision review of the screenshot mockups (CVD-safe palette).
  • Captions and transcripts for any video we add — the current hero loop is silent and decorative.
  • Lighthouse / axe-core in CI so regressions get caught at PR time, not after deploy.

Reporting an issue

If something on this site isn't usable for you — with a screen reader, with a keyboard only, at high zoom, with a switch device, in high-contrast mode — tell us. We'd rather hear about it than not.

Email hello@wiserframe.com with "Accessibility" in the subject line. Include the page, the assistive tech you're using, and what went wrong. We aim to respond within two working days and fix anything in scope within ten.

Technical specs

  • Standard: WCAG 2.1 Level AA · w3.org/TR/WCAG21
  • Site type: Static HTML/CSS/JS hosted on Vercel.
  • Last reviewed: 2026-05-13

Questions? Email hello@wiserframe.com — we reply within two working days.