Guide · Agent skill
How to use the Audio Descriptions Review agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The audio-descriptions skill is an agent skill, a set of instructions you add to an AI coding agent so it knows how to do a specific task. This one teaches the agent to review web pages and video code for audio descriptions, a narration track that describes on-screen visuals for blind and low-vision viewers. After this guide you will know how to install the skill, ask for a review in plain language, and read what the agent reports.
Audio Descriptions Reviewthedaviddias/Front-End-Checklist · MIT Download the skill Quick start
- 1Download the ZIP. Get the audio-descriptions skill ZIP from the Front-End Checklist page.
- 2Unzip the skill folder. Extract it into ~/.claude/skills/ for personal use, or into .claude/skills/ in a project.
- 3Or upload it in the Claude apps. In the Claude apps, open Settings, go to Capabilities, then Skills, and upload the ZIP.
- 4Ask for a review. Describe the video or page in plain language and mention accessibility or audio descriptions.
- 5Read the findings. Check the exact markup the agent flags and the fix it suggests, such as a kind='descriptions' track.
- 6Verify the fix. Test the change with browser accessibility tools or a screen reader, as the agent recommends.
What does the audio-descriptions skill make the agent do?
When you ask for a review, the agent checks whether videos that convey visual-only information, such as actions, expressions, scene changes or on-screen text, have a description track. It looks for the HTML track element with kind='descriptions'.
If a video has no description track, the agent suggests fixes. These include adding a separate description track, providing an extended description version with pauses for descriptions, or putting visual details into the main narration. It then points to the exact markup or missing elements and explains how to verify the fix with browser accessibility tooling or assistive technology.
- Finds video content that shows information not available in the audio
- Checks for a track element with kind='descriptions'
- Suggests a fix: separate track, extended version, or richer narration
- Flags exact markup and explains how to verify the change
Install the audio-descriptions skill
Download the ZIP for the skill from the Front-End Checklist page. Unzip it so the skill folder sits in your personal skills directory, ~/.claude/skills/, or in a project's .claude/skills/ folder if you want it to apply only to that project.
If you use the Claude apps instead, open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project
- Claude apps: Settings, then Capabilities, then Skills, then upload the ZIP
How do you trigger the skill with a natural request?
You do not need a special command. Describe the task in normal language that mentions video and accessibility, and the agent should load the skill when it matches. The skill description is about reviewing rendered HTML and components for audio descriptions, so requests that name those things work best.
Give the agent the file or page to review. Be specific about what you want checked, for example the video player markup or a page template.
- Review the video on this page for audio descriptions.
- Check whether our product demo needs an audio description track.
- Audit this video player markup for accessibility and tell me what to fix.
- Does this course video need an extended description?
What does a correct video look like?
The reference material shows a video with a separate captions track for deaf users and a separate descriptions track for blind users. The descriptions track uses kind='descriptions' and points to a WebVTT file. Use this as the pattern the agent compares your code against.
- Keep captions and descriptions as separate track elements
- Set kind to 'descriptions' for the audio description track
- Set srclang and label so users can pick the right track
<video controls>
<source src="product-demo.mp4" type="video/mp4">
<track kind="captions" src="captions-en.vtt" srclang="en" label="English">
<track kind="descriptions" src="descriptions-en.vtt" srclang="en" label="English Audio Description">
</video>What does the skill need, and is it safe to run?
The skill lists no required tools or dependencies. It does not run scripts and does not use the network, so it only supplies instructions and reads the code you give it. The skill is licensed under MIT.
The skill is guidance, not a legal sign-off. Treat its output as a checklist to work through, and check the results with real browser tools or a screen reader.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
- Licence: MIT
What the skill does not do
The skill does not write the audio description script or record narration. It focuses on markup and checks. Write the descriptions yourself or with a production team, then use the skill to confirm they are wired up correctly.
A checklist-style review cannot replace an accessibility audit against the specific standard that applies to your project. Use it to catch common problems early.
- Not a script writer or narration recorder
- Not a substitute for a formal accessibility audit
What people use it for
- A front-end developer adding a product demo video checks the player markup before launch.
- A QA reviewer audits a set of training videos against an accessibility checklist.
- A team new to accessibility asks for a plain-language explanation of why descriptions matter, then fixes its video pages.
Frequently asked questions
How do I install the audio-descriptions skill?
Download the skill ZIP from the Front-End Checklist page and unzip it into ~/.claude/skills/ for personal use or into .claude/skills/ in a project. In the Claude apps, you can instead upload the ZIP under Settings, Capabilities, Skills.
Does the audio-descriptions skill require anything else to run?
The skill lists no required dependencies. It does not run scripts and does not use the network, so you do not need to install extra tools to use it.
Is the audio-descriptions skill free to use?
The skill is licensed under MIT. Check the licence file in the skill's source repository for the full terms.
Can the skill write my audio description script?
No. The skill provides review guidance and focuses on markup and checks. It does not write descriptions or record narration.
What is the difference between a captions track and a descriptions track?
Captions give deaf users the spoken dialogue and sounds as text. A descriptions track, marked kind='descriptions', gives blind and low-vision users a narration of on-screen visuals. The two should be separate track elements.
Is a skill review enough for legal accessibility compliance?
No. A checklist-style review cannot replace an accessibility audit against the specific standard that applies to your project. Use the skill to find common issues early, then get a formal audit where compliance matters.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you build or review video pages and want a fast, plain-language check for audio descriptions, especially if your team is new to accessibility. Pick something else if you need someone to write descriptions or sign off on legal compliance, since this skill only reviews markup and guides checks.
Download the skill