accessibility-engineer

Audit and remediate web and mobile accessibility issues for WCAG 2.2 compliance.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Exia-thd/Digital-Nervous --skill accessibility-engineer-exia-thd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-engineer
Source: https://github.com/Exia-thd/Digital-Nervous/tree/main/skills/accessibility-engineer
Command: npx skills add https://github.com/Exia-thd/Digital-Nervous --skill accessibility-engineer-exia-thd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and implements accessibility improvements to make web and mobile products usable by people with visual, auditory, motor, and cognitive disabilities and to reduce legal and usability risk from non-compliance.

Core Features & Use Cases

  • Standards Compliance: Verifies and remediates issues against WCAG 2.2 (AA minimum, AAA preferred) and produces prioritized remediation plans.
  • Practical Audits: Runs automated axe-core and Lighthouse scans, performs keyboard navigation and focus audits, and conducts screen reader testing (VoiceOver, NVDA, TalkBack).
  • Implementation Guidance: Applies ARIA patterns, semantic HTML fixes, color contrast corrections, prefers-reduced-motion handling, and CI integration for recurring checks.
  • Use Case: Seamlessly integrate into Harden or Frontend pipelines to surface critical accessibility defects, produce an audit-report, and deliver a remediation plan and testing checklist.

Quick Start

Run a full accessibility audit across the site, generate a prioritized remediation plan, and include axe-core in CI for ongoing checks.

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 compliance and generate a remediation plan?

To audit for WCAG 2.2 compliance, run automated axe-core and Lighthouse scans, perform keyboard navigation and focus audits, and conduct screen reader testing to generate a prioritized remediation plan.

What is the best way to integrate automated accessibility checks into a Frontend CI pipeline?

Integrating accessibility checks into a Frontend CI pipeline involves running automated axe-core scans during development and production checks to surface critical defects and deliver a remediation testing checklist.

Does this accessibility audit approach support mobile interfaces and screen readers like VoiceOver and TalkBack?

Yes, the accessibility audit applies to both web and mobile interfaces, conducting screen reader testing with VoiceOver, NVDA, and TalkBack to ensure inclusive interactions across platforms.

How do I fix ARIA semantics and keyboard navigation issues found during an accessibility audit?

Fixing ARIA semantics and keyboard navigation issues involves applying ARIA patterns, implementing semantic HTML fixes, and correcting focus management to achieve WCAG 2.2 AA or AAA criteria compliance.

What accessibility standards and criteria are evaluated during an inclusive digital experience audit?

An inclusive digital experience audit evaluates technical requirements including WCAG 2.2 AA/AAA criteria, ARIA semantics and patterns, keyboard navigation, screen reader behavior, and color contrast ratios.

How do I handle prefers-reduced-motion and color contrast corrections for UI components?

Handling prefers-reduced-motion and color contrast corrections involves applying specific CSS media queries and adjusting visual contrast ratios to meet WCAG 2.2 AA/AAA standards during implementation.