accessibility-expert

Name: accessibility-expert
Availability: InStock
Author: ripgraphics

Diagnose web accessibility violations and suggest WCAG 2.1/2.2 fixes.

Updated Apr 23, 2025

Search Tags:#accessibility #a11y #screen reader #keyboard navigation #compliance #wcag #aria

Ready to run

npx skills add https://github.com/ripgraphics/authorsinfo --skill accessibility-expert-ripgraphics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-expert
Source: https://github.com/ripgraphics/authorsinfo/tree/main/.cursor/skills/accessibility-expert
Command: npx skills add https://github.com/ripgraphics/authorsinfo --skill accessibility-expert-ripgraphics

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses and resolves web accessibility issues, ensuring digital content is usable by everyone, including people with disabilities.

Core Features & Use Cases

WCAG Compliance: Audits and fixes websites against WCAG 2.1/2.2 standards.
ARIA Implementation: Corrects ARIA roles, states, and properties for better screen reader support.
Keyboard Navigation: Ensures all interactive elements are navigable via keyboard.
Screen Reader Optimization: Improves content structure and announcements for assistive technologies.
Use Case: A developer has received a report of accessibility violations on their e-commerce site, including poor color contrast and unlabelled form fields. They use this Skill to identify, prioritize, and fix these issues before launch.

Quick Start

Analyze the current webpage for accessibility violations and suggest fixes.

Frequently Asked Questions about accessibility-expert

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

FAQPage Schema

How do I fix WCAG compliance violations on my website?▼

To fix WCAG compliance violations, audit web pages against WCAG 2.1 and 2.2 standards to diagnose issues like poor color contrast and unlabelled form fields, then apply targeted solutions to resolve usability barriers.

What is the correct way to implement WAI-ARIA for screen reader optimization?▼

WAI-ARIA implementation requires correcting ARIA roles, states, and properties to improve content structure and announcements, ensuring assistive technologies accurately interpret interactive elements and dynamic updates for screen reader users.

How do I ensure keyboard navigation works for all interactive elements?▼

Ensuring keyboard navigation involves auditing web content to verify that all interactive elements are fully navigable via keyboard, diagnosing focus issues, and applying fixes to meet accessibility standards for diverse user needs.

Does this identify ARIA errors and usability problems for e-commerce sites?▼

Yes, it diagnoses ARIA errors and usability problems for e-commerce sites by evaluating code against accessibility standards, identifying violations, and offering prioritized solutions to resolve barriers before site launch.

What are common limitations when manually testing web accessibility?▼

Manual web accessibility testing limitations include missing complex ARIA implementation errors and subtle keyboard navigation barriers, which automated auditing against WCAG 2.1/2.2 standards can help diagnose and prioritize for resolution.