Stop pretending your text is bold: why fake formatting breaks accessibility
We need to talk about something that keeps showing up in LinkedIn posts, company updates, and personal branding pep talks: fancy fake bold text. You’ve seen it. You’ve maybe even used it.
𝗟𝗶𝗸𝗲 𝘁𝗵𝗶𝘀, or 𝘁𝗵𝗶𝘀, or even ⓉⒽⒾⓈ.
💡 For everyone using a screenreader: There is a line that uses unicode characters to display something that resembles bold letters. Screenreaders can’t interpret these characters.
💡 For everyone not using a screenreader: Try CTRL + Shift + U in your browser, ot should enable the Read aloud feature for some aha effect
It looks cool, sure. It grabs attention. But it’s also a nightmare for screen readers, completely unsearchable, and let’s be honest: it’s a trick. A formatting hack. And the people using it usually know exactly what they’re doing.
What’s the trick?
LinkedIn doesn’t support bold text, italic, or even basic markdown formatting. So people turn to Unicode font generators: little tools that replace your normal letters with characters from obscure parts of the Unicode table that look bold, italic, or fancy. And yes, it makes the post stand out visually in the feed. That’s the whole point. But it comes at a cost.
It’s not formatting — it’s a lie.
When you type 𝐁𝐨𝐥𝐝, you haven’t added formatting. You’ve swapped normal, readable letters for mathematical symbols. To a screen reader, that’s not “bold”. That’s:
“Mathematical Bold Capital B” Or worse: nothing at all. People who rely on assistive tech won’t hear your clever headline. They won’t get your message. Because your entire paragraph just vanished into something they can’t read or understand. And it gets worse…
And no, it’s not searchable either
This trick also breaks basic functionality like search and indexing. If you write 𝐩𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐯𝐢𝐭𝐲 with fake bold letters, nobody searching for “productivity” will find it. It won’t show up in: LinkedIn search, Browser text search (CTRL+F), SEO indexing and translation tools. It looks like content. But it’s actually just noise. So yes, it’s a trick. And using it to game the feed while leaving part of your audience behind? That’s not clever. That’s unethical. Screen readers don’t see your branding tricks — they parse your intent. If it only works for sighted users, it doesn’t really work. Using formatting hacks to game the feed is tempting, especially when real formatting tools aren’t available. But building attention on the back of accessibility gaps is a dirty move.
Your content should be visible, readable, searchable, understandable. For everyone. If it’s only beautiful to people who can see and ignore the technical glitches, you’ve missed the point.
The real flex? Writing that works for everyone
Using fake formatting to stand out is like putting neon stickers on a car that doesn’t run. It looks good parked. It fails the second someone tries to interact with it. Real professionals know how to write clearly, structure simply, and communicate accessibly. So before you paste in that shiny Unicode headline …Ask yourself:
Am I being clever, or just unreadable?
Spoiler: the best posts are both stylish and searchable.
Published on:
Learn moreWe can help you with Stop pretending your text is bold: why fake formatting breaks accessibility
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
You are holding GitHub Copilot Wrong!
Most developers think that one can’t really use GitHub Copilot wrong. There is a chat interface that lets you also choose a model, so th...
You are holding GitHub Copilot Wrong!
Part 0 showed why constant prompting, re-prompting, and steering GitHub Copilot feels fragile. Not because Copilot is unreliable, but because ...
Building a Multi-Hierarchy Ticket Classification System (Because Keywords Aren't Enough)
Look, I love a good keyword-based system as much as the next developer. They’re fast, predictable, and when your user says “VPN,&r...
Secretless cross-tenant dataverse access
Client secrets are like hiding your house key under the mat; easy to grab and impossible to audit. Certificates are just slightly better, beca...
How Azure CLI handles your tokens and what you might be ignoring
Running az login feels like magic. A browser pops up, you pick an account, and from then on, everything just works. No more passwords, no more...
How Dev Proxy teaches you to make your apps more resilient
I added Microsoft Dev Proxy to my Mermaid → Dataverse converter, because I wanted to test how it handled rate limits and API errors. What I go...
Building Azure functions that never store secrets — ever
What if your function could hit Microsoft Graph with no client secrets, no certs, and no Key Vault entries? That is exactly what a Managed id...
Introducing Mermaid to Dataverse Converter
Why diagrams matter (and why they usually fail us) Entity-Relationship Diagrams (ERDs) are the universal shorthand for talking about data mode...
It’s OK to be seen trying
It’s OK to be seen trying Somewhere along the way, we started believing that you’re only allowed to speak after you’ve figured everything out....
Stuck in pilot - Part 1: no foundations, no future
“We just need to test the AI. We’ll figure out the data later.” That sentence has quietly killed more AI pilots than any model failure ever ...