Fancy characters carry a hidden cost for blind users: screen readers don't recognize decorated letters and many announce the full table name — 𝗕𝗼𝗹𝗱 becomes “mathematical sans bold B, mathematical sans bold o”, completely unintelligible.
This isn't a ban on fancy text — it's a boundary map: where to use it freely, where to hold back, and where never to.
How screen readers read styled letters
Screen readers turn characters into speech using name tables. Ordinary letters have short names (“B”); styled math letters carry formal names like “MATHEMATICAL BOLD CAPITAL B” — announced as a description string.
Support varies by reader and version; newer ones try to fold the names, but coverage is patchy. The safe assumption: styled characters come out as noise.
Where to draw your own lines
- Free to decorate: display names, bios, signatures — identity decoration, and assistive tech locates you by your ID anyway.
- Use sparingly in content: one or two stressed words in a post; full styled paragraphs are an readability disaster.
- Never in function fields: verification codes, payment details, critical notices — systems validate plain characters only.
- Combining marks are the worst: strike/zalgo add per-character noise; avoid where information density matters.
Better tools for emphasis
To emphasize without sacrificing readability, prefer the platform's native formatting: Discord markdown, WhatsApp *bold*, Reddit formatting. Those are layout-level and read correctly.
Give fancy characters the identity job: make the nickname recognizable and the signature stylish — they exist to be seen, not read aloud.