What Screen Readers Do with Styled Unicode Text

We build a tool that produces Unicode styled text, so let's be straight about its biggest cost: to a screen reader, 𝐇𝐞𝐥𝐥𝐨 is not the word "hello." Depending on the software and settings, it is announced as "mathematical bold capital h, mathematical bold e..." — one symbol at a time — or skipped as unpronounceable. A post written entirely in styled characters is noise, or silence, to a blind reader. This page explains why that happens and how to use styling without shutting people out.

What actually happens

VoiceOver (Apple), NVDA and JAWS (Windows) read text by looking up each character's identity in Unicode. A real bold word carries formatting around normal letters, so a screen reader says the word — and can announce the emphasis. A Unicode-styled word contains no normal letters at all. Each 𝐥𝐞𝐭𝐭𝐞𝐫 is a distinct symbol whose official name is something like Mathematical Bold Small L. The results vary by product and verbosity setting, and none of them are good:

• Spelled out: "mathematical bold capital s, mathematical bold a, mathematical bold l, mathematical bold e" — four words of audio per letter.
• Skipped: some configurations pass over unknown symbols silently, so your emphasized phrase — usually the most important one — simply vanishes from the sentence.
• Garbled: partial recognition produces fragments that sound like a broken connection.

Why: these are math symbols, not letters

The characters come from Unicode's Mathematical Alphanumeric Symbols block, added so that mathematicians could distinguish a bold v (a vector) from an italic v (a variable) in plain text. Their semantics are mathematical notation. Assistive technology handles them exactly as specified — the surprise is ours, for using math notation as typography. That's also why these characters break search and spell check: Unicode bold vs real bold covers that side of the trade.

Who this affects

Millions of people rely on screen readers full-time, and many more use text-to-speech situationally — while driving, cooking, or because reading long text on a phone is hard. On LinkedIn specifically, recruiters and professionals with visual impairments are part of the audience you post for. If your post's key claim is styled, it is precisely the part they lose.

How to style responsibly

1. Style a word or two, never the message. One bolded phrase in a plain paragraph degrades gracefully: a screen-reader user loses a little emphasis, not the meaning. A fully styled post loses everything.
2. Never style information itself. Names, dates, prices, links, hashtags and email addresses must stay plain — they're the parts people search for, copy, and need read aloud correctly.
3. Make the sentence work without the styling. If the emphasis carries meaning ("do NOT reply before Tuesday"), say it in words too.
4. Prefer real formatting wherever the platform allows it. WhatsApp and Discord have markup, Facebook Groups have a toolbar, and email supports real rich text — which screen readers announce as actual emphasis. Our email page exists largely to make that point.

What Boldify does about it

Two product decisions follow from this page. First, the editor's Copy as Rich Text button produces real <strong> HTML — in any destination that accepts rich text, screen readers get genuine emphasis, not symbols. Second, Format with AI bolds selectively — a handful of key phrases — rather than styling text wholesale, which is the pattern that keeps posts legible to everyone.

Unicode styling is a workaround for platforms that forbid formatting. Workarounds have costs; this is the main one. Use it where it's the only option, keep it small, and your posts stay readable to every reader — see where Unicode bold works and where it fails for the platform-by-platform picture.

Frequently asked questions

Is it wrong to use Unicode bold at all?

No — on platforms with no real formatting, a styled word or two is a reasonable trade. The problems come from styling whole sentences, or styling the information itself rather than the emphasis around it.

Do screen readers handle italic or script styles any better?

No — every style from the Mathematical Alphanumeric Symbols block (italic, script, fraktur, double-struck, monospace) has the same problem. Decorative styles are often worse, because fewer fonts carry their glyphs.

How do I check what my post sounds like?

Turn on your device's built-in screen reader — VoiceOver on iPhone/Mac, TalkBack on Android, Narrator on Windows — and have it read your draft. Thirty seconds of listening teaches more than any guide.