accessibility-auditor

Audit WCAG 2.2 AA conformance in Expo and web apps with manual screen-reader tests.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill accessibility-auditor-coreymaypray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/coreymaypray/sloth-skill-tree/tree/main/plugins/maycrest-ops/skills/accessibility-auditor
Command: npx skills add https://github.com/coreymaypray/sloth-skill-tree --skill accessibility-auditor-coreymaypray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Digital products frequently meet automated accessibility checks but still present real usability barriers for screen-reader users and keyboard-only navigation. This Skill delivers expert auditing that combines WCAG 2.2 AA criteria with hands-on testing to identify and fix practical accessibility barriers.

Core Features & Use Cases

  • WCAG 2.2 AA compliance evaluation across mobile (Expo/React Native) and web previews
  • Manual screen-reader walkthroughs (VoiceOver, TalkBack) and keyboard navigation testing
  • Focus management, ARIA validation, and dynamic content accessibility checks
  • Actionable remediation guidance with concrete code examples and prioritization

Quick Start

Run a comprehensive accessibility audit on Expo mobile screens and web previews using automated checks and manual screen-reader testing to generate actionable fixes.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema
How do I audit React Native Expo screens for WCAG 2.2 AA accessibility compliance?

Audit React Native Expo screens for WCAG 2.2 AA accessibility by evaluating accessibilityLabel, accessibilityRole, color contrast, and focus management, then performing manual screen-reader walkthroughs using VoiceOver and TalkBack to identify real usability barriers.

Why does my web app pass automated accessibility checks but still fail screen-reader navigation?

Automated accessibility checks often miss dynamic content updates, ARIA validation gaps, and focus management errors that break screen-reader navigation, requiring manual keyboard testing and hands-on walkthroughs to uncover real usability barriers.

How do I fix color contrast and ARIA issues found during an accessibility audit?

Fix color contrast and ARIA issues by following actionable remediation guidance with concrete code-level examples and prioritization, ensuring dynamic content updates and focus management meet WCAG 2.2 AA conformance criteria.

Can I use axe-core and Lighthouse for manual keyboard navigation testing in mobile apps?

While axe-core and Lighthouse satisfy automated baseline checks for web previews, manual keyboard navigation and screen-reader testing are required across Expo React Native mobile screens to identify practical accessibility barriers automated tools miss.

What is the best way to test focus management for dynamic content in web previews?

The best way to test focus management for dynamic content in web previews is combining WCAG 2.2 AA conformance evaluation with manual screen-reader walkthroughs and keyboard navigation tests to validate ARIA usage and focus shifts.

Does this accessibility audit cover both VoiceOver and TalkBack screen-reader workflows?

Yes, the accessibility audit covers VoiceOver and TalkBack screen-reader workflows, performing manual testing across Expo React Native mobile screens and web previews to validate inclusive use beyond automated baseline checks.