accessibility-tester

Identify UI accessibility defects including keyboard navigation, focus management, labeling, ARIA semantics, and color contrast; document them with remediation steps and validation criteria for runtime testing.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill accessibility-tester-jshsakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-tester
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/accessibility-tester
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill accessibility-tester-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify accessibility defects in UI changes, providing evidence-based findings to reduce risk and improve usability.

Core Features & Use Cases

  • Evaluates keyboard navigation, focus order, and focus visibility across critical UI paths
  • Checks ARIA roles, labeling, state semantics, color and non-text contrast, and dynamic content updates for screen readers
  • Produces actionable remediation guidance tied to concrete UI elements and user impact

Quick Start

Run a focused accessibility audit on the latest UI changes and report the top-priority findings with recommended fixes.

Frequently Asked Questions about accessibility-tester

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

FAQPage Schema
How do I audit UI changes for accessibility defects?

To audit UI changes for accessibility defects, evaluate keyboard navigation, ARIA semantics, and color contrast, then document concrete findings with remediation steps and validation criteria.

What is the best way to check ARIA roles and color contrast in my web interface?

Checking ARIA roles and color contrast involves evaluating state semantics, labeling, and non-text contrast across dynamic content to ensure screen reader compatibility and produce actionable remediation guidance.

How do I test keyboard navigation and focus management for critical UI paths?

Testing keyboard navigation and focus management requires evaluating focus order and focus visibility across critical UI paths to identify interaction barriers and document evidence-based findings.

Can I use this accessibility audit for dynamic content and interaction flows?

Yes, accessibility audits can be applied to UI components, interaction flows, and dynamic content across web interfaces to identify defects and improve usability with evidence-driven findings.

Why does my accessibility review need to include validation criteria for runtime testing?

Accessibility reviews need validation criteria for runtime testing to ensure thorough evaluation of dynamic content updates, provide concrete findings, and verify that remediation steps effectively resolve user impact.

What limitations exist when auditing screen reader compatibility for non-text contrast?

Auditing screen reader compatibility for non-text contrast relies on evaluating ARIA state semantics and dynamic updates, requiring concrete UI elements and runtime testing to validate findings and reduce usability risk.