Accessibility Statement

Our commitment

We aim for this site to meet WCAG 2.1 Level AA. That covers the site itself — navigation, headings, forms, and interface controls — which are built with semantic HTML, visible focus states, keyboard support, and sufficient color contrast, and are never rendered using decorative Unicode characters.

An honest note about styled Unicode text

The text our generators produce is a different matter. Styled Unicode characters — bold, cursive, gothic, circled letters and similar — are real Unicode code points, but they are drawn from blocks (like Mathematical Alphanumeric Symbols) that most screen readers were never designed to pronounce as letters. A screen reader may spell the word out character by character, skip it, or announce it as “mathematical.” This is a limitation of how assistive technology and font rendering handle those code points generally — not something a website can fix on its own.

Because of that, we built two things directly into the product rather than just warning about the problem: an Accessibility Friendly mode that favors styles with better assistive-technology behavior, and a Copy Plain Text option next to every styled result, so you can always choose the accessible version of what you typed.

What to expect from the site itself

• A “skip to content” link for keyboard and screen-reader users.
• Visible focus outlines on every interactive element.
• One clear, semantic heading (H1) per page, in a logical order.
• Support for reduced-motion preferences (no essential motion depends on animation).
• Sufficient contrast between text and background in both light and dark mode.

Reporting a problem

If you hit an accessibility barrier anywhere on this site, please tell us via the contact page. We treat these reports as bugs, not feature requests.