← Back to guides

Emojis and Icons

How screen readers handle emoji and when icons need labels

Text & Links

Emojis and icons can add personality and visual clarity to content, but when used incorrectly, they create barriers. Screen readers announce emoji names - often in unexpected ways - and relying on icons alone to convey meaning excludes users who cannot see them.

What to avoid

Using emojis as the sole way to communicate information:

📅 Wednesday, February 26th ⏰ 4–6 PM 🍪 Light refreshments served
Problems with this pattern
  • A screen reader might announce: "calendar spiral notepad Wednesday February 26th alarm clock 4 to 6 PM cookie light refreshments served" - interrupting the actual content with emoji names
  • Emoji meanings vary by culture and are not universally understood
  • Over-relying on emojis increases cognitive load for users with dyslexia or ADHD
  • Some emojis render differently (or not at all) across operating systems and devices

Best practice for emojis

Put information in text first. Add emojis for visual enhancement only, and mark them so screen readers skip them:

<!-- Text comes first; emoji is decorative -->
<p><span aria-hidden="true">📅</span> Wednesday, February 26th,
4–6 PM. Light refreshments will be served.</p>

Accessible icon usage

For SVG icons that carry meaning, provide an accessible label:

<!-- Icon with visible text - mark SVG as hidden -->
<button>
  <svg aria-hidden="true" focusable="false">...</svg>
  Download report
</button>

<!-- Icon-only button - use aria-label -->
<button aria-label="Close dialog">
  <svg aria-hidden="true" focusable="false">...</svg>
</button>
Key principles
  • Never rely on an icon alone to convey meaning - always pair with visible text or an accessible label
  • Mark decorative emojis and icons with aria-hidden="true"
  • Use aria-label for icons that are the sole content of an interactive element
  • Keep emoji use minimal - a few well-placed emojis are fine; emoji-heavy text is not

Why it matters

When emojis and icons are used without text alternatives, screen reader users hear a string of emoji names interrupting the actual content. Users with cognitive disabilities or sensory sensitivities may find emoji-heavy text harder to process. Putting the information in text first ensures everyone gets it.

WCAG criteria

Referenced criteria
1.1.1 Non-text Content (opens in a new tab) - Meaningful icons and emojis need text alternatives. A
1.3.1 Info and Relationships (opens in a new tab) - Information must be conveyed through text, not visuals alone. A