accessibility-engineer

Audit web and mobile interfaces for WCAG 2.2 AA/AAA conformance and ARIA readiness.

47|11|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/buiphucminhtam/forgewright --skill accessibility-engineer-buiphucminhtam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-engineer
Source: https://github.com/buiphucminhtam/forgewright/tree/main/skills/accessibility-engineer
Command: npx skills add https://github.com/buiphucminhtam/forgewright --skill accessibility-engineer-buiphucminhtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and implements web/mobile accessibility to ensure WCAG 2.2 AA/AAA compliance, screen reader support, keyboard navigation, color contrast, ARIA patterns, and assistive technology testing.

Core Features & Use Cases

  • WCAG conformance auditing and remediation planning for web and mobile interfaces.
  • ARIA pattern integration, keyboard-navigable components, and accessible testing workflows.
  • Use Case: integrate accessibility checks into a production workflow to ship inclusive features with validated conformance.

Quick Start

Audit a production product for accessibility gaps and generate a remediation plan.

Frequently Asked Questions about accessibility-engineer

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

FAQPage Schema
How do I audit my web application for WCAG 2.2 AA conformance?

WCAG 2.2 AA conformance auditing evaluates web interfaces for keyboard navigation, screen-reader compatibility, color contrast, and ARIA patterns. The process generates structured documentation and a remediation plan for identified accessibility gaps across production-grade projects.

What's the best way to implement keyboard navigation and ARIA patterns for accessible components?

Implementing keyboard navigation and ARIA-ready interactions requires applying established accessibility patterns to interactive components. This ensures screen-reader compatibility and full keyboard operability, satisfying WCAG 2.2 AA/AAA conformance requirements for web and mobile interfaces.

Can I use this accessibility audit approach for both web and mobile interfaces?

Yes, the accessibility audit and remediation process applies to both web and mobile interfaces. It validates color-contrast remediation, ARIA integration, and assistive technology testing across platforms to achieve WCAG 2.2 AA/AAA conformance.

How do I integrate accessibility testing into a production workflow?

Integrating accessibility checks into a production workflow involves running automated and manual testing for keyboard navigation, screen-reader compatibility, and color contrast. This ships inclusive features with validated WCAG conformance and structured remediation artifacts.

Does WCAG 2.2 AAA conformance require more than automated accessibility testing?

WCAG 2.2 AAA conformance requires both automated and manual testing. Automated checks catch color-contrast and ARIA issues, while manual testing validates screen-reader compatibility, keyboard navigation, and assistive technology interactions for full compliance.

When should I generate a remediation plan for accessibility gaps?

Generate a remediation plan after auditing production products for accessibility gaps. The plan documents WCAG 2.2 AA/AAA non-conformance findings, ARIA pattern failures, and keyboard navigation issues, providing structured artifacts for targeted fixing within Harden mode workflows.