Fancy Text and Screen Readers: The Honest Guide
Some fancy styles replace your letters and are read out as Unicode character names. Others only mark them and stay readable. Here is which is which, and where to use each.
Most fancy text sites either ignore accessibility completely or wave at it with a line about using styles responsibly. Neither is useful, because the styles do not all behave the same way. Some are genuinely harmless. Some make your text unreadable to a portion of your audience. The difference is mechanical, and once you know it you can decide for yourself.
Two classes of style
Fancy text works in one of two ways, and everything downstream follows from which one you picked.
Replaced styles swap each of your letters for a different Unicode character that happens to be drawn in a styled shape. 𝐇𝐞𝐥𝐥𝐨 does not contain the letter H. It contains U+1D407, mathematical bold capital H, which is a different character entirely. This covers the bold, italic, script, fraktur and double-struck alphabets, the enclosed styles such as Ⓗⓔⓛⓛⓞ and 🅷🅴🅻🅻🅾, fullwidth text such as Ｈｅｌｌｏ, small caps, superscript and subscript, upside down and mirror text.
Marked styles leave your letters alone and add a combining mark after each one. H̶e̶l̶l̶o̶ contains the real letters H, e, l, l, o, each followed by a zero-width character that tells the renderer to draw a line through it. This covers strikethrough, underline, overline, slashed and the glitch styles.
Every style page on CopyFont states which class the style is in, because it is the fact that determines everything else.
What a screen reader does with a replaced style
A screen reader reads a stream of characters and looks each one up. For H it says the letter. For U+1D407 there is no letter to say, so the fallback is the character’s official Unicode name: “mathematical bold capital H”. Do that across a word and a sentence becomes a slow recitation of character names.
That is the worst case, and it is a real one. It is not the only behaviour, though, and this is where honesty matters more than a scary example. What actually happens depends on the screen reader, its version, the verbosity level the user has chosen, the speech synthesiser, and whether the platform has done any normalisation of its own before the text reaches the reader. Accessibility practitioners who have tested this in detail describe an inconsistent picture rather than a single failure mode: see the write-ups by Scope and by Eleven Ways.
The behaviours reported across that testing fall into three groups:
- Announcing the full character name. Verbose, slow, and the reader has to reconstruct the word from letter names.
- Announcing something short and unhelpful, such as a generic symbol description, which loses the word.
- Skipping the character in silence. NVDA has been observed passing over some characters without announcing anything at all. This is the most damaging outcome, because nothing signals that content was missed. The listener does not hear a mangled word; they hear a shorter sentence and have no way to know.
The user can usually change verbosity settings to get more information, but that is not a fix. It means the burden of decoding your decorative text has been moved onto the person least able to spare the effort, and they have to know to do it.
The problems that are not about screen readers
Replaced styles break more than speech, and these effects hit everyone.
Search stops matching. 𝐇𝐞𝐥𝐥𝐨 is not Hello, so ctrl-F on the page, the platform’s own search, and search engines will not find it. A styled hashtag is a different hashtag. A styled brand name will not surface when someone searches your brand.
Copying gives the wrong string. Someone who copies your styled email address, product name or code and pastes it somewhere that expects plain text ends up with something that does not work, and often cannot see why.
Rendering is not guaranteed. A device whose installed fonts do not cover the block draws a box. Enclosed and filled-square styles are particularly exposed here, because on some systems they are rendered by the emoji font and appear as coloured tiles rather than letters.
Machine translation stops working. Automatic translation, which many readers rely on, treats the characters as symbols and leaves them untranslated. Since CopyFont pages exist in six languages, this one is worth stating plainly: styled text does not translate.
Why marked styles are different
Because a marked style keeps the original letters, none of the above applies in the same way. Search matches, copying gives you the real text, and a screen reader reads the actual word.
The combining marks are not free. A reader may announce the mark, and heavy glitch text stacks many marks per letter, which can produce a long run of announcements and can also overflow visually into the lines above and below. But the word underneath is intact and recoverable, which is the important difference. If you want visible style with the least harm, strikethrough, underline, overline and slashed are the honest choice.
Practical placement rules
These are the rules we would apply to our own profiles.
Use styled letters for a short display name. A profile name in script or bold is a few words, decorative, and sits next to a plain @handle that carries the same information in a readable form. The cost is bounded and there is a plain fallback in view.
Never style a whole bio. A bio is content. It says what you do and how to reach you. A bio in mathematical alphanumerics is unsearchable, untranslatable, and either recited character by character or silently dropped.
Never style anything a reader has to act on. Links, email addresses, prices, dates, discount codes, calls to action, instructions, hashtags. If a person needs to read it accurately, copy it or search for it, it must be plain.
Never style the only copy of information. If a styled word carries meaning that appears nowhere else in plain form, some readers will not receive it.
Do not use replaced styles to fake emphasis in a long post. The character names are read aloud in the middle of your sentence, which is precisely the opposite of emphasis. Where the platform has real formatting, such as Discord and WhatsApp markdown, use it.
Test one style before you commit to it. Send it to yourself on a second device, ideally an older one, and look at whether the letters render or box out. The style index shows a live sample of each style in your own browser, which is the fastest check available.
The short version
Styled text is a decoration applied to the characters themselves, so it travels everywhere the text travels, including into places where it stops being text and starts being an obstacle. Keep it short, keep it next to a plain version, and keep it out of anything functional. That is the whole of the advice, and it costs you almost nothing visually.
Frequently asked questions
Quick answers to what people ask us most
Does a screen reader really say 'mathematical italic capital A'?
That is the character's Unicode name, and announcing the name is the correct fallback when no better pronunciation is available. Whether you hear it depends on the screen reader, its verbosity setting and its version. Some read the name, some read something shorter, and some skip the character entirely.
Which styles are safe to use?
Strikethrough, underline, overline, slashed and the lighter glitch styles keep the original letters and add a combining mark, so the text stays searchable and readable. They are the only fancy styles that do not change what the text is.
Is it ever acceptable to use styled letters?
Yes, in short display text where the words are decorative and repeated in plain form somewhere nearby. A styled display name next to a plain handle is fine. A styled bio, caption, post or anything a reader has to act on is not.