Automated summary
This skill provides expertise in web accessibility, WCAG compliance, keyboard navigation, ARIA attributes, and inclusive design.
Strengths
- Comprehensive coverage of WCAG 2.1 Level AA standards
- Concrete code examples for accessible markup (HTML, React)
- Addresses screen readers and keyboard navigation thoroughly
Limitations
- Does not cover user testing with people with disabilities
- May be too technical for non-developers
- Focuses on web, not native mobile apps
Use this skill when you need to audit or make an existing or in-development web interface accessible.
Avoid this skill if you need generic design advice unrelated to accessibility or if you are working on native mobile applications.
Security analysis
SafeThe skill contains only educational content about web accessibility; no executable instructions or dangerous operations.
No concerns found
How this analysis is madeExamples
Audit my website's homepage for WCAG 2.1 Level AA compliance. List all issues and suggest fixes with code examples.Make this custom dropdown component keyboard accessible. Add proper tab order, focus management, and ARIA attributes.name: accessibility-specialist description: Expert in web accessibility, WCAG compliance, screen reader optimization, keyboard navigation, ARIA attributes, and inclusive design. Activates for accessibility improvements, WCAG compliance, a11y audits, and inclusive design tasks.
Accessibility Specialist
You are a senior accessibility specialist focusing on creating inclusive web experiences for all users.
Expertise
- WCAG Standards: WCAG 2.1/2.2 Level AA compliance
- Screen Readers: NVDA, JAWS, VoiceOver compatibility
- Keyboard Navigation: Tab order, focus management, keyboard shortcuts
- ARIA: Roles, states, properties, live regions
- Semantic HTML: Proper element usage, document structure
- Testing: Automated and manual accessibility testing
- Inclusive Design: Color contrast, text sizing, motor accessibility
Responsibilities
-
Accessibility Audits
- Conduct WCAG compliance reviews
- Identify accessibility barriers
- Prioritize issues by severity
- Create remediation plans
-
Implementation
- Write accessible markup
- Implement keyboard navigation
- Add proper ARIA attributes
- Ensure screen reader compatibility
-
Testing
- Test with screen readers
- Verify keyboard navigation
- Check color contrast
- Validate HTML semantics
-
Education
- Document accessibility patterns
- Create accessibility guidelines
- Train teams on best practices
- Advocate for inclusive design
WCAG 2.1 Level AA Requirements
1. Perceivable
Text Alternatives (1.1)
// ❌ Bad: Missing alt text
<img src="/product.jpg" />
// ✅ Good: Descriptive alt text
<img src="/product.jpg" alt="Blue cotton t-shirt with round neck" />
// ✅ Decorative images
<img src="/decoration.png" alt="" role="presentation" />
// ✅ Complex images
<img
src="/chart.png"
alt="Bar chart showing 40% increase in sales from Q1 to Q2"
aria-describedby="chart-details"
/>
<div id="chart-details">
Detailed description of chart data...
</div>
Time-Based Media (1.2)
// Video with captions and transcript
<video controls>
<source src="/video.mp4" type="video/mp4" />
<track kind="captions" src="/captions.vtt" srclang="en" label="English" />
</video>
<details>
<summary>Video Transcript</summary>
<p>Full text transcript of video content...</p>
</details>
Adaptable Content (1.3)
// ✅ Semantic HTML structure
<header>
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
</ul>
</nav>
</header>
<main>
<article>
<h1>Article Title</h1>
<p>Content...</p>
</article>
</main>
<aside aria-label="Related links">
<h2>Related Articles</h2>
</aside>
<footer>
<p>© 2025 Company</p>
</footer>
Distinguishable Content (1.4)
// Color contrast ratios
// Normal text: 4.5:1 minimum
// Large text (18pt+): 3:1 minimum
// ❌ Bad: Color only to convey meaning
<p style={{ color: 'red' }}>Error</p>
// ✅ Good: Color + icon + text
<div className="error" role="alert">
<svg aria-hidden="true">❌</svg>
<span>Error: Please fix the following issues</span>
</div>
// ✅ Resize text up to 200%
<html lang="en">
<body style={{ fontSize: '16px' }}> {/* Use relative units */}
2. Operable
Keyboard Accessible (2.1)
// ❌ Bad: Click-only interaction
<div onClick={handleClick}>Click me</div>
// ✅ Good: Keyboard accessible
<button onClick={handleClick}>Click me</button>
// ✅ Custom keyboard interactions
<div
role="button"
tabIndex={0}
onClick={handleClick}
onKeyDown={(e) => {
if (e.key === 'Enter' || e.key === ' ') {
e.preventDefault()
handleClick()
}
}}
>
Custom button
</div>
// ✅ Skip navigation link
<a href="#main-content" className="skip-link">
Skip to main content
</a>
<main id="main-content">...</main>
Enough Time (2.2)
// ✅ Warning before timeout
function SessionTimeout() {
const [showWarning, setShowWarning] = useState(false)
useEffect(() => {
// Show warning 2 minutes before timeout
const warningTimer = setTimeout(() => {
setShowWarning(true)
}, 28 * 60 * 1000) // 28 minutes
return () => clearTimeout(warningTimer)
}, [])
return showWarning && (
<div role="alert">
<p>Your session will expire in 2 minutes.</p>
<button onClick={extendSession}>Extend Session</button>
</div>
)
}
Seizures and Physical Reactions (2.3)
// ❌ Bad: Flashing content without warning
<div className="flashing-animation">...</div>
// ✅ Good: Respect prefers-reduced-motion
<div className={`
${!reducedMotion && 'animate-fade-in'}
`}>
Content
</div>
// CSS
@media (prefers-reduced-motion: reduce) {
* {
animation-duration: 0.01ms !important;
transition-duration: 0.01ms !important;
}
}
Navigable (2.4)
// ✅ Descriptive page titles
<title>User Profile - Settings | YourApp</title>
// ✅ Descriptive headings
<h1>Account Settings</h1>
<h2>Profile Information</h2>
<h3>Contact Details</h3>
// ✅ Focus visible
button:focus-visible {
outline: 2px solid #0066cc;
outline-offset: 2px;
}
// ✅ Descriptive links
// ❌ Bad
<a href="/more">Click here</a>
// ✅ Good
<a href="/more">Read more about accessibility</a>
Input Modalities (2.5)
// ✅ Target size at least 44x44 pixels
<button className="min-w-[44px] min-h-[44px]">
<span className="sr-only">Submit</span>
✓
</button>
// ✅ Cancel pointer actions
<button
onPointerDown={handlePointerDown}
onPointerUp={handlePointerUp}
onPointerCancel={handleCancel}
>
Draggable
</button>
3. Understandable
Readable (3.1)
// ✅ Language of page
<html lang="en">
// ✅ Language of parts
<p>This is English text</p>
<p lang="es">Este es texto en español</p>
Predictable (3.2)
// ❌ Bad: Focus causes context change
<input onFocus={navigateAway} /> // Don't do this!
// ✅ Good: User-initiated changes
<button onClick={navigateAway}>Continue</button>
// ✅ Consistent navigation
<nav aria-label="Main navigation">
{/* Same navigation on all pages */}
</nav>
Input Assistance (3.3)
// ✅ Error identification and suggestions
<form>
<label htmlFor="email">
Email
<input
id="email"
type="email"
aria-invalid={emailError ? 'true' : 'false'}
aria-describedby={emailError ? 'email-error' : undefined}
/>
</label>
{emailError && (
<div id="email-error" role="alert" className="error">
Please enter a valid email address (e.g., user@example.com)
</div>
)}
{/* Labels and instructions */}
<label htmlFor="password">
Password
<span className="hint">Must be at least 8 characters</span>
<input
id="password"
type="password"
aria-describedby="password-requirements"
/>
</label>
<div id="password-requirements" className="text-sm">
Password must contain at least one number and one special character
</div>
</form>
4. Robust
Compatible (4.1)
// ✅ Valid HTML
<button type="button" aria-label="Close">×</button>
// ✅ Name, Role, Value
<div
role="checkbox"
aria-checked={checked}
aria-labelledby="label-id"
tabIndex={0}
onKeyDown={handleKeyDown}
onClick={handleClick}
>
<span id="label-id">Enable notifications</span>
</div>
// ✅ Status messages
<div role="status" aria-live="polite" aria-atomic="true">
{message}
</div>
Common Accessibility Patterns
Modal Dialog
function Modal({ isOpen, onClose, title, children }) {
const modalRef = useRef<HTMLDivElement>(null)
useEffect(() => {
if (isOpen) {
// Focus trap
const focusableElements = modalRef.current?.querySelectorAll(
'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])'
)
const firstElement = focusableElements?.[0] as HTMLElement
firstElement?.focus()
// Prevent background scroll
document.body.style.overflow = 'hidden'
return () => {
document.body.style.overflow = ''
}
}
}, [isOpen])
if (!isOpen) return null
return (
<div
className="modal-overlay"
onClick={onClose}
role="dialog"
aria-modal="true"
aria-labelledby="modal-title"
ref={modalRef}
>
<div className="modal-content" onClick={(e) => e.stopPropagation()}>
<h2 id="modal-title">{title}</h2>
{children}
<button onClick={onClose} aria-label="Close dialog">
×
</button>
</div>
</div>
)
}
Accordion
function Accordion({ items }) {
const [openIndex, setOpenIndex] = useState<number | null>(null)
return (
<div className="accordion">
{items.map((item, index) => (
<div key={index} className="accordion-item">
<h3>
<button
id={`accordion-button-${index}`}
aria-expanded={openIndex === index}
aria-controls={`accordion-panel-${index}`}
onClick={() => setOpenIndex(openIndex === index ? null : index)}
>
{item.title}
</button>
</h3>
<div
id={`accordion-panel-${index}`}
role="region"
aria-labelledby={`accordion-button-${index}`}
hidden={openIndex !== index}
>
{item.content}
</div>
</div>
))}
</div>
)
}
Data Table
<table>
<caption>User Statistics for Q1 2025</caption>
<thead>
<tr>
<th scope="col">Month</th>
<th scope="col">New Users</th>
<th scope="col">Active Users</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">January</th>
<td>1,234</td>
<td>5,678</td>
</tr>
</tbody>
</table>
Live Region (Toast Notifications)
function Toast({ message, type }) {
return (
<div
role="status"
aria-live="polite"
aria-atomic="true"
className={`toast toast-${type}`}
>
{message}
</div>
)
}
// For urgent alerts
<div role="alert" aria-live="assertive">
Critical error occurred!
</div>
Accessibility Testing
Automated Testing
# Install axe-core
npm install --save-dev @axe-core/react
# In development
if (process.env.NODE_ENV !== 'production') {
import('@axe-core/react').then(axe => {
axe.default(React, ReactDOM, 1000)
})
}
Manual Testing Checklist
## Accessibility Test Plan
### Keyboard Navigation
- [ ] All interactive elements reachable by Tab
- [ ] Logical tab order
- [ ] Focus visible on all elements
- [ ] No keyboard traps
- [ ] Skip navigation link works
### Screen Reader
- [ ] Test with VoiceOver (Mac/iOS)
- [ ] Test with NVDA (Windows)
- [ ] All content read in logical order
- [ ] Images have appropriate alt text
- [ ] Form labels announced correctly
- [ ] Error messages announced
- [ ] Dynamic content announced
### Visual
- [ ] Text resizable to 200% without loss of content
- [ ] Color contrast meets WCAG AA (4.5:1 normal, 3:1 large)
- [ ] Content doesn't rely on color alone
- [ ] No flashing content (< 3 flashes per second)
### Forms
- [ ] All inputs have labels
- [ ] Error identification clear
- [ ] Error suggestions provided
- [ ] Required fields indicated
### Structure
- [ ] Proper heading hierarchy (h1 → h2 → h3)
- [ ] Landmarks used (header, nav, main, aside, footer)
- [ ] Valid HTML
- [ ] Language attribute set
Tools and Resources
Testing Tools
- axe DevTools: Browser extension for automated testing
- WAVE: Web accessibility evaluation tool
- Lighthouse: Accessibility audit in Chrome DevTools
- NVDA: Free screen reader (Windows)
- VoiceOver: Built-in screen reader (Mac/iOS)
Development Tools
// Screen reader only text
<span className="sr-only">
Additional context for screen readers
</span>
// CSS
.sr-only {
position: absolute;
width: 1px;
height: 1px;
padding: 0;
margin: -1px;
overflow: hidden;
clip: rect(0, 0, 0, 0);
white-space: nowrap;
border: 0;
}
When to Activate
Activate this skill when the task involves:
- Accessibility improvements and audits
- WCAG compliance implementation
- Screen reader optimization
- Keyboard navigation fixes
- ARIA attribute implementation
- Semantic HTML improvements
- Color contrast fixes
- Accessible form creation
- Inclusive design patterns
- Accessibility testing
- A11y documentation
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/accessibility-specialist-mmio70hm/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/accessibility-specialist-mmio70hm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/accessibility-specialist-mmio70hm/download' --output '.skill-downloads/accessibility-specialist-mmio70hm/SKILL.md.part' && mv '.skill-downloads/accessibility-specialist-mmio70hm/SKILL.md.part' '.skill-downloads/accessibility-specialist-mmio70hm/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/accessibility-specialist-mmio70hm/SKILL.md' && test -s '.skill-downloads/accessibility-specialist-mmio70hm/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/accessibility-specialist' && cp -R '.skill-downloads/accessibility-specialist-mmio70hm' '.claude/skills/accessibility-specialist'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/accessibility-specialist-mmio70hm'openskills read 'accessibility-specialist-mmio70hm'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/accessibility-specialist-mmio70hm/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.