Start scanning free

( Perceivable / WCAG 1.1.1 )

Object element has no text alternative

This check maps to Non-text Content. Use the guidance below to confirm the issue, understand who it affects and ship a fix.

Serious Level A WCAG 1.1.1 — Non-text Content

What’s wrong

An object element is embedded without alternative text or fallback content.

Why it matters

Screen reader users may get no usable output from embedded objects. Fallback content gives them access when the object cannot be interpreted.

How to fix it

Use semantic HTML and valid ARIA so assistive technology gets the same state and structure as sighted users. Keep labels and states explicit in markup.

Before
<object data="report.pdf" type="application/pdf"></object>
After
<object data="report.pdf" type="application/pdf">
  <p>Download the report PDF: <a href="report.pdf">Quarterly report</a>.</p>
</object>

If this pattern is generated by a component, fix it once in the shared component so every instance inherits the accessible behavior.

Learn more