Not “never use it” — but a fully styled sentence can be silent or unintelligible to a screen reader. Here’s the honest picture and the simple rule.
It can be, if you overuse it. Styled Unicode letters are mathematical symbols, not real letters, so a screen reader may skip them entirely (losing your meaning), spell them out one at a time as “mathematical bold capital B…”, or mispronounce them — and behaviour differs by reader. A whole styled sentence can become unusable. It’s not a reason to never use it: style a word or two for emphasis, and keep names, messages and calls to action in plain text.
There’s no single behaviour — and that’s the problem. Across the common readers, styled Unicode is handled three incompatible ways:
Because these aren’t letters wearing a style — they’re separate characters from a block Unicode built for equations. Assistive tech reads them by their character identity, which is “mathematical bold capital B,” not “B.” The same property breaks search and Ctrl+F, for the same reason.
Keep every load-bearing word — your name, the core message, any call to action — in plain text, and use styling only for emphasis a listener can afford to miss. Style a word, not a paragraph. Done this way it adds personality at almost no accessibility cost. The full version, with a screen-reader demo, is in the fancy fonts & accessibility guide.
Generate emphasis for a word or two and leave your core message readable — the accessible way to use styled text.
Open the Text Generator →Related: the deeper fancy fonts & accessibility guide, is LinkedIn bold text safe, and is fancy text bad for SEO.
It can be if overused. Screen readers may skip styled Unicode, spell it out one glyph at a time as “mathematical bold capital B,” or mispronounce it, so a fully styled sentence can be silent or unintelligible. Used on a word or two, with the core message in plain text, it is low-risk.
Behaviour varies by reader: some skip the styled text entirely, some read each character by its Unicode name (“mathematical bold capital B…”), and some mispronounce it. There is no consistent, reliable pronunciation.
Yes, sparingly. Emphasise a word or two and keep your name, message and any call to action in plain text so screen-reader users don’t lose the meaning. Avoid styling whole posts.
Follow the plain-core rule: load-bearing words stay plain, styling is only decoration a listener can miss. Style a word, not a paragraph, and never hide essential meaning inside styled characters.
Styled Unicode used for meaning can create WCAG problems because assistive tech may not convey it correctly. Used purely as decoration alongside plain-text content, it is much lower risk. Keep the real information in plain text.