← ClaudeAtlas

accessibility-reviewlisted

Audits a digital product against recognized accessibility standards — WCAG (the W3C Web Content Accessibility Guidelines) and IBM's accessibility requirements — and produces a prioritized findings report mapping each issue to the specific success criterion it fails, with severity and a concrete fix. Use this whenever the user wants an accessibility review, a11y audit, WCAG check, Section 508 / EN 301 549 conformance pass, or wants to know whether a screen, component, flow, PDF, or document is accessible; wants to fix contrast, keyboard, screen-reader, focus, alt-text, form-label, or ARIA problems; or asks which WCAG criterion something violates. Reach for it even when "accessibility" isn't named — any request to make a UI usable for people with disabilities, or to meet a legal accessibility requirement, qualifies.
JoaoMonteiro100/ux-design-skills · ★ 0 · Code & Development · score 72
Install: claude install-skill JoaoMonteiro100/ux-design-skills
# Accessibility Review This skill audits a product for accessibility — how well people with disabilities (visual, motor, auditory, cognitive, situational) can perceive, operate, and understand it — and writes up what to fix, tied to the standard it fails. Accessibility isn't a subjective "nice to have": it's governed by published, testable standards, and much of it is a legal requirement (ADA, Section 508 in the US, EN 301 549 / the European Accessibility Act in the EU). Grounding findings in those standards is what makes the report credible and actionable. Two honest framing points to carry into any review: - **Automated checks catch only part of it.** Tools (axe, WAVE, Lighthouse) find maybe a third of issues — mostly contrast, missing alt, missing labels. The rest (meaningful focus order, sensible reading order, whether alt text is *good*, whether an interaction is truly operable by keyboard and screen reader) needs human judgment. Say so, and don't imply a clean automated scan means "accessible." - **You often can't fully verify from a description.** Real conformance testing needs the running product, a keyboard, and a screen reader. When you only have a screenshot or a description, give your best assessment, be explicit about what you couldn't verify, and never claim conformance you didn't test. ## The standards to reference Reference these directly and by name — they're public norms, and citing them precisely is what gives the review authority. - *