- Home
- Skills
- Frontend & Web Apps
- accessibility upgrade pro
accessibility upgrade pro
Audit and remediate web accessibility issues with semantic HTML guidance and keyboard navigation plans.
$5
Works with the AI Agents you already use
accessibility upgrade pro
Example session with this skill installed
I have a custom dropdown menu built with divs that keyboard users can't open. Can you help me make it accessible?
- Read your context and instructions
- Compiled the accessibility upgrade pro
I have analyzed the custom dropdown component. The primary issues are a lack of semantic triggers, missing keyboard event listeners, and no visible focus management.
Accessibility Remediation: Custom Dropdown
| Component Part | Current State | Remediation Action | ARIA/Attribute Requirement |
|---|---|---|---|
| Trigger | div | Change to <button> | aria-haspopup="listbox", aria-expanded="false" |
| Menu Container | div | Add role="listbox" | aria-labelledby="[button-id]" |
| Menu Items | div | Add role="option" | tabindex="-1" (managed focus) |
| Focus State | None | Add :focus-visible | High-contrast outline (min 2px) |
Prioritized Fixes
- Swap Trigger to Button: Using a
divfor a trigger prevents keyboard users from discovering it via the Tab key. - Implement Keyboard Listeners: Add
EnterandSpaceto open, andArrowDown/Upto navigate items.
Manage Focus: When the menu opens, move focus to the first item. When Esc is pressed, close the menu and return focus to the trigger.
Semantic Guidance
<!-- Recommended Structure -->
<div class="dropdown-wrapper">
<button
id="menu-button"
aria-haspopup="listbox"
aria-expanded="false"
aria-controls="menu-list">
Select Option
</button>
<ul
id="menu-list"
role="listbox"
tabindex="-1"
hidden>
<li role="option" tabindex="-1">Option 1</li>
<li role="option" tabindex="-1">Option 2</li>
</ul>
</div>
Keyboard Test Plan
- Tab Navigation: Ensure the trigger button is reachable in the natural page tab order.
- Activation: Verify
SpaceandEnterkeys toggle the menu visibility. - Escape Key: Verify the
Esckey closes the menu and returns focus to the button. - List Navigation: Ensure
ArrowDownmoves focus through the options without moving the page scroll.
Next steps
- Update the HTML template to use the
<button>and<ul>tags as shown. - Add a JavaScript event listener for the
keydownevent to handle arrow key navigation. - Verify the focus outline is clearly visible in your brand colors.
Connects securely to your tools. The creator never sees your data.
About this skill
Retrofitting accessibility into an existing codebase often feels like a guessing game of ARIA roles and contrast ratios. This skill automates the audit and remediation process, turning vague requests into a prioritized implementation roadmap for WCAG-friendly interfaces.
What it does
- Semantic auditing identifies where native HTML elements should replace non-accessible custom components.
- Keyboard mapping defines logical focus order and identifies traps that break navigation for non-mouse users.
- Form remediation structures labels, error states, and recovery instructions to meet modern standards.
- Visual logic check evaluates if motion or color are being used as the sole carriers of information.
- Reflow analysis predicts how UI components will behave under browser zoom and responsive shifts.
How it works
- Submit a code snippet, a description of a user flow, or a known list of accessibility complaints.
- The agent isolates facts from assumptions to build a professional accessibility structure.
- It applies domain-specific quality gates to prioritize fixes that impact usability most.
- You receive a structured artifact containing findings, code-level fixes, and a manual testing plan.
Frameworks & tools
Works with any web stack including React, Vue, Angular, and vanilla HTML/CSS. Guidance focuses on semantic HTML, WAI-ARIA standards, and WCAG 2.1/2.2 principles.
Why this beats prompting it yourself
Generic prompts often hallucinate ARIA attributes that actually break screen readers or focus on easy visual fixes while ignoring complex keyboard traps. This skill follows a rigorous professional standard that prefers native semantics over "ARIA-first" hacks, ensuring your site remains maintainable and truly usable.
Use cases
- Auditing a legacy landing page for basic keyboard and screen reader support.
- Refactoring custom div-based buttons and menus into semantic components.
- Designing accessible form validation logic and error messaging.
- Creating a manual QA checklist for developers to verify focus states.
Known limitations
Cannot guarantee legal compliance or final WCAG certification without real-world assistive technology testing. Does not support automated color contrast checking of images.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
Cannot claim legal compliance without real-world assistive technology testing. Performance is limited by the quality of the UI descriptions or code snippets provided.
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 1 month ago
Permissions
No special permissions declared or detected