accessibility-audit

Validate web accessibility compliance with WCAG 2.1 AA standards.

2|Updated Apr 9, 2025
One-click install
npx skills add https://github.com/PP-Namias/Portfolio --skill accessibility-audit-pp-namias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/PP-Namias/Portfolio/tree/main/.agents/skills/accessibility-audit
Command: npx skills add https://github.com/PP-Namias/Portfolio --skill accessibility-audit-pp-namias

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining accessibility standards in web design, specifically ensuring compliance with WCAG 2.1 AA guidelines.

Core Features & Use Cases

  • Semantic HTML Validation: Checks for proper use of semantic HTML tags for accessibility.
  • Keyboard Navigation: Ensures interactive elements are operable via keyboard.
  • Color Contrast Analysis: Validates color contrast ratios for readability.
  • Screen Reader Compatibility: Tests the site's compatibility with screen readers.
  • Use Case: Before deploying a new feature or change, use this Skill to ensure it meets accessibility standards, reducing the risk of legal action and improving user experience.

Quick Start

Run the accessibility-audit skill to scan and fix accessibility issues across your portfolio.

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 website for WCAG 2.1 AA compliance?

To check WCAG 2.1 AA compliance, run an accessibility audit to validate semantic HTML, keyboard navigation, color contrast ratios, screen reader compatibility, and focus management. Manual review is required to remediate identified issues.

What does an accessibility audit test for in web development?

An accessibility audit tests web development elements against WCAG 2.1 AA standards. It specifically validates semantic HTML tags, keyboard operability, color contrast ratios, focus management, and screen reader compatibility.

Does WCAG 2.1 AA compliance require manual review after automated testing?

WCAG 2.1 AA compliance requires manual review and remediation after automated testing. While automated checks identify semantic HTML and color contrast issues, manual validation is needed to ensure proper focus management and screen reader compatibility.

What's the best way to ensure keyboard navigation meets accessibility standards?

The best way to ensure keyboard navigation meets accessibility standards is to run an audit validating that interactive elements are fully operable via keyboard. This verifies WCAG 2.1 AA compliance and identifies focus management issues for remediation.

When do I need to run an accessibility audit before deploying new features?

You need to run an accessibility audit before deploying any new feature or change to ensure it meets WCAG 2.1 AA standards. This reduces legal risks and improves user experience by catching semantic HTML and color contrast issues early.

Why does my web application fail screen reader compatibility checks?

Web applications fail screen reader compatibility checks due to improper semantic HTML, missing focus management, or insufficient color contrast. Running a WCAG 2.1 AA accessibility audit identifies these specific areas for manual remediation.