wcag-audit-perceivable-media-deep
Audio and video accessibility rules for multimedia content design
Audio and video accessibility rules for multimedia content design
When to Use
Apply when implementing videos, audio content, podcasts, or other time-based media.
Rules
- Provide text alternatives for audio-only content
- Include captions for video content with spoken dialogue
- Provide audio descriptions for important visual information
- Ensure media controls are keyboard accessible and clearly labeled
- Provide transcripts for audio and video content
- Allow users to control media playback independently
- Ensure media doesn't auto-play with sound
- Provide sign language interpretation when needed
Avoid
- Auto-playing media with audio that cannot be muted
- Video content without captions for spoken dialogue
- Media controls that are not keyboard accessible
- Audio content without text alternatives
You Might Also Like
Related Skills
fix
Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.
facebook
frontend-testing
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
langgeniusfrontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
langgenius
code-reviewer
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
google-gemini
session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
moltbot