Embedded objects have no text alternative
Automated check object-alt, run with axe-core
- WCAG
- 1.1.1 Non-text Content (Level A)
- Severity
- Serious: completable, but painful
- Typical effort
- Quick win, under 1 hour
- Category
- Content
Who this affects
Screen reader users encountering embedded PDFs, plugins or legacy objects.
Why it matters
The embedded content is announced as an unlabelled region the user cannot interpret or confidently skip past.
How to fix it
Add a text alternative inside the <object> element, or an aria-label describing what it contains.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.