- Home
- Skills
- UX & UI Design
- accessibility reviewer
Works with the AI Agents you already use
accessibility reviewer
Audit UI components and markup for WCAG 2.2 compliance with actionable fix recommendations.
$6
accessibility reviewer
Example session with this skill installed
- Read your context and instructions
- Compiled the accessibility reviewer
I have reviewed the provided button component for WCAG 2.1 AA compliance. The implementation relies on a generic div which lacks native interactive properties.
Accessibility Review Report
| ID | Status | Page/state/element | User impact | Severity | Evidence/reproduction | WCAG criterion | Fix | Retest |
|---|---|---|---|---|---|---|---|---|
| A11Y-01 | Confirmed | Submit Button | Keyboard users cannot trigger action | Critical | Component uses a div; not in tab order; no KeyDown listener | 2.1.1 (A) | Change div to <button> or add tabindex="0" and keyboard listeners | Attempt to trigger button using 'Enter' and 'Space' |
| A11Y-02 | Confirmed | Submit Button | Screen reader users miss role | Major | Role="button" is present but lacks focusable state | 4.1.2 (A) | Use native <button> element | Verify screen reader announces "Submit, button" |
| A11Y-03 | Potential | Submit Button | Low vision users may struggle with contrast | Minor | Blue #0000FF and White #FFFFFF is 8.59:1 (Passes AA) | 1.4.3 (AA) | None required for AA | Verify contrast in high-contrast mode |
Remediation Snippet
// Problematic Code
<div role="button" onclick="submit()">Submit</div>
// Corrected Code
<button type="button" onClick={submit}>Submit</button>
Manual Test Scenario
Keyboard Test: Use the Tab key to navigate the page. Ensure the focus ring lands on the "Submit" button. Press 'Enter' to trigger the function.
2.
Screen Reader Test: Navigate to the element using a screen reader (NVDA/VoiceOver). Confirm it is announced as a "button" and the label "Submit" is read clearly.
Next steps
- Replace the
divwith a nativebuttonelement to inherit global attributes. - Verify the focus indicator is visible when the button is focused.
- Integrate an automated linter to catch non-semantic button usage in the future.
Connects securely to your tools. The creator never sees your data.
About this skill
Accessibility debt and WCAG violations often go unnoticed until a legal audit or a blocked user report. This skill provides a systematic review of UI components and markup to catch barriers before they reach production.
What it does
- Analyze markup Inspects HTML or JSX for semantic roles, names, values, and heading hierarchies.
- Identify barriers Detects keyboard focus traps, illogical tab orders, and missing ARIA properties.
- Contrast verification Checks text and non-text contrast against AA or AAA thresholds.
- Screen reader simulation Predicts AT announcements for dynamic content and live regions.
- Actionable remediation Provides specific code fixes and step-by-step retest scenarios.
How it works
- Define scope Identify the specific pages, states, and user flows requiring audit.
- Execute inspection Review semantic roles, landmarks, and interaction feedback.
- Map violations Align findings to specific WCAG 2.2 criteria and conformance levels.
- Generate report Produce a structured table including severity, evidence, and code fixes.
Frameworks & tools
Works with any web-based stack including React, Vue, Angular, and plain HTML. It references WCAG 2.1/2.2 success criteria and supports evaluation for screen readers and keyboard-only navigation.
Why this beats prompting it yourself
Generic prompts often miss interactive states like focus management in dialogs or dynamic live region updates. This skill follows a rigorous 7-step procedure that forces a distinction between confirmed failures and potential barriers, ensuring you don't receive false conformance claims from automated-only checks.
Use cases
- Component Audits Reviewing a new UI library component before it is merged into the design system.
- Release Checks Running a final accessibility pass on a critical user flow like checkout or registration.
- Bug Remediation Investigating reported accessibility issues and generating reproducible fix scenarios.
- Compliance Mapping Documenting how specific interface elements meet (or fail) WCAG success criteria.
Known limitations
Cannot verify DOM or runtime behavior from visual-only artifacts. It does not provide legal conclusions or absolute conformance guarantees.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for UX & UI Design.
Cannot verify DOM or runtime behavior from visual-only artifacts. Requires human review to establish WCAG conformance. Does not provide legal conclusions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 days ago