svelte-a11y — Claude Code command for Svelte accessibility
Audit Svelte and SvelteKit interfaces for accessibility issues and get suggested fixes. Use it to review forms, keyboard navigation, focus, and ARIA.
npx claude-code-templates@latest --command svelte/svelte-a11yWhat svelte-a11y does
The command guides Claude Code through checks for WCAG 2.1 AA/AAA, keyboard access, color contrast, and ARIA. Its audit instructions also call for screen reader checks and automated tests. Automated results still need hands-on review; the command includes both approaches.
Examples cover semantic interactive elements, labelled form fields, error announcements, skip links, and focus management. The listed testing options include Svelte a11y warnings, axe-core integration, and Pa11y CI setup. The command can also help create an accessibility test suite and a WCAG compliance report.
What it helps with
- audit a Svelte interface for accessibility issues
- replace inaccessible controls with semantic markup
- check form labels and error announcements
- review keyboard navigation and focus handling
- inspect color contrast and ARIA usage
Example prompts for the agent
- Audit my Svelte app for accessibility issues and report the WCAG findings.
- Check the checkout form for keyboard access, field labels, and announced errors.
- Review focus handling and ARIA in my SvelteKit components.
How to install svelte-a11y
1claude-code-templates
npx claude-code-templates@latest --command svelte/svelte-a11y2Manually: put the files in place
.claude/commands/svelte-a11y.mdCall it with /svelte-a11y. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/svelte-a11y.mdCall it with /prompts:svelte-a11y. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/svelte-a11y.prompt.mdManually: put the files in place
.gemini/commands/svelte-a11y.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about svelte-a11y
How do I install svelte-a11y in Claude Code?
Run npx claude-code-templates@latest --command svelte/svelte-a11y. The command file is .claude/commands/svelte-a11y.md.
What does svelte-a11y do?
It guides Claude Code through accessibility checks and suggested fixes for Svelte and SvelteKit apps, including forms, keyboard access, focus, and ARIA.
Which accessibility testing tools does it cover?
The instructions include Svelte a11y warnings, axe-core integration, and Pa11y CI setup. They also call for screen reader and keyboard testing.
Source text
svelte-a11y.md · MIT
---
description: "Audit and improve accessibility in Svelte/SvelteKit applications, ensuring WCAG compliance and inclusive user experiences."
---
# /svelte:a11y
Audit and improve accessibility in Svelte/SvelteKit applications, ensuring WCAG compliance and inclusive user experiences.
## Instructions
You are acting as the Svelte Development Agent focused on accessibility. When improving accessibility:
1. **Accessibility Audit**:
- Run automated accessibility tests
- Check WCAG 2.1 AA/AAA compliance
- Test with screen readers
- Verify keyboard navigation
- Analyze color contrast
- Review ARIA usage
2. **Common Issues & Fixes**:
**Component Accessibility**:
```svelte
<!-- Bad -->
<div onclick={handleClick}>Click me</div>
<!-- Good -->
<button onclick={handleClick} aria-label="Action description">
Click me
</button>
```
**Form Accessibility**:
```svelte
<label for="email">Email Address</label>
<input
id="email"
type="email"
required
aria-describedby="email-error"
/>
{#if errors.email}
<span id="email-error" role="alert">
{errors.email}
</span>
{/if}
```
3. **Navigation & Focus**:
```javascript
// Skip links
<a href="#main" class="skip-link">Skip to main content</a>
// Focus management
onMount(() => {
if (shouldFocus) {
element.focus();
}
});
// Keyboard navigation
function handleKeydown(event) {
if (event.key === 'Escape') {
closeModal();
}
}
```
4. **ARIA Implementation**:
- Use semantic HTML first
- Add ARIA labels for clarity
- Implement live regions
- Manage focus properly
- Announce dynamic changes
5. **Testing Tools**:
- Svelte a11y warnings
- axe-core integration
- Pa11y CI setup
- Screen reader testing
- Keyboard navigation testing
6. **Accessibility Checklist**:
- [ ] All interactive elements keyboard accessible
- [ ] Proper heading hierarchy
- [ ] Images have alt text
- [ ] Color contrast meets standards
- [ ] Forms have proper labels
- [ ] Error messages announced
- [ ] Focus indicators visible
- [ ] Page has unique title
- [ ] Landmarks properly used
- [ ] Animations respect prefers-reduced-motion
## Example Usage
User: "Audit my e-commerce site for accessibility issues"
Assistant will:
- Run automated accessibility scan
- Check product cards for proper markup
- Verify cart keyboard navigation
- Test checkout form accessibility
- Review color contrast on CTAs
- Add ARIA labels where needed
- Implement focus management
- Create accessibility test suite
- Provide WCAG compliance report
© davila7 · MIT · davila7/claude-code-templates