Skip to main content
numora.
numora.

Accessibility Statement

Numora is built to WCAG 2.1 AA. Report any access issue to a11y@numora.net.

Our commitment

Numora is built to WCAG 2.1 AA from the start. Every calculator is designed to work for people who navigate via keyboard, screen reader, magnifier, or in high-contrast / dark mode.

What this looks like in practice

  • Keyboard-first. Every input, button, and link is reachable via Tab. Focus indicators are visible and meet contrast requirements.
  • Screen-reader-friendly. Form fields have labels. Results update via aria-live so they're announced as you type. Calculator state changes don't break navigation flow.
  • Adequate contrast. Text contrast meets 4.5:1 (body) and 3:1 (large text + UI components). Dark mode uses tokens that satisfy the same thresholds.
  • Reduced-motion respected. Animations are dialled back to fade-only when prefers-reduced-motion is set.
  • Resizable text. Layout holds up at 200% zoom without horizontal scroll on standard viewports.
  • Touch targets. Mobile tap targets are at least 44 × 44 px.

Known gaps

We're a small team and ship rapidly. Likely accessibility gaps as of April 2026:

  • Some long-form blog content uses an emoji or two that screen readers may announce verbosely.
  • A few of the more complex calculator widgets (group inputs, schedules) have not yet been formally tested against JAWS or NVDA.

If you encounter a barrier, please tell us — we treat accessibility bugs as P1 fixes.

How to report an issue

Email a11y@numora.net with:

  1. The URL where the issue occurs.
  2. A short description of what's broken (e.g. "screen reader skips result on BMI page after submit").
  3. Your assistive technology + browser if relevant.

We aim to respond within five business days.