accessibility-auditor

Reviews Android screens for accessibility issues across semantics, contrast, touch targets, and TalkBack flow.

Updated Jan 2, 2024
One-click install
npx skills add https://github.com/Mithrandir21/game-deals-app --skill accessibility-auditor-mithrandir21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/Mithrandir21/game-deals-app/tree/main/.claude/skills/accessibility-auditor
Command: npx skills add https://github.com/Mithrandir21/game-deals-app --skill accessibility-auditor-mithrandir21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Android apps often ship with accessibility defects — missing contentDescription, undersized touch targets, poor contrast, broken TalkBack navigation — that block users who rely on assistive technology. This Skill provides a structured, screen-by-screen audit process so nothing on the long accessibility checklist gets missed. ## Core Features & Use Cases - Phased audit workflow: Runs automated checks first (Accessibility Scanner, lint, Compose semantics tree dumps), then manual TalkBack walkthroughs, then high-impact edge cases like WebViews, forms, RTL, and keyboard access. - Concrete Compose and View fixes: Gives specific remediation code patterns such as Modifier.semantics, minimumInteractiveComponentSize, liveRegion, and AccessibilityDelegate for custom views. - Severity-ranked report output: Produces a findings document grouping issues by screen with Blocker/High/Medium/Low severity and a recommended remediation order. - Use Case: Before launching a new checkout screen, run the audit to catch that the icon-only close button lacks a contentDescription and the error text is communicated by color alone, then fix both before release. ## Quick Start Audit the accessibility of my Android app's main screens and produce a severity-ranked report of TalkBack, contrast, and touch target issues.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema
How do I test Android app accessibility with TalkBack?▼

Enable TalkBack in system settings and navigate each screen without looking, checking reading order, labels, and focus behavior. Combine this with Accessibility Scanner and lint checks to catch contrast, touch target, and missing-label issues automatically.

How to make Jetpack Compose components accessible?▼

Use Modifier.semantics to set contentDescription, roles, and headings, and Modifier.minimumInteractiveComponentSize for 48dp touch targets. Group related elements with mergeDescendants and add liveRegion for status updates that should be announced.

What is the minimum touch target size on Android?▼

Interactive elements should be at least 48dp by 48dp. In Compose use Modifier.minimumInteractiveComponentSize(); in XML layouts set android:minWidth and android:minHeight to 48dp.

Does Accessibility Scanner catch all accessibility issues?▼

No, Accessibility Scanner only catches a fraction of issues like contrast, touch targets, and missing labels. Manual TalkBack walkthroughs are required to find reading order problems, unannounced state changes, and focus management defects.

Why does TalkBack read my button label twice?▼

This happens when contentDescription duplicates the visible text label. If the visible text already serves as the label, leave contentDescription null so TalkBack announces it only once.