skills.rest
gcampton
gcamptonCOMMUNITY
Explore all skills by this author →
Website𝕏@gcamptonGitHub

gteam-accessibility-auditor

Audit web and mobile interfaces against WCAG 2.2 and produce prioritized remediation guidance.

Updated Aug 23, 2026
Search Tags:#accessibility#a11y#remediation#wcag#screen-reader#aria#accessibility-audit
One-click install
npx skills add https://github.com/gcampton/GTeam --skill gteam-accessibility-auditor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gteam-accessibility-auditor
Source: https://github.com/gcampton/GTeam/tree/main/specialists/accessibility-auditor
Command: npx skills add https://github.com/gcampton/GTeam --skill gteam-accessibility-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill finds and fixes accessibility barriers that prevent people with visual, motor, cognitive, or auditory disabilities from using web and mobile products, turning audit findings into prioritized, actionable remediation with copy-ready code examples.

Core Features & Use Cases

  • WCAG 2.2 Audits: Automated plus manual audits against POUR principles with severity, relevant success criteria, and prioritised remediation.
  • Assistive Technology Testing: Practical checks and test patterns for screen readers (VoiceOver, NVDA, JAWS), keyboard navigation, zoom/magnification, colour blindness, and reduced motion.
  • Remediation and Code Fixes: Concrete fixes including ARIA patterns, focus management, skip links, captions, and responsive text sizing with before/after examples.
  • Use Case: Run a component-level audit for a checkout form, identify keyboard traps and missing labels, and return prioritized fixes with React or plain-HTML examples.

Quick Start

Run a full WCAG 2.2 audit on https://example.com and return a prioritized remediation plan with code-ready fixes.

Frequently Asked Questions about gteam-accessibility-auditor

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

FAQPage Schema
How do I perform a WCAG 2.2 accessibility audit on a web page?▼

A WCAG 2.2 accessibility audit requires running automated tools and manual checks against POUR principles to identify barriers on web pages. This process evaluates page-level and component-level interfaces to produce a prioritized remediation plan with severity ratings and relevant success criteria.

What's the best way to fix keyboard navigation traps and missing ARIA labels in a checkout form?▼

Fixing keyboard traps and missing ARIA labels requires implementing correct ARIA patterns and focus management for your checkout form. Component-level audits identify these specific motor and visual barriers, returning code-ready fixes with before-and-after examples in plain HTML or React.

Does screen reader testing work with VoiceOver, NVDA, and JAWS during an accessibility audit?▼

Screen reader testing with VoiceOver, NVDA, and JAWS is fully supported during an accessibility audit. Practical checks and test patterns are applied to evaluate how assistive technologies interact with your interfaces, ensuring visually impaired users can navigate content effectively.

How do I test web interfaces for zoom, magnification, and reduced motion preferences?▼

Testing web interfaces for zoom, magnification, and reduced motion involves manual checks against WCAG accessibility criteria. The audit evaluates whether users can adjust text sizing and disable animations, returning responsive CSS fixes and motion preference media query guidance.

Can I audit mobile interfaces for WCAG compliance or is it limited to web pages?▼

Auditing mobile interfaces for WCAG compliance is supported alongside web page evaluations. The accessibility audit applies to both web and mobile platforms, identifying visual, motor, cognitive, and auditory barriers to ensure accessible UX across all product interfaces.

What are the limitations of automated WCAG 2.2 accessibility checks?▼

Automated WCAG 2.2 accessibility checks are limited because they cannot detect all manual barriers like keyboard navigation traps or screen reader context issues. A complete audit combines automated tools with manual assistive-technology testing to ensure full compliance and accessible UX.

Related Skills

Explore More Design & Creative Skills→
dodygdodyg

cognitive-accessibility

Evaluate web interfaces against WCAG 2.2 cognitive criteria and COGA guidance.

Community
Intermediate
travisjneumantravisjneuman
88

accessibility-a11y

Ensure WCAG 2.2 compliance with ARIA patterns and keyboard navigation.

Community
Intermediate
MinhAnh-CorpMinhAnh-Corp

accessibility-compliance

Implement WCAG 2.2 compliant interfaces and ARIA patterns for UI components.

Official
Intermediate
mahamaneharouna9-cpumahamaneharouna9-cpu

accessibility-expert

Audit web accessibility for WCAG 2.1/2.2 compliance and ARIA errors.

Community
Advanced