Accessibility Statement

Last reviewed 2026-09-06.

What we’ve built for accessibility

• Semantic landmarks (header, nav, main, footer), one H1 per page, a skip-to-content link, and visible keyboard focus styles.
• The textarea is labeled, results are not announced on every keystroke, and copy confirmations use a polite live region rather than moving focus.
• An always-available "Copy original text" control alongside every styled result.
• Support for 200% zoom, 320px reflow, and prefers-reduced-motion.

What we haven’t finished testing yet

As of this revision, we’ve run automated accessibility scanning (axe) against the core templates, but have not yet completed a manual VoiceOver+Safari or NVDA+Firefox pass with a named tester — automated scanning alone does not prove conformance, and we won’t claim it does. This is tracked as an open prelaunch gate; see testing methodology for current status.

An honest limitation of the product itself

Decorative Unicode text (bold, script, circled, and similar styles) is not the same as semantic bold/heading markup. Screen readers may spell out unusual characters letter-by-letter, skip them, or read them inconsistently between apps — see our accessibility guide (in progress) for what we observed. We never label any of these decorative outputs "screen-reader safe." The "Copy original text" control exists specifically so you can choose plain text when that matters more than a decorative look.

Report a problem

See Contact to report an accessibility issue.