Accessibility statement

Our target

We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as a practical reference for design and testing. Conformance is an ongoing process rather than a one-time badge, and this statement does not claim that every legacy page or third-party destination is perfectly conformant.

Features implemented across the site

• A keyboard-visible skip link moves directly to main content.
• Mobile navigation exposes expanded and collapsed state to assistive technology and closes with Escape.
• Visible focus indicators help keyboard users track position.
• Pages use a single primary heading and semantic section headings.
• Forms and interactive tools pair controls with labels, provide error text, and use live regions where results change.
• Layouts reflow for narrow screens and avoid requiring horizontal page scrolling.
• Color is not intended to be the only carrier of meaning.
• Decorative icons are hidden from assistive technology; informative images require alternative text.
• Print styles remove navigation and nonessential interface elements.
• Search and reference pages pre-render their core content so links remain available before scripts run.

Interactive tools and games

New interactive resources are designed for keyboard use and provide text explanations rather than relying only on color or animation. Scores and calculated results use status regions where appropriate. Tools explain assumptions and preserve access to related articles when JavaScript is unavailable.

Some experiences use JavaScript for filtering, calculation, or game state. The underlying educational explanation and navigation should remain available without it, but the interactive behavior itself may not.

Known limitations

The library contains older hand-built pages that are being progressively upgraded. Navigation wording and layout can vary between generations of templates. Some externally linked PDFs, government tools, videos, or third-party pages are outside our control and may have different accessibility characteristics.

Automatically generated search snippets can be lengthy. Very large text settings may create additional scrolling, though content should remain readable. We continue to test zoom, keyboard order, contrast, labels, reduced-motion preferences, and common mobile widths as components change.

Testing and prevention

Repository validation checks every public HTML file for a title, description, canonical URL, primary heading, parseable JSON-LD, valid internal targets, and sitemap inclusion. Automated checks cannot prove full accessibility, so manual keyboard and visual review remains necessary for new interaction patterns.

We avoid overlays that claim to “fix” accessibility after page load. Accessible structure belongs in the site itself.

Tell us about a barrier

If a page, form, calculator, game, or document is difficult to use, contact us through the contact page. Include the URL, the task you were trying to complete, your browser or assistive technology when comfortable sharing it, and the barrier you encountered.

Do not include medical or other sensitive personal information. Accessibility reports are handled as product-quality issues and do not affect access to the site.