Provide text alternatives for embedded objects or plugins
Accessibility isn’t only about avoiding violations — it’s about ensuring your product can be used confidently by everyone. This guide explains the principle of this rule, shows what goes wrong in real-world code, and provides a verified fix that meets WCAG and the European Accessibility Act (EAA).
Why this matters and how to fix it
Why this matters
Objects such as Flash, Java applets, or custom embeds may not be accessible. Without fallback text, users relying on assistive technology will have no way to access the content.
How to fix this issue
Use the `<object>` element’s body content or a text alternative nearby to describe its function. Consider replacing inaccessible technologies with modern, accessible HTML5 equivalents.
Developer guidance
Avoid legacy technologies like Flash. Provide a textual or HTML fallback for all multimedia or embedded widgets. Ensure the fallback is updated when the object changes.
Code examples
Incorrect Implementation
<object data='chart.swf'></object>Correct Implementation
<object data='chart.swf'>Bar chart showing Q2 revenue growth of 25%.</object>
Trusted by organizations across Europe working toward WCAG and EAA conformance