Implement WCAG 2.1 accessibility standards for semantic HTML, keyboard navigation, ARIA attributes, and screen reader support.
Works with
Covers semantic HTML structure, keyboard navigation (Tab, arrow keys, ESC), and focus management for modals and interactive components
Provides ARIA attribute guidance (aria-label, aria-live, aria-hidden, role attributes) with practical React/TypeScript examples
Includes color contrast requirements (WCAG AA/AAA), visual focus indicators, and testing strategie
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionweb-accessibilityExecute the skills CLI command in your project's root directory to begin installation:
Fetches web-accessibility from supercent-io/skills-template and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate web-accessibility. Access via /web-accessibility in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
62
total installs
62
this week
88
GitHub stars
0
upvotes
Run in your terminal
62
installs
62
this week
88
stars
Make a React modal component accessible:
- Framework: React + TypeScript
- WCAG Level: AA
- Requirements:
- Focus trap (focus stays inside the modal)
- Close with ESC key
- Close by clicking the background
- Title/description read by screen readers
Use meaningful HTML elements to make the structure clear.
Tasks:
<button>, <nav>, <main>, <header>, <footer>, etc.<div> and <span><h1> ~ <h6>) correctly<label> with <input>Example (❌ Bad vs ✅ Good):
<!-- ❌ Bad example: using only div and span -->
<div class="header">
<span class="title">My App</span>
<div class="nav">
<div class="nav-item" onclick="navigate()">Home</div>
<div class="nav-item" onclick="navigate()">About</div>
</div>
</div>
<!-- ✅ Good example: semantic HTML -->
<header>
<h1>My App</h1>
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about">About</a></li>
</ul>
</nav>
</header>
Form Example:
<!-- ❌ Bad example: no label -->
<input type="text" placeholder="Enter your name">
<!-- ✅ Good example: label connected -->
<label for="name">Name:</label>
<input type="text" id="name" name="name" required>
<!-- Or wrap with label -->
<label>
Email:
<input type="email" name="email" required>
</label>
Ensure all features are usable without a mouse.
Tasks:
tabindex appropriatelyDecision Criteria:
tabindex="0" (focusable)tabindex="-1" (programmatic focus only)tabindex="1+"Example (React Dropdown):
import React, { useState, useRef, useEffect } from 'react';
interface DropdownProps {
label: string;
options: { value: string; label: string }[];
onChange: (value: string) => void;
}
function AccessibleDropdown({ label, options, onChange }: DropdownProps) {
const [isOpen, setIsOpen] = useState(false);
const [selectedIndex, setSelectedIndex] = useState(0);
const buttonRef = useRef<HTMLButtonElement>(null);
const listRef = useRef<HTMLUListElement>(null);
// Keyboard handler
const handleKeyDown = (e: React.KeyboardEvent) => {
switch (e.key) {
case 'ArrowDown':
e.preventDefault();
if (!isOpen) {
setIsOpen(true);
} else {
setSelectedIndex((prev) => (prev + 1) % options.length);
}
break;
case 'ArrowUp':
e.preventDefault();
if (!isOpen) {
setIsOpen(true);
} else {
setSelectedIndex((prev) => (prev - 1 + options.length) % options.length);
}
break;
case 'Enter':
case ' ':
e.preventDefault();
if (isOpen) {
onChange✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
686mattpocock/skills
Productivitysame categorypremortem
217parcadei/continuous-claude-v3
Productivitysame categorydeslop
162cursor/plugins
Productivitysame categorytravel-planner
140ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
137pproenca/dot-skills
Productivitysame categorynutritional-specialist
132ailabs-393/ai-labs-claude-skills
Productivitysame categoryReviews
4.7★★★★★31 reviews- CChaitanya Patil★★★★★Dec 28, 2024
web-accessibility is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- MMeera Ramirez★★★★★Dec 24, 2024
web-accessibility fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- SSoo Smith★★★★★Dec 20, 2024
web-accessibility has been reliable in day-to-day use. Documentation quality is above average for community skills.
- IIra Jain★★★★★Dec 4, 2024
Keeps context tight: web-accessibility is the kind of skill you can hand to a new teammate without a long onboarding doc.
- IIra Ghosh★★★★★Nov 23, 2024
web-accessibility is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- PPiyush G★★★★★Nov 19, 2024
Keeps context tight: web-accessibility is the kind of skill you can hand to a new teammate without a long onboarding doc.
- SSakura Bansal★★★★★Nov 11, 2024
Useful defaults in web-accessibility — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- SSoo Mehta★★★★★Nov 7, 2024
Solid pick for teams standardizing on skills: web-accessibility is focused, and the summary matches what you get after install.
- HHana Rahman★★★★★Oct 26, 2024
We added web-accessibility from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- IIra Torres★★★★★Oct 14, 2024
Useful defaults in web-accessibility — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 31
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.