Accessibility

WhenMath is built to be usable by keyboard, screen reader, and touch, on a small phone screen or a large monitor, from the first page shipped rather than as a retrofit. This page states the concrete standard the site is held to and how to report a gap.

Standard

The site targets the intent of WCAG 2.2 Level AA: semantic HTML controls with explicit labels, a logical reading and tab order, a visible focus indicator on every interactive element, sufficient color contrast, meaning that is never conveyed by color alone, and form validation errors that are announced clearly rather than only shown visually.

Keyboard and screen-reader support

Every interactive control, including a calculator's inputs, presets, and action buttons (copy, share, reset), is reachable and operable from a keyboard alone, with a "Skip to content" link at the top of every page. Where a result updates dynamically as you type or change an input, the update is exposed to assistive technology so it is announced rather than silently changing on screen.

Motion and animation

WhenMath respects your operating system's reduced-motion setting. Where the site uses any animation or transition, it is shortened to effectively nothing for a visitor who has requested reduced motion at the system level.

Timers and active tools

A running timer or stopwatch remains operable by keyboard and announces its state changes (started, paused, finished) to assistive technology, not only through a visual or audible cue. No tool on this site plays sound or requests a notification permission automatically without your action.

Mobile and responsive layout

Layouts are designed mobile-first: touch targets are sized for a thumb, tables and timelines are built to scroll within their own container rather than forcing the whole page to scroll sideways, and every export or share action works on a small screen, not only a desktop browser.

Known limitations and reporting a problem

As a young, growing site, a specific page or interaction may not yet meet this standard even when the intent above is genuinely the target. If you hit a barrier using WhenMath with a keyboard, screen reader, or any other assistive technology, please describe the page and the problem through the Contact page; accessibility reports are treated as a real defect, not general feedback.