Accessibility review
Skill yigityildiz0/universal-ai-skill-library/skills/common/accessibility-review
531 searchable AI Agent Skills for Claude Code, OpenAI Codex, and OpenCode — EN/TR catalog, platform and risk notes, direct ZIPs, and curated bundles.
npx -y skills add yigityildiz0/universal-ai-skill-library --skill accessibility-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Audit a web, mobile, desktop, document, or product flow for practical accessibility issues using current WCAG 2.2 AA-oriented checks, code, screenshots, and interaction evidence. Use for accessibility review, a11y audit, WCAG review, keyboard navigation, screen-reader issues, contrast, or inclusive UX.
SKILL.md
1.3 KB, as published. Nobody here has run it
Accessibility Review
Review the actual experience, not just a checklist.
Evidence-first workflow
- Define the surface, users, platforms, assistive technology assumptions, and evidence available.
- Review semantic structure, names/roles/states, keyboard path, focus order/visibility, forms/errors, contrast, zoom/reflow, motion, media, dynamic updates, and touch targets as applicable.
- Test representative happy, error, empty, loading, and modal/overlay states.
- Classify findings by user impact, reproducibility, relevant criterion, evidence, and pragmatic fix direction.
- Retest after changes; a screenshot never proves keyboard or screen-reader behavior alone.
Guardrails
- Use current WCAG 2.2 guidance when standards mapping matters; do not claim certification.
- Do not rely on automated scans as proof of accessibility.
- Preserve user preferences such as reduced motion, zoom, contrast, and input method.