Provide text alternatives for embedded objects or plugins

WCAG 1.1.1
Non-text Content

Content available in English only.

Accessibility isn’t just about avoiding violations — it’s about ensuring that everyone can use your product with confidence. This guide explains each rule’s intent, highlights common issues, and shows how to fix them according to WCAG and the European Accessibility Act (EAA).

These guidelines do not replace the official WCAG standards. They’re concise, developer-focused notes to help you identify and fix issues effectively.

If the object disappears, the meaning must remain.

Why this matters and how to fix it

Why this matters

Assistive technologies cannot interpret the visual content of embedded objects like custom charts, maps, media players, PDFs, or legacy applets. If an `<object>` or `<embed>` does not include a text alternative or accessible fallback, users who cannot perceive the visual content will miss critical information.

How to fix this issue

Include meaningful fallback text between the opening and closing `<object>` tags, or place a descriptive text alternative near the object. If the object conveys structured or interactive information (charts, graphs, dashboards), provide a textual summary or accessible HTML equivalent.

Automated detection · Manual review recommended

Developer guidance

Do not rely on the embedded content being self-accessible — treat it as non-text. When embedding data visualizations, always include a chart summary + textual interpretation. For PDF viewers, provide a direct 'Download PDF' link plus a brief description of the content.

Code examples

Incorrect Implementation

<object data="chart.swf"></object>

Correct Implementation

<object data="chart.swf">Bar chart showing Q2 revenue growth of 25%.</object>

Real-World Examples

Before

<object data="report.pdf"></object>
<!-- Screen reader users hear nothing → content inaccessible -->

After

<object data="report.pdf" type="application/pdf">
  <p>This report is also available as:
    <a href="report.pdf">Download the accessible PDF</a>
  </p>
</object>

Manual testing

  1. 1. Locate any <object>, <embed>, or <applet> elements in the DOM.
  2. 2. Disable or block the embedded media (e.g., browser devtools → network → block request).
  3. • Expected: A meaningful text fallback is displayed instead.
  4. 3. Turn on a screen reader and navigate to the embedded object.
  5. • Expected: The fallback text or description is read aloud.
  6. 4. If the object conveys complex data (charts, dashboards, maps), confirm that a textual summary explains the key insights.
  7. 5. If the object is purely decorative, remove it or add `aria-hidden="true"`.
eu icon getwcag

Trusted by organizations across Europe working toward WCAG and EAA conformance