reviewing-accessibility

Review UI code against WCAG AA criteria for accessibility compliance.

1|Updated Apr 22, 2022
One-click install
npx skills add https://github.com/eventua11y/eventua11y.com --skill reviewing-accessibility-eventua11y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-accessibility
Source: https://github.com/eventua11y/eventua11y.com/tree/main/.agents/skills/reviewing-accessibility
Command: npx skills add https://github.com/eventua11y/eventua11y.com --skill reviewing-accessibility-eventua11y

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining WCAG AA compliance in UI code, providing a detailed review process to identify accessibility issues before they impact users.

Core Features & Use Cases

  • Code Review for Accessibility: Analyzes implemented UI code against WCAG Level AA criteria.
  • Comprehensive Checklist: Includes checks for semantic HTML, keyboard navigation, labels and names, ARIA usage, visual standards, and forms.
  • Use Case: Before releasing a feature, run this skill to audit the codebase for accessibility compliance, ensuring that all interactive elements are accessible to users with disabilities.

Quick Start

Run the reviewing-accessibility skill on the latest commit to ensure accessibility compliance.

Frequently Asked Questions about reviewing-accessibility

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

FAQPage Schema
How do I check my UI code for WCAG AA compliance before deployment?

WCAG AA compliance is verified by performing a detailed code review against criteria covering semantic HTML, keyboard navigation, labels, ARIA usage, visual standards, and forms. This identifies accessibility issues before they impact users.

What does an accessibility code review cover for interactive elements?

An accessibility code review covers semantic HTML, keyboard navigation, labels and names, ARIA usage, visual standards, and forms. It ensures all interactive elements are accessible to users with disabilities.

Can I audit ARIA usage and semantic HTML in my codebase automatically?

You can audit ARIA usage and semantic HTML by running a comprehensive code review skill on your latest commit. It checks implemented UI code against WCAG Level AA criteria to ensure accessibility compliance.

When do I need to run an accessibility compliance check on my latest commit?

You need to run an accessibility compliance check before releasing a feature. Auditing the codebase before deployment ensures that interactive elements are accessible and WCAG AA compliant.

Does this accessibility review check keyboard navigation and visual standards?

Yes, this accessibility review checks keyboard navigation and visual standards. It analyzes implemented UI code against WCAG Level AA criteria, including forms, labels, names, and ARIA usage.

What is the best way to ensure forms are accessible to users with disabilities?

The best way to ensure forms are accessible is to run a comprehensive code review against WCAG AA criteria. This process checks forms, labels, names, and semantic HTML to identify compliance issues.