Accessibility Engineer

Audit UI components for WCAG compliance and accessibility gaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tannergolden/repository --skill accessibility-engineer-tannergolden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Accessibility Engineer
Source: https://github.com/tannergolden/repository/tree/main/.agent/storage/skills/accessibility
Command: npx skills add https://github.com/tannergolden/repository --skill accessibility-engineer-tannergolden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Digital products often exclude users with disabilities due to insufficient accessibility considerations. This skill ensures inclusivity by advocating for semantic HTML, keyboard navigation, color contrast, and WCAG-compliant practices throughout the product lifecycle.

Core Features & Use Cases

  • Accessibility audits: Systematically evaluate interfaces for keyboard operability, screen reader compatibility, and semantic structure, then document fixes.
  • Guidelines & Standards: Enforce semantic HTML, proper ARIA usage, and color-contrast requirements to meet WCAG criteria.
  • Use Case: Release-ready web apps gain improved usability for users with disabilities, reducing accessibility-related risks and QA rework.

Quick Start

Run a quick accessibility assessment on the latest UI to identify keyboard, color-contrast, and semantic issues.

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 app for WCAG compliance and keyboard accessibility?

To audit WCAG compliance, evaluate UI components for keyboard operability, screen reader compatibility, semantic HTML structure, and color contrast, then document actionable fixes and validation checkpoints.

What is the best way to fix semantic HTML and ARIA issues for screen reader compatibility?

The best way to fix screen reader compatibility issues is to enforce semantic markup and proper ARIA usage across your interfaces, ensuring all interactive elements are correctly announced and navigable.

How do I check color contrast requirements to meet WCAG criteria?

You check color contrast by evaluating your UI components against WCAG contrast guidelines, identifying insufficient ratios, and applying actionable fixes to ensure text remains readable for users with visual impairments.

Can I use accessibility audits during QA workflows to reduce rework?

Yes, you can integrate accessibility audits across design, development, and QA workflows to identify keyboard, contrast, and semantic issues early, reducing accessibility-related risks and QA rework before release.

What inclusive design principles should I apply for assistive technology users?

Apply inclusive design by enforcing semantic HTML, keyboard navigation, and color-contrast guidelines, ensuring digital products are operable and usable for users relying on assistive technologies.

When should I not rely on automated accessibility checks alone?

Automated checks have limitations detecting real-world keyboard navigation and screen reader compatibility scenarios, so combine them with manual audits to validate semantic structure and interactive element behavior.