Accessibility Statement

KitchenMath.io is committed to making cooking conversion accessible to every cook, including those who use assistive technologies. The site targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard referenced by Section 508 of the U.S. Rehabilitation Act and the Americans with Disabilities Act.

What we have built in

• A "Skip to main content" link that becomes visible on keyboard focus, letting keyboard and screen reader users bypass the header navigation on every page.
• Semantic landmark structure on every page: header, nav, main, and footer elements with proper labeling so screen readers can navigate by region.
• Visible keyboard focus indicators on every interactive element. Tab through the calculator, navigation, and links and you will see a clear amber focus ring.
• Color contrast ratios of at least 4.5:1 for body text and 3:1 for large text, exceeding the WCAG AA minimum.
• Form fields with explicit labels and accessible focus rings. Number inputs declare inputmode="decimal" so mobile keyboards present a numeric pad.
• The conversion calculator announces results to screen readers via an aria-live="polite" region whenever the ingredient, amount, or units change.
• Variant selector pills communicate their pressed state via aria-pressed attributes, and a fieldset with a legend groups them semantically.
• Tables use th elements with scope attributes for column and row headers, plus screen-reader-only captions describing the table's contents.
• Active navigation links are marked with aria-current="page" so screen readers announce which page you are on.
• Touch targets sized at 36 pixels or larger, well above the 24-pixel WCAG 2.5.8 minimum.
• Decorative graphics, including the logo and FAQ expand icons, are marked aria-hidden="true" so they do not produce audio clutter.
• Page titles and meta descriptions are unique per conversion page so browser tabs, bookmarks, and screen reader page lists are distinguishable.
• The site is mobile-first and works with browser zoom up to 200 percent without loss of content or functionality.

Known limitations

We test against the latest versions of major screen readers (VoiceOver on macOS and iOS, NVDA and JAWS on Windows, TalkBack on Android), but assistive technology rendering can differ from one version or browser combination to another. If you encounter content that does not work with your setup, please tell us. The site does not yet implement full keyboard shortcuts beyond the browser default tab order; that is on the improvement list.

Standards we target

WCAG 2.1 Level AA across all four principles: Perceivable, Operable, Understandable, and Robust. Where WCAG 2.2 introduces additional Level AA criteria, we adopt those too, including the 24-pixel minimum target size requirement.

Reporting accessibility issues

If any part of KitchenMath.io is hard to use with your assistive technology, send a description of the problem to [email protected] . Include the page URL, the assistive technology and browser you are using, and what happened versus what you expected. We aim to respond within five business days.

Ongoing work

Accessibility is not a one-time pass. Each new feature is reviewed against WCAG 2.1 AA before release, and this site runs an automated audit on every build that flags missing landmarks, broken focus indicators, color contrast regressions, and table semantic problems. The audit script lives in the public repository and the latest passing run is verifiable in the deployment log.