Review videos for information conveyed only through images, such as actions, expressions, and on-screen text. Identify missing audio descriptions and outline options for a separate description track, an extended version, or descriptions within the main narration.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide audio descriptions for video. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Run score Not tested
See how to installIdentifies information conveyed only through a video’s images and checks whether audio descriptions are available. It examines actions, facial expressions, scene changes, and on-screen text, including whether existing dialogue or narration already conveys that information. Where descriptions are missing, it outlines three options: a separate description track, an extended version with pauses for descriptions, or descriptions added to the main audio.
Use it with product demonstrations or videos that tell a story to check whether blind and low-vision viewers receive the information they need. It also supports reviews of HTML and interaction states associated with videos embedded in web pages and their players.
The source specifies a track element with kind='descriptions' for a separate track. If gaps between dialogue are too short, an extended version with pauses for descriptions is another option to consider.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Blind users miss critical plot points, product demos, and on-screen information that's only shown visually—audio descriptions provide equal access to the complete experience.
Identify videos where visual content conveys information not available in the audio track (actions, expressions, scene changes, on-screen text). Verify audio descriptions are available or visual content is described in dialogue.
Add a separate audio description track using the track element with kind='descriptions'. Alternatively, provide an extended version with pauses for descriptions, or include visual descriptions in the main narration.
Explain how blind and low-vision users miss visual-only information in videos, and why audio descriptions provide equal access to the complete content experience.
Review the rendered markup and interactive states that affect Provide audio descriptions for video. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/audio-descriptions
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.