fix-accessibility

Name: fix-accessibility
Availability: InStock
Author: Archetype AI

Audit and fix WCAG accessibility issues in shadcn-svelte projects.

Updated Apr 9, 2026

Search Tags:#accessibility #a11y #audit #wcag #screen-reader #aria #keyboard-navigation

Ready to run

npx skills add https://github.com/archetypeai/newton-earthquake-demo --skill fix-accessibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-accessibility
Source: https://github.com/archetypeai/newton-earthquake-demo/tree/main/.claude/skills/fix-accessibility
Command: npx skills add https://github.com/archetypeai/newton-earthquake-demo --skill fix-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and fixes accessibility issues in projects built with shadcn-svelte and the Archetype AI design system. Use when running an a11y audit, fixing WCAG violations, adding aria labels, improving keyboard navigation, fixing focus management, adding screen reader support, or when the user mentions "accessibility", "a11y", "aria", "screen reader", or "keyboard navigation".

Core Features & Use Cases

Comprehensive accessibility audits covering skip links, landmarks, heading hierarchy, ARIA attributes, and keyboard navigation.
Practical fixes that add aria labels, proper focus management, screen reader support, and accessible component patterns across Svelte-based interfaces.
Use Case: teams implementing a11y checks during code reviews or before public releases to reduce WCAG violations and improve keyboard operability.

Quick Start

Run an accessibility audit on your project and start applying fixes following the audit checklist.

Frequently Asked Questions about fix-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix WCAG violations in my web project?▼

To fix WCAG violations, run an accessibility audit to identify issues across skip links, landmarks, and ARIA attributes, then apply safe suggestions that do not alter core functionality unless necessary.

How do I improve keyboard navigation and focus management?▼

Improve keyboard navigation by applying practical fixes that enforce proper focus management and accessible component patterns, ensuring reliable operability across Svelte-based interfaces.

Can I use this to add screen reader support to shadcn-svelte?▼

Yes, you can add screen reader support to shadcn-svelte by applying targeted ARIA labels and accessible component patterns during your development or code review workflow.

What is the best way to audit a11y issues in a modern design system?▼

The best way to audit a11y issues is using a checklist-like workflow that validates heading structures, landmarks, and interaction patterns to ensure WCAG-compliant semantics.

Does applying accessibility fixes alter my core application functionality?▼

No, applying accessibility fixes does not alter core functionality unless necessary, as the skill provides safe suggestions and fallback guidance to preserve your original interactions.