accessibility-tester

Audit digital interfaces for WCAG 2.1 compliance and accessibility gaps.

68|6|Updated Apr 16, 2020
One-click install
npx skills add https://github.com/zenobi-us/dotfiles --skill accessibility-tester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-tester
Source: https://github.com/zenobi-us/dotfiles/tree/main/devtools/files/opencode/skills/accessibility-tester
Command: npx skills add https://github.com/zenobi-us/dotfiles --skill accessibility-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? Digital products often fail to meet accessibility standards, excluding users with disabilities and leading to compliance issues, legal risks, and poor user experience.

Core Features & Use Cases

  • WCAG Compliance Verification: Ensures adherence to WCAG 2.1 Level AA standards through automated and manual testing.
  • Assistive Technology Testing: Verifies compatibility with screen readers (NVDA, JAWS, VoiceOver) and ensures keyboard navigation.
  • Inclusive Design Remediation: Fixes color contrast, implements ARIA attributes, and optimizes content structure for cognitive accessibility.
  • Use Case: Your web application needs an accessibility audit to ensure WCAG 2.1 AA compliance. Use this Skill to perform automated scans, manual keyboard navigation tests, and screen reader verification, identifying and remediating all critical violations.

Quick Start

Use the accessibility-tester skill to perform an accessibility audit on your web application, focusing on 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 a web application for WCAG 2.1 compliance?

WCAG 2.1 compliance auditing combines automated scans with manual testing to identify violations. Run automated accessibility scans across your web application, then perform manual keyboard navigation tests and screen reader compatibility checks using assistive technologies like NVDA, JAWS, or VoiceOver to uncover gaps automated tools miss.

Can I test keyboard navigation and screen reader compatibility across multiple platforms?

Yes, keyboard navigation and screen reader compatibility testing spans web, mobile, and software UIs. Test keyboard-only workflows on each platform, verify screen reader announcement accuracy, and validate ARIA labels and semantic structure to ensure inclusive access across your entire digital product.

What accessibility issues does WCAG 2.1 Level AA cover?

WCAG 2.1 Level AA covers color contrast ratios, keyboard navigation, screen reader compatibility, ARIA labeling, error messaging clarity, and cognitive accessibility considerations. Compliance requires addressing visual, motor, auditory, and cognitive barriers that exclude users with disabilities from digital products.

How do I fix color contrast and ARIA attribute issues?

Color contrast remediation ensures text meets WCAG 2.1 ratio requirements; ARIA attribute implementation adds semantic labels for screen reader users. Apply inclusive design fixes by updating color palettes, adding missing ARIA roles and descriptions, and restructuring content for assistive technology compatibility.

What's included in an accessibility audit report?

An accessibility audit report documents automated scan results, manual testing findings, screen reader compatibility verification outcomes, identified WCAG violations, remediation guidance, and conformance documentation. Actionable reports prioritize critical violations and provide step-by-step fixes for developers and designers.

Do I need assistive technology testing if I use automated accessibility tools?

Automated scans catch rule-based violations but miss context-dependent issues that assistive technology testing reveals. Manual testing with screen readers, keyboard navigation, and real user feedback validates that fixes work in practice and identifies UX gaps automated tools cannot detect.