skills.rest
mtsatryan
mtsatryanCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-tester

Audit digital products for WCAG 2.1/3.0 conformance across web, mobile, and software interfaces.

1|Updated Apr 23, 2026
Search Tags:#accessibility#a11y#compliance#wcag#screen-reader#keyboard-navigation#inclusive-design
One-click install
npx skills add https://github.com/mtsatryan/openclaw-ai-agents --skill accessibility-tester-mtsatryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-tester
Source: https://github.com/mtsatryan/openclaw-ai-agents/tree/main/accessibility-tester
Command: npx skills add https://github.com/mtsatryan/openclaw-ai-agents --skill accessibility-tester-mtsatryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies and verifies accessibility gaps in digital products, ensuring compliance with WCAG 2.1/3.0 and supporting inclusive design across assistive technologies, keyboard interactions, and color contrast.

Core Features & Use Cases

  • WCAG compliance assessment and gap analysis for web, mobile, and software interfaces.
  • Keyboard navigation, screen reader compatibility, color contrast, and ARIA labeling verification.
  • Remediation guidance and documentation to empower product teams to achieve accessible experiences.

Quick Start

Initiate an accessibility assessment for a web app focusing on WCAG 2.1 AA, keyboard navigation, and screen reader compatibility.

Frequently Asked Questions about accessibility-tester

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

FAQPage Schema
How do I audit my web app for WCAG 2.1 AA compliance?▼

To audit web apps for WCAG 2.1 AA compliance, assess screen reader compatibility, keyboard navigation, color contrast, and ARIA usage. The evaluation applies automated scans and manual verification to generate pass/fail criteria and remediation guidance.

How do I verify keyboard navigation and screen reader compatibility for digital interfaces?▼

Verifying keyboard navigation and screen reader compatibility requires manual testing of interactive elements across web, mobile, and software interfaces. The process checks focus order, ARIA labeling, and keyboard interactions to ensure assistive technologies function correctly.

Can I use automated scans for WCAG conformance testing on mobile interfaces?▼

Automated scans for WCAG conformance testing can be applied to mobile interfaces. These scans identify basic accessibility barriers, but manual verification is required to validate complex interactions like screen reader compatibility and keyboard navigation.

What is the best way to generate accessibility documentation with pass/fail criteria?▼

Generating accessibility documentation with pass/fail criteria involves auditing digital products for WCAG 2.1/3.0 conformance. The documentation details identified gaps, verification results, and specific remediation guidance to empower product teams to fix accessibility issues.

Does ARIA usage verification require manual testing or can it be fully automated?▼

ARIA usage verification cannot be fully automated. While automated scans detect missing or misapplied ARIA attributes, manual verification using screen readers is necessary to confirm that labels, roles, and dynamic updates are correctly announced to assistive technologies.

Why does color contrast testing fail on dynamic web components?▼

Color contrast testing fails on dynamic web components when background colors or text change state without meeting WCAG 2.1/3.0 contrast ratios. Manual verification across all interactive states is required to ensure continuous compliance and accessible experiences.

Related Skills

Explore More Design & Creative Skills→
ngoldblangoldbla
1

vpat

Audit HTML, CSS, and JavaScript/TypeScript projects for WCAG 2.1 conformance and generate VPAT 2.4 ACR documentation.

Community
Advanced
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced
calcosmiccalcosmic
9

accessibility

Audit frontend components for WCAG 2.2 AA accessibility compliance.

Community
Advanced
matteocervellimatteocervelli
25

accessibility-checker

Identify and report WCAG 2.1 Level AA accessibility violations on web pages.

Community
Advanced