- Success Criterion 1.1.1
- Conformance level A
- W3C reference F71
Fancy Unicode Letters Used Instead of Real, Readable Text
1.1.1 — Non-text Content
Scenario
Setting
A dating app's profile setup
What’s wrong
Fancy Unicode 'font' characters are used to imitate styled text — screen readers can't read them as normal words.
Example
<h2>𝒜𝒷𝑜𝓊𝑂 𝑀𝑒</h2> Why it matters
Someone setting up their profile with a screen reader hears a string of cryptic character names instead of "About Me," and has no idea what section they're in.
How to test
Copy suspect 'text' and paste it into a plain text editor: if it renders as unusual Unicode glyphs instead of normal letters, a screen reader will not read it as words.
How to fix
Get stylized type from CSS, never from lookalike Unicode characters. Real text stays readable to every tool; decorative Unicode "fonts" only fool the eye.
<h2 style="font-family: 'Playfair Display', serif; font-style: italic;">About Me</h2> Outcome
A screen reader user hears "About Me" announced clearly and knows exactly which section they're filling in.
Who is affected
Screen reader users, and anyone using text-to-speech or translation tools, all fail to get real words out of lookalike Unicode characters.
Learn more
- Understanding Understanding document (opens in a new tab)
- Technique Related technique (opens in a new tab)
Related scenarios
- Product Photo Added as a CSS Background With No Alt Text
- Chart Alt Text That Never Explains What Each Color Means
- Outdated Alt Text That No Longer Matches the Image
- Alt Text Left as a Filename Instead of a Real Description
- Decorative Image Not Hidden From Screen Reader Users
- Decorative Image Given Alt Text Instead of Being Marked Silent