Skip to content
Calixo

Accessibility Statement

Last updated: July 10, 2026

We want every calculator on this Site to be usable by everyone, including people using a keyboard, a screen reader, or who need reduced motion or higher contrast. This page is a plain account of where things stand today — not a certification.

Standard we aim for

We build against the Web Content Accessibility Guidelines (WCAG) 2.1, targeting Level AA. We haven't commissioned an independent, formal audit against the full standard, so we describe this as an ongoing effort rather than a certified compliance claim.

What's implemented today

  • • A "Skip to content" link at the very top of every page for keyboard users.
  • • Every calculator input is a real, labeled form control — not a div styled to look like one — so screen readers announce it correctly.
  • • The ⌘K search palette is fully keyboard-operable: open, navigate results, and select without touching a mouse.
  • • Color contrast for body text and interactive elements is checked with real contrast-ratio measurement tools, not eyeballed — we've previously found and fixed tokens that measured under the 4.5:1 minimum.
  • • Every page respects your operating system's "reduce motion" setting — animations and transitions collapse to near-instant instead of being forced on everyone.
  • • Decorative icons and mascots are marked aria-hidden, so screen readers skip them instead of announcing meaningless icon names.
  • • Dark and light themes both meet the same contrast bar — neither is treated as the "secondary" option.

Known limitations

Some calculators use sliders as an additional input method alongside a standard number field — the number field is always present and fully accessible even where a slider is also offered. Complex data visualizations (charts) include the same information in the numeric results next to them, but the charts themselves are not yet independently described for screen readers beyond their surrounding text. We're aware of this and treat it as an open item, not a solved one.

Reporting an issue

If you hit a barrier using this Site with a keyboard, screen reader, or any assistive technology, please tell us — the page you were on and what happened is all we need to start investigating. Reach out via our Contact page. We treat accessibility reports as real bugs, not feature requests.