web-accessibilitylisted
Install: claude install-skill ziniman/ai-instruct
# Web Accessibility Guide
> Applies to: Any website or web app | Updated: March 2026
A practical reference for building accessible websites - covering WCAG 2.2 criteria, semantic HTML, ARIA, forms, touch, and testing.
---
## Section 0: Before You Start
Answer these questions before generating accessibility code. Each answer changes which sections apply.
**Q: Where are your users?**
Default: worldwide - EU/UK requirements (EAA, PSBAR) will be flagged as applicable throughout this guide.
Options: US only | Europe/EU | UK | Worldwide
**Q: What kind of product is this?**
Default: company/marketing website
Options: Company/marketing website | Online shop/e-commerce | Web app/SaaS | Media/video site | Document tool
**Q: Will people use this on mobile phones or tablets as well as desktop?**
Default: yes - touch target sizing and pointer accessibility sections apply.
**Q: Are you building with a component library?**
Default: none
Options: Radix UI | shadcn/ui | MUI | Chakra UI | Other | None - if a library is detected in `package.json`, note which accessibility features it handles natively so you don't duplicate them.
**Q: Do you need to comply with a specific standard for legal or contract reasons?**
Default: WCAG 2.2 AA - current best-practice baseline.
Options: WCAG 2.1 AA | WCAG 2.2 AA | Section 508 | EN 301 549 | Not sure
> **AI assistant:** Use these answers to prioritize. For EU products: apply EAA compliance notes. For mobile: apply touch target and point