Fancy fonts and screen readers: an honest accessibility guide
How VoiceOver, TalkBack and NVDA actually read Unicode fancy text, which styles are least disruptive, how to use them responsibly, and a two-minute phone test.
Every page on this site ends its explanation with a warning about screen readers, and it deserves more than a sentence. Fancy text is built from characters that were never meant to spell words: math symbols, phonetic letters, enclosed numbers, accents stacked on top of each other. Sighted readers see a stylish name. A blind reader using a screen reader hears something between a lecture on Unicode and total silence. This guide explains what actually happens, which styles do the least damage, and how to use fancy text without locking anyone out.
What a screen reader is doing
A screen reader does not look at the screen. It reads the underlying text and turns each character into speech using a pronunciation dictionary. For ordinary letters that is trivial. For a character like 𝗮 (MATHEMATICAL SANS-SERIF BOLD SMALL A), the software has to decide: is this the letter a, or is it a symbol that should be described?
Different screen readers make different choices, and the same reader behaves differently depending on version, language and verbosity settings. That is why you will find people online insisting fancy text is “read fine” and others insisting it is “completely skipped”. Both are reporting real experiences.
There is also a third path. Some software normalises text before speaking it, mapping compatibility characters back to their plain equivalents (a process Unicode calls NFKC). Where that happens, 𝗕𝗼𝗹𝗱 is simply spoken as “Bold”. Where it does not, you get one of the outcomes below.
How the major screen readers handle it
Observed behaviour at the time of writing, with the caveat that any update can change it:
VoiceOver (iPhone, iPad, Mac). For the math-style bold, italic and sans letters, recent versions of iOS VoiceOver often speak the plain letter or the whole word, because Apple’s text engine treats them as compatibility variants. Older versions and some third-party apps instead read each character’s full name, so “𝗡𝗼𝘃𝗮” becomes “mathematical sans-serif bold capital N, mathematical sans-serif bold small o…” and so on. Script and Fraktur letters are more likely to get the long treatment. Enclosed letters such as Ⓝ are usually read as “circled N”, which is slow but understandable.
TalkBack (Android). TalkBack depends on the Google text-to-speech engine, which has patchy coverage of the Mathematical Alphanumeric Symbols block. The common result is that styled words are skipped entirely: a bio reading “𝓝𝓸𝓿𝓪 · photographer” is heard as “photographer”. Some characters produce a brief “unknown” or a pause. Small Caps and enclosed letters are more often spoken by name.
NVDA (Windows). NVDA reads what its symbol dictionary knows. By default many math letters are spoken by their long Unicode names at higher punctuation levels, or skipped at lower ones. Users can adjust this, but most do not, so a fancy name in a tweet is heard as a string of “mathematical bold” announcements. Combining marks (the ones used in glitch text) are announced individually or produce a long silence while the synthesizer processes them.
JAWS (Windows) behaves broadly like NVDA, with somewhat better coverage of enclosed and fullwidth characters.
The pattern across all of them: the reader either hears your word spelled out with a long prefix per letter, hears nothing, or, if they are lucky, hears the word. You cannot control which.
Which styles are least bad
This ranking is based on how the characters are classified in Unicode and on reported screen reader behaviour. It is a rough guide, not a guarantee.
| Style | Typical result | Rating |
|---|---|---|
| Vaporwave Wide (fullwidth) | Almost always normalised to the plain letters and read as the word | Least bad |
| Bold Sans, Bold Serif, Italic Serif | Often normalised on iOS; spelled out with long names or skipped elsewhere | Acceptable in a heading |
| Small Caps | Usually spoken as “small capital A” per letter, or as the letter | Slow but comprehensible |
| Bubble, Squared | “Circled A”, “squared A” per letter | Slow but comprehensible |
| Double Struck | Long names or skipped; a few letters (ℕ, ℝ) have special names | Poor |
| Cursive Script, Bold Cursive | Long names or skipped; capitals from the Letterlike block vary | Poor |
| Gothic Fraktur, Bold Old English | Long names or skipped | Poor |
| Upside Down, Mirror | Read as the unrelated letters they actually are (ɐ is a real phonetic letter) | Misleading |
| Lookalike alphabets (Manga, Samurai, Elven) | Read as Chinese, Cherokee or Georgian letters, or skipped | Misleading |
| Glitch / Zalgo | Each combining mark announced, or a long pause, or the app crashes the speech queue | Worst |
Two things are worth noticing. “Skipped” is not harmless: if your name is skipped, a blind follower does not know who they are looking at. And “misleading” is arguably worse than “spelled out”, because the reader hears confident nonsense with no signal that something is missing.
If you want emphasis that is genuinely accessible, the vaporwave fonts page is the safest style on the whole site, and Bold Sans from the bold fonts page is the least disruptive of the math-letter styles.
Using fancy text responsibly
You do not have to give it up. You have to put it where it does the least harm and provide a way around it.
- Headings and names only. Style a title, a display name or a single emphasised word. Never style a sentence that carries information: prices, dates, instructions, links, “DM to order”.
- Always keep a plain fallback. If your display name is styled, make sure the plain spelling appears in your handle or the first line of your bio. Screen reader users, and search engines, will use that.
- One styled element per screen. A bio with a styled name is fine. A bio where every line starts in a different alphabet is exhausting to listen to and impossible to skim with a braille display.
- Avoid glitch text in shared spaces. In group chats, comment threads and server channels, it affects everyone scrolling past, not just the people who chose to read it. Keep it to the glitch fonts page’s lightest variant if you use it at all, and never in a name.
- Do not use fancy text for hashtags, mentions or URLs. They stop working for everyone, not just screen reader users.
- Prefer real formatting when the platform has it. Discord Markdown, a bold button in a document, or an actual heading element in a website are read correctly and cost nothing. Fancy Unicode is for the places that offer no formatting at all.
- Write alt text and captions in plain text. Image descriptions are read aloud by definition; a styled word inside one defeats the purpose.
For anything that is meant to be printed, tattooed or turned into a logo, use a real font file rather than pasted characters. Real fonts change only how letters are drawn, so the text underneath stays ordinary and readable by everything.
A two-minute test on your own phone
The quickest way to understand the problem is to hear it. You do not need to turn on a full screen reader; both platforms have a lighter feature that reads selected text aloud.
iPhone or iPad
- Go to Settings → Accessibility → Spoken Content and turn on Speak Selection.
- Paste a styled name from the fancy fonts page into Notes or a message draft.
- Select the text and tap Speak in the popup menu.
- Repeat with two or three styles: Bold Sans, Bold Cursive and Glitch will give you the full range.
For the real thing, go to Settings → Accessibility → VoiceOver and switch it on, then swipe right through your own profile in Instagram or TikTok. To turn it off again, triple-click the side button if you have set the Accessibility Shortcut, or ask Siri to turn off VoiceOver.
Android
- Open Settings → Accessibility → Select to Speak (the name varies slightly by manufacturer) and turn it on.
- Paste a styled name into Keep, Messages or any text field.
- Tap the accessibility button, then tap or drag over the text to hear it.
For the full experience, enable TalkBack from the same Accessibility menu. Be aware that TalkBack changes how touch works (single tap selects, double tap activates), so read the on-screen tutorial before dismissing it, or hold both volume keys for a few seconds to switch it off.
Whichever route you take, listen for three things: whether the word is spoken as a word, whether each letter comes with a long description, and whether anything is silently dropped. Then look at your own profile and ask whether a stranger could still find out who you are and what you do with the styled parts removed. If the answer is yes, you are using fancy text well.
Summary
- Screen readers either spell styled letters out with long Unicode names, skip them, or (sometimes) normalise them; you cannot pick which.
- Fullwidth text and Bold Sans are the least disruptive; glitch, upside-down and lookalike alphabets are the worst.
- Use fancy text for a name or heading only, and keep every piece of real information in plain characters.
- Provide a plain fallback: the handle, the first bio line, or a caption.
- Test with Speak Selection or Select to Speak; it takes two minutes and you will not forget what you heard.