skills.rest
augustoheiss
augustoheissCOMMUNITY
Explore all skills by this author →
GitHub

agency-accessibility-auditor

Audit web interfaces for WCAG failures using automated scans and assistive-technology testing.

Updated Feb 11, 2026
Search Tags:#accessibility#wcag#screen-reader#aria#keyboard-navigation#a11y-audit#assistive-technology
One-click install
npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-accessibility-auditor-augustoheiss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-accessibility-auditor
Source: https://github.com/augustoheiss/LogicDefense/tree/main/.gemini/skills/agency-accessibility-auditor
Command: npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-accessibility-auditor-augustoheiss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility audits often miss the real-world barriers that prevent people with disabilities from using digital products; this Skill identifies those barriers, differentiates automated false positives from manual failures, and translates findings into actionable fixes tied to WCAG success criteria.

Core Features & Use Cases

  • Standards-based auditing: Evaluates interfaces against WCAG 2.2 AA (and AAA when specified) and references exact success criteria for each finding.
  • Automated + manual testing: Combines axe-core/Lighthouse-style automated scans with manual assistive-technology testing (VoiceOver, NVDA, JAWS), keyboard-only flows, zoom/high-contrast checks, and reduced-motion verification.
  • Actionable remediation: Produces prioritized reports with severity, WCAG references, code examples (ARIA/semantic HTML/focus management), and verification steps for developers and designers.
  • Use Case: Run a pre-release audit of a single-page web app to find keyboard traps, screen reader announcement failures, and contrast issues, then deliver a prioritized remediation plan that dev teams can implement.

Quick Start

Run a combined automated scan and manual screen reader walkthrough of the target page, document each issue with the WCAG criterion and a code-level remediation, and produce a prioritized audit report.

Frequently Asked Questions about agency-accessibility-auditor

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

FAQPage Schema
How do I run a WCAG audit on a web application using automated scans and manual screen reader testing?▼

A WCAG audit combines axe-core-style automated scans with manual assistive-technology testing using VoiceOver, NVDA, or JAWS, evaluating keyboard navigation, visual contrast, and zoom to identify real accessibility barriers against WCAG 2.2 AA criteria.

What is the best way to document accessibility barriers with code examples for developer remediation?▼

Documenting accessibility barriers requires prioritized reports containing exact WCAG references, severity ratings, semantic HTML or ARIA remediation code examples, and verification steps, ensuring developers can implement fixes and validate screen reader compatibility.

How do I differentiate automated accessibility false positives from actual WCAG failures?▼

Differentiating automated accessibility false positives from WCAG failures requires manual assistive-technology testing, validating keyboard-only flows, screen reader announcements, and reduced-motion checks to confirm real user barriers that automated tools cannot detect.

Can I use this accessibility audit approach for component libraries and interactive widgets?▼

Yes, accessibility auditing applies to component libraries and interactive widgets, evaluating scenarios requiring keyboard navigation, screen reader compatibility, focus management, and visual contrast checks to ensure complex user journeys meet WCAG 2.2 AA standards.

What's the difference between automated accessibility scans and manual assistive-technology testing?▼

Automated accessibility scans detect code-level WCAG failures quickly, while manual assistive-technology testing using screen readers and keyboard-only navigation identifies real-world user barriers and dynamic ARIA announcement failures that automated tools miss.

Why does my web app still have keyboard traps and screen reader announcement failures after passing automated accessibility scans?▼

Keyboard traps and screen reader announcement failures persist because automated accessibility scans cannot detect dynamic ARIA issues; manual assistive-technology testing using VoiceOver, NVDA, or keyboard-only flows is required to find these real-world WCAG barriers.

Related Skills

Explore More Design & Creative Skills→
thec3ukthec3uk

Frontend Accessibility

Guide frontend code to meet accessibility standards like ARIA and keyboard navigation.

Official
Basic
anavvanzinanavvanzin

agency-accessibility-auditor

Audit web and mobile interfaces for WCAG 2.2 accessibility barriers.

Community
Advanced
ryan-nguyen-01ryan-nguyen-01
4

skill-ui-accessibility

Analyze web UI structure, semantics, and ARIA usage for accessibility gaps.

Community
Advanced
bizoton19bizoton19

508-audit

Audit federal websites for WCAG 2.1 AA accessibility compliance.

Community
Advanced