This check finds <object> elements without a text alternative or other accessible identification of their content and purpose.
Why this matters
Embedded documents and media may not be available to every browser or assistive technology. Users need to know what the object contains and, when possible, have a direct alternative route to the information.
How to fix it
- Add concise fallback content between the opening and closing
<object>tags. - Provide a direct link to the embedded document or an equivalent accessible HTML version.
- Use an appropriate accessible name through visible text or ARIA when the object is interactive.
- Prefer modern semantic elements such as
<img>,<video>, or<iframe>when they match the resource better.
When the finding appears across many URLs, fix the shared component or layout that produces it instead of patching generated HTML page by page. Recheck representative templates and responsive states after deployment so the correction does not create a regression elsewhere.
How to verify the fix
Disable or block the embedded resource and confirm the fallback remains useful. Inspect the accessibility tree and test any alternative link using only the keyboard.
Keep before-and-after evidence for the affected URL, original output, correction, and verification method. If markup changes after load, test consent states, localization, responsive variants, and client-side navigation because the initial HTML and rendered DOM can differ.