FontGenerate is built to be operated by keyboard and assistive technology, and it is honest about the limits of decorative Unicode text.
Our commitments
FontGenerate aims to meet WCAG 2.2 level AA. In practice that means:
Every control is reachable and operable with a keyboard, and focus is always visible.
The text input has a persistent label, and each Copy button names the style it copies.
Successful copies and errors are announced to screen readers through a polite live region.
Meaning is never conveyed by color alone; selected and copied states also change text and icons.
The layout works at 320px wide and at 200% browser zoom without horizontal scrolling.
Motion is reduced when your system requests reduced motion.
Automated accessibility checks run on every page in our test suite, and the core journey is tested manually with a keyboard and a screen reader.
A note on decorative Unicode text
The text this site generates is made of Unicode characters that look like different type styles. Assistive technologies handle these characters inconsistently:
Some screen readers pronounce 𝐇𝐞𝐥𝐥𝐨 correctly as “Hello”. Others read each character’s technical name, or skip characters they do not recognize.
Braille displays may not have cells for these characters.
Text-to-speech, translation, and search tools may not recognize styled words.
For that reason we recommend using styled text only for short, decorative content and keeping anything essential — names people need to find, contact details, instructions — in plain text. Every generator page repeats this guidance.
Known limitations
Styled results are exposed to assistive technology as the raw Unicode characters; we do not currently provide a plain-text equivalent alongside each result.
Rendering of some symbol styles depends on the fonts installed on your device.
Report a problem
If you find something that does not work with your assistive technology, please tell us through the contact page. Include the page, the browser and assistive technology you use, and what happened. Accessibility reports are treated as defects, not feature requests.
FAQ
Accessibility questions
Can I use FontGenerate with only a keyboard?
Yes. Tab moves through the input, category chips, search, and every Copy button; Enter or Space activates them; Escape closes menus. Focus is always visible.
How does a screen reader know a copy succeeded?
A polite live region announces “Style name copied” after each successful copy, and the button label changes from Copy to Copied.
Which styles are safest for screen-reader users?
Frames, kaomoji, emoji borders, and separators keep your letters plain, so the words are read normally. Alphabet styles may be spelled out character by character.
Does the site support reduced motion?
Yes. When your system requests reduced motion, hover lifts, slides, and the copy flash are removed; only short opacity changes remain.
Does the layout work with large text or zoom?
Yes. The site is tested at 200% browser zoom and at 320px width, and no action is lost or hidden behind horizontal scrolling.
Why is the generated text not read as words?
Styled letters are separate Unicode characters. Some screen readers map them back to letters; others read their technical names. That is a limitation of the characters, not something the site can change.
Is there a plain-text version of each result?
Not yet. Your original text remains in the input, and the style name is announced with each result, so the plain version is always one step away.
Do the category chips work with switch access and voice control?
Yes. Chips are real buttons with visible labels, so voice commands such as “click Bold” work, and switch scanning reaches them in order.
Are color contrasts sufficient?
Text and controls meet WCAG AA contrast on every surface, including the lime selected state and the blue hero, and focus rings are high-contrast.
How do I report an accessibility issue?
Use the contact page and describe the page, your assistive technology, and what happened. Reports are treated as defects and fixed before feature work.
