What This Rule Checks
For users who rely on assistive technologies such as screen readers, the content within an <object> element needs to be properly described so that they understand the purpose or function of the object. If the <object> element lacks a descriptive text alternative, users who cannot see the visual content may not be able to interact with or comprehend the information being conveyed.
Who Is Affected
This issue primarily affects: Blind users, who rely entirely on screen readers or braille displays to navigate and interact with content; Deafblind users, who rely on braille displays and cannot access visual or auditory content.
Why This Matters
Embedded objects without alternative text are invisible to screen reader users. The fallback content inside <object> tags also serves as the accessible description. This violates WCAG 1.1.1 (Non-text Content).
How to Fix
Ensure that each <object> element includes either an alt attribute, an aria-label, or an aria-labelledby attribute to provide a text alternative. For purely decorative objects, consider using the role=”presentation” or role=”none” attributes to hide them from screen readers.
Code Examples
<!-- Object with no alternative text -->
<object
data="animation.swf"
type="application/x-shockwave-flash">
</object>
Copy
<!-- Object with fallback text -->
<object
data="animation.swf"
type="application/x-shockwave-flash">
<p>
Interactive animation showing the product assembly process.
</p>
</object>
<!-- Or using aria-label -->
<object
data="chart.swf"
aria-label="Sales performance chart for Q3 2025">
</object>
Copy
Common Mistakes to Avoid
- Leaving <object> elements completely empty with no fallback content.
- Providing fallback content that doesn’t describe the embedded object’s purpose.
- Not considering that many embedded object formats (Flash, Java) are obsolete.
AI Auto-Fix Available
This rule supports ACE™ AI Auto-Fix. When a violation is detected, ACE can automatically generate a code fix for review. The AI analyzes the specific element in context and proposes a targeted remediation that preserves your existing markup and styling. You can preview, modify, and approve the fix before it is applied.
Tip: Multimedia content must be accessible to users who cannot see or hear. Provide captions for video, transcripts for audio, and text descriptions for visual-only content. Always include user-controllable playback.
Related WCAG Criteria
- 1.1.1: Non-text Content