In one paragraph
Object elements must have alternative text means a tested displayed object lacked an accepted accessible name. Name the embedded resource appropriately and provide equivalent information or an accessible route to it where needed. Fallback children alone are not a dependable label when the object loads. Do not flatten an interactive document into a single image role merely to clear a naming check.
Why it matters
An object can represent an image, a document, or another embedded resource. A short name tells a user what that region is, but cannot make the embedded PDF, chart, or application itself accessible. Evaluate the resource's reading order, controls, and information independently.
Fallback content is used when the browser cannot display the resource. It may not be exposed as the loaded object's name, so text placed between the tags is not equivalent to a reliable naming relationship in every loaded state.
For PDFs, an outside link remains useful even when the viewer loads but fails to provide the document properly. A download link also does not transform an inaccessible file into an accessible one; provide a suitable equivalent or improve the document itself as appropriate.
How WebAuditOS evaluates this finding
The supplied object-alt rule examines applicable visible object elements with data when the browser displays the resource. It recognises supported ARIA names and a non-empty title, with applicability or presentation exceptions described in the source.
Serious impact maps to high severity. Fallback-rendered, hidden, or otherwise inapplicable objects may not be tested. The check does not validate the embedded content's accessibility, and an applicability exception must not be treated as approval to hide a needed interactive resource.
How to fix it
- Identify what the object actually represents and whether it successfully loaded. Distinguish a static picture, complex chart, PDF, or interactive content before choosing naming and semantics.
- Provide a short accurate name through an appropriate mechanism. A PDF example is:
<object data="/documents/delivery-guide.pdf" type="application/pdf" aria-label="Delivery guide PDF">
<a href="/documents/delivery-guide.pdf">Download the delivery guide PDF</a>
</object>
<p><a href="/documents/delivery-guide.pdf">Open the delivery guide PDF separately</a></p>The outside link remains present when the fallback is not shown. The example does not establish that the PDF is accessible.
- Supply an equivalent accessible version where needed, such as maintained HTML instructions or a properly structured document. Keep it aligned with the actual embedded resource rather than offering an obsolete summary.
- For a simple image without required embedded interaction, consider img with a context-appropriate alt instead. Test differences in SVG scripting, external resources, and rendering before changing the delivery mechanism.
- Use role=img only when the object is genuinely a single noninteractive graphic and the implementation supports that model. Do not apply it indiscriminately to a PDF form or a resource with links whose interaction users need.
- Test keyboard entry, exit, focus visibility, zoom, loading failure, and the supported assistive-technology combinations. A named embed can still trap focus or hide meaningful content.
- Inspect CSP object-src and other delivery controls separately. A blocked embed is not fixed by adding an accessible name, and a failing fetch can make the naming rule inapplicable.
- Rescan loaded and fallback states where possible, and retain a manual document review. Keep the alternative route and resource ownership maintained after updates.
What the fix can break
Switching embedding elements can change isolation, interactivity, resource loading, or styling. Review the actual SVG or document features instead of assuming every object can become an equivalent img.
An image role can hide structure intended to remain interactive. Naming must not erase the function users came to access.
Do not rely on a tooltip as the only explanation or available alternative. Make the purpose and a usable route understandable through the interface.
Questions
Does fallback text necessarily name a loaded object?
No. Fallback and accessible naming have different roles. Inspect the computed name while the resource is displayed.
Does a good label make the embedded PDF accessible?
No. Its internal document structure and interaction need separate evaluation.
Should I add role=img to every object?
No. Choose semantics according to the real resource and preserve necessary interaction.
Which related checks help?
Review image alternatives, SVG alternatives, and the automation limits guide.
What severity does this get in the report?
High. An axe finding takes its severity from the impact axe reports for the element that failed, and the report maps critical and serious to high, moderate to medium, minor to low. This rule is declared serious in axe-core, so a failure arrives as high.