- Home
- Skills
- Frontend & Web Apps
- WCAG AAA Compliance Auditor
Works with the AI Agents you already use
WCAG AAA Compliance Auditor
Audit frontend components for strict WCAG 2.1 Level AAA accessibility compliance and get line-by-line remediation code.
$15
WCAG AAA Compliance Auditor
Example session with this skill installed
Audit this React button component for WCAG 2.1 Level AAA compliance, focusing on keyboard navigation and focus states.
- Read your context and instructions
- Compiled the wcag aaa compliance
I have completed a static accessibility audit of the provided React component against WCAG 2.1 Level AAA standards.
WCAG 2.1 AAA Compliance Scorecard
| Requirement | Status | Issue Identified | Remediation |
|---|---|---|---|
| Focus Visible | FAIL | Focus ring contrast is 1.8:1 against background. | Update CSS to 3:1 minimum contrast. |
| Keyboard Nav | PASS | Tab order is logical; no traps found. | No action required. |
| Name/Role/Value | FAIL | Missing aria-label for icon-only variant. | Add descriptive aria-label prop. |
| Reflow | PASS | Responsive layout maintains structure. | No action required. |
Remediation Code
// Updated Component with AAA fixes
import React from 'react';
const PrimaryButton = ({ icon, label, onClick }) => {
return (
<button
onClick={onClick}
aria-label={label}
style={{
// AAA requirement: 3:1 focus contrast
outline: '3px solid #2563EB',
outlineOffset: '2px'
}}
className="focus:ring-offset-2 focus:ring-blue-600"
>
{icon}
</button>
);
};
export default PrimaryButton;
Next steps
- Apply the updated CSS outline properties to ensure 3:1 contrast on all interactive elements.
- Verify that
aria-live="polite"is used on the parent container if this button triggers dynamic content updates. - Run the automated evaluation suite in
evals/eval-suite.jsonto verify the fix.
Connects securely to your tools. The creator never sees your data.
About this skill
Most automated accessibility tools stop at Level AA. This skill targets the much stricter WCAG 2.1 Level AAA standards, identifying subtle failures in keyboard navigation, focus contrast, and screen reader announcements that standard linters miss. It provides a formal audit for enterprise teams who need inclusive design by default.
What it does
- Markup evaluation identifies missing ARIA attributes and semantic landmark omissions in HTML/JSX.
- Keyboard navigation audit verifies tab order, eliminates keyboard traps, and checks focus indicators.
- Contrast verification ensures focus states maintain at least a 3:1 contrast ratio against adjacent colors.
- Screen reader enforcement checks for proper
aria-liveregions to handle dynamic DOM updates. - Remediation delivery produces a compliance scorecard with specific code fixes for every identified failure.
How it works
- Submit your component code or markup for static analysis.
- The agent evaluates the structure against the WCAG 2.1 AAA compliance matrix.
- It performs a virtual walkthrough of keyboard tab sequences and focus states.
- You receive an itemized scorecard detailing violations and the exact code needed to fix them.
Frameworks & tools
This skill is optimized for modern frontend stacks including HTML5, JSX, React, and Next.js. It performs static analysis on local files without requiring external browser automation.
Why this beats prompting it yourself
Generic prompts often confuse AA and AAA requirements or provide vague "best practice" advice. This skill uses a deterministic workflow to enforce specific numeric contrast thresholds and strict ARIA roles required for Level AAA certification.
Use cases
- Auditing React component libraries for enterprise Design Systems.
- Verifying complex dynamic dashboards for screen reader compatibility.
- Hardening navigation menus to prevent keyboard traps.
- Reviewing high-contrast focus states for low-vision users.
Known limitations
This is an advisory static audit and does not perform active browser automation or manual user testing. It is restricted to analyzing files within the active project workspace.
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.
Limited to static analysis only. No browser automation or live site crawling. Workspace confined to the local project directory.
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 3 days ago
- Software
- Zero global installationorelevated privileges required.
File System Read/Write (strictly scoped to current project workspace `./`).
Permissions
Target Use Cases: - Audit this frontend component for WCAG AAA compliance. - Check keyboard accessibility and screen reader support in my React app. - Evaluate ARIA attributes on this dropdown menu.