Screen readers cannot translate non-text content.
Adding alternative text to define
<object> elements helps screen readers convey meaning to users.
Lighthouse reports when any
<object> elements do not have alternative text:
How to fix this problem
To fix this problem,
provide alternative text for every
The alternative text describes the information contained in the embedded object
and goes inside the object element as regular text
like "Annual report" below:
2019 Web Accessibility Report
Learn more in Include text alternatives for images and objects.
You can also use
alt and ARIA labels to describe object elements,
<object type="application/pdf" data="/report.pdf alt="2019 Web Accessibility Report">
(see <object> elements must have alternate text)
Tips for writing effective
- As previously mentioned, describe the information contained in the embedded object.
- Alternative text should give the intent, purpose, and meaning of the object.
- Blind users should get as much information from alternative text as a sighted user gets from the object.
- Avoid non-specific words like "chart", "image", or "diagram".
Learn more in WebAIM's guide to Alternative Text.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.