skills.rest
SAP
SAPOFFICIAL
Explore all skills by this author →
Website𝕏@SAPOpenSourceGitHub

a11y-audit

Audit UI components for WCAG AA accessibility compliance.

294|147|Updated May 27, 2018
Search Tags:#accessibility#a11y#audit#wcag#semantic-html#aria#keyboard-navigation
One-click install
npx skills add https://github.com/SAP/fundamental-ngx --skill a11y-audit-sap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/SAP/fundamental-ngx/tree/main/.claude/skills/a11y-audit
Command: npx skills add https://github.com/SAP/fundamental-ngx --skill a11y-audit-sap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit teams and developers by evaluating a component and its usage against WCAG AA accessibility criteria to ensure inclusive design.

Core Features & Use Cases

  • Semantic HTML checks ensure native elements are used where appropriate.
  • ARIA & Keyboard checks verify proper ARIA attributes, roles, focus management, and keyboard navigation.
  • Documentation validation ensures component examples and docs demonstrate accessible usage patterns.
  • Use Case: Before releasing a new UI component, run this audit to catch accessibility issues in implementation and documentation, reducing post-release fixes.

Quick Start

Audit the component at the provided path for WCAG AA compliance.

Frequently Asked Questions about a11y-audit

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

FAQPage Schema
How do I audit UI components for WCAG AA compliance?▼

You can audit UI components for WCAG AA compliance by validating HTML structure, ARIA usage, and keyboard operability, which generates a structured report detailing screen reader issues and specific remediation guidance.

What is included in an accessibility audit for semantic HTML and ARIA?▼

An accessibility audit for semantic HTML and ARIA verifies native element usage, validates ARIA roles and attributes, checks keyboard navigation, and ensures component documentation demonstrates accessible usage patterns.

Can I validate keyboard navigation and focus management in component documentation?▼

Yes, you can validate keyboard navigation and focus management by auditing component documentation examples to ensure they demonstrate accessible usage patterns and proper keyboard operability according to WCAG AA criteria.

When do I need to run a WCAG AA accessibility audit?▼

You should run a WCAG AA accessibility audit before releasing a new UI component to catch accessibility issues in implementation and documentation, ensuring inclusive design and reducing post-release fixes.

Does this accessibility audit check color contrast and screen reader issues?▼

Yes, this accessibility audit checks color contrast and screen reader issues by validating HTML structure and ARIA usage, identifying operability problems, and providing structured remediation guidance for WCAG AA compliance.

Related Skills

Explore More Legal & Compliance Skills→
TalonT-OrgTalonT-Org
5

verify-diag

Validate architecture diagrams against source code for component and connection accuracy.

Official
Advanced
DexploarerDexploarer
6

a11y-annotation-generator

Add ARIA labels, roles, and alt text to HTML, JSX, and Vue templates.

Community
Intermediate
HDeiblerHDeibler
6

accessibility-operable

Review user interfaces for keyboard operability and focus management.

Community
Advanced
xobotyixobotyi
19

accessibility

Enforce WCAG 2.2 AA compliance in HTML, CSS, and JavaScript.

Community
Intermediate