skills.rest
jonnabio
jonnabioCOMMUNITY
Explore all skills by this author →
𝕏@jonnabioGitHub

accessibility-audit

Audits frontend interfaces for WCAP 2.1 AA compliance and accessibility best practices.

6|3|Updated Jan 29, 2026
Search Tags:#accessibility#keyboard navigation#ARIA#WCAG#HTML#semantics
One-click install
npx skills add https://github.com/jonnabio/ace-framework --skill accessibility-audit-jonnabio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/jonnabio/ace-framework/tree/main/.ace/skills/accessibility-audit
Command: npx skills add https://github.com/jonnabio/ace-framework --skill accessibility-audit-jonnabio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps ensure that frontend interfaces meet WCAG standards, making them accessible to all users.

Core Features & Use Cases

  • WCAG Compliance: Audits interfaces for adherence to WCAG 2.1 AA standards.
  • Accessibility Best Practices: Provides guidelines for semantic HTML and ARIA attributes.
  • Keyboard Navigation: Checks for focusable elements and keyboard traps.
  • Visual Constraints: Ensures proper color contrast and alt text for images.
  • Use Case: When developing a new web application, use this Skill to ensure it is accessible to users with disabilities.

Quick Start

Apply the accessibility-audit skill to the 'web-app' project.

Frequently Asked Questions about accessibility-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my web application for WCAG 2.1 AA compliance?▼

You can check WCAG 2.1 AA compliance by auditing frontend interfaces to validate semantic HTML, ARIA attributes, keyboard navigation, and visual constraints like color contrast. This ensures your web application meets accessibility standards for users with disabilities.

What is the best way to test keyboard navigation and focusable elements for accessibility?▼

Testing keyboard navigation involves auditing your interface for focusable elements and detecting keyboard traps. This validates that users can navigate your web application effectively without requiring a mouse.

How do I validate ARIA attributes and semantic HTML structure for accessibility?▼

Validating ARIA attributes and semantic HTML requires running an accessibility audit on your UI components. This checks frontend code against best practices so screen readers and assistive technologies interpret elements correctly.

Can I use an automated accessibility audit to check color contrast and alt text?▼

Yes, an automated accessibility audit checks visual constraints by ensuring proper color contrast ratios and verifying alt text for images. This helps frontend interfaces adhere to WCAG standards efficiently.

Do I need to configure UI components before testing for accessibility best practices?▼

Yes, testing requires proper configuration of WCAG requirements and UI components beforehand. Configuring frontend interfaces allows the accessibility audit to accurately validate semantics, keyboard navigation, and visual constraints.

Why does my web application fail WCAG compliance even with correct semantic HTML?▼

Your web application may fail WCAG compliance if visual constraints like color contrast or keyboard navigation traps exist despite correct semantic HTML. A full accessibility audit identifies missing ARIA attributes or focusable element issues.

Related Skills

Explore More Software Engineering Skills→
timsvoicetimsvoice

specimin-ui-accessibility

Audit and fix generated UI code for WCAG 2.1 AA compliance.

Community
Advanced
mauriciodelriomauriciodelrio
3

a11y-rules

Audit React and Next.js components for WCAG 2.2 AA accessibility violations.

Community
Intermediate
benswiftbenswift
26

frontend-web-engineer

Develops accessible, responsive HTML/CSS/JavaScript interfaces with Playwright-based testing.

Community
Intermediate
a8cteam51a8cteam51
8

a11y

Audit live websites against WCAG 2.2 Level AA using Playwright browser automation.

Official
Advanced