Accessibility Engineer

Name: Accessibility Engineer
Availability: InStock
Author: daffy0208

Audit web UIs for WCAG 2.1 AA compliance and keyboard navigation.

34|7|Updated Oct 22, 2025

Search Tags:#inclusive design #accessibility #a11y #screen reader #keyboard navigation #ARIA #WCAG

Ready to run

npx skills add https://github.com/daffy0208/ai-dev-standards --skill accessibility-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Accessibility Engineer
Source: https://github.com/daffy0208/ai-dev-standards/tree/main/SKILLS/accessibility-engineer
Command: npx skills add https://github.com/daffy0208/ai-dev-standards --skill accessibility-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates accessibility barriers that prevent people with disabilities from using your applications, ensuring legal compliance and expanding your user base.

Core Features & Use Cases

WCAG Compliance: Achieve WCAG 2.1 AA standards with practical implementation guidance.
Accessibility Auditing: Conduct comprehensive audits using automated tools and manual testing methods.
Use Case: Imagine you're launching a new e-commerce site. Use this Skill to ensure all users can navigate, purchase products, and complete checkout using only keyboard controls and screen readers.

Quick Start

Use the accessibility engineer skill to audit the current web page for WCAG 2.1 AA compliance issues.

Frequently Asked Questions about Accessibility Engineer

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

FAQPage Schema

How do I achieve WCAG 2.1 AA compliance for my web application?▼

WCAG 2.1 AA compliance requires implementing semantic HTML, proper ARIA labels, sufficient color contrast, keyboard navigation, and screen reader support. Use automated tools like Lighthouse and axe to identify gaps, then manually test keyboard focus management and screen reader behavior to meet all AA standards.

What's the best way to audit a website for accessibility issues?▼

Conduct accessibility audits by combining automated testing tools (Lighthouse, axe) with manual verification. Test keyboard-only navigation, screen reader functionality, color contrast ratios, and semantic HTML structure. Document findings against WCAG 2.1 AA criteria to identify and prioritize remediation.

How do I ensure keyboard navigation works reliably across my application?▼

Keyboard navigation requires logical tab order, visible focus indicators, semantic HTML elements, and skip links. Test every interactive component using only the keyboard, verify focus management in modals and dynamic content, and use ARIA attributes to clarify complex widget behavior for assistive technologies.

Can I use ARIA to fix accessibility issues in my existing UI?▼

ARIA enhances accessibility when applied correctly—use it to label interactive elements, describe regions, manage focus, and clarify widget roles. However, ARIA alone cannot replace semantic HTML; always prioritize native elements first, then layer ARIA for complex patterns that semantic markup cannot express.

Do screen readers work with all HTML frameworks and platforms?▼

Screen readers work with any platform that produces valid semantic HTML and respects keyboard focus. Compatibility depends on proper markup, ARIA implementation, and avoiding focus traps or hidden semantic structure. Test with actual screen readers and multiple frameworks to verify integration.

What are the limitations of automated accessibility testing tools?▼

Automated tools like Lighthouse and axe catch structural issues, color contrast, and missing labels but cannot verify screen reader announcements, keyboard usability, or user experience nuances. Manual testing with real assistive technologies and users with disabilities is essential to find gaps automation misses.