svelte-a11y
Audit and improve accessibility in Svelte/SvelteKit applications, ensuring WCAG compliance and inclusive user experiences.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 48904c6eaa6555cf… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
svelte-a11y.md
/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:
-
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
-
Common Issues & Fixes:
Component Accessibility:
<!-- Bad --> <div onclick={handleClick}>Click me</div> <!-- Good --> <button onclick={handleClick} aria-label="Action description"> Click me </button>Form Accessibility:
<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} -
Navigation & Focus:
// 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(); } } -
ARIA Implementation:
- Use semantic HTML first
- Add ARIA labels for clarity
- Implement live regions
- Manage focus properly
- Announce dynamic changes
-
Testing Tools:
- Svelte a11y warnings
- axe-core integration
- Pa11y CI setup
- Screen reader testing
- Keyboard navigation testing
-
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
Files
1- svelte-a11y.md
48f570a6482.5 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from davila7/claude-code-templates8
Execute GitHub Actions locally using act
Implement secure user authentication system with chosen method and security best practices
Generate and maintain project changelog with Keep a Changelog format
Setup comprehensive mutation testing with framework selection and CI integration
Add and configure new package to workspace with proper structure and dependencies
Setup comprehensive application performance monitoring with metrics, alerting, and observability
Implement property-based testing with framework selection and invariant identification
Add entry to project changelog following Keep a Changelog format
Related frontend skillsscan passed
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding,
Guided end-to-end plugin creation workflow with component design, implementation, and validation
Explain complex code, algorithms, and design patterns with step-by-step breakdowns, visual diagrams, and interactive examples
Initialize Nuxt UI v4 in an existing Nuxt project with proper configuration