agency-section-508-accessibility-specialist

Audit web applications for WCAG 2.0/2.1 AA conformance and generate VPAT/ACR documentation.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-section-508-accessibility-specialist-rajyeole6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-section-508-accessibility-specialist
Source: https://github.com/rajyeole6/AI-RECRUITER/tree/main/.agents/skills/engineering-section-508-specialist
Command: npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-section-508-accessibility-specialist-rajyeole6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the critical gap between automated accessibility scans and real-world usability, ensuring digital products meet legal requirements for users with disabilities.

Core Features & Use Cases

  • Manual Audit & Remediation: Provides expert guidance on fixing HTML, ARIA, and keyboard navigation issues that automated tools miss.
  • Compliance Documentation: Assists in authoring defensible VPAT/ACR reports and remediation plans for Section 508 and ADA Title II.
  • Use Case: Use this skill to audit a custom web component library to ensure it follows ARIA Authoring Practices and is fully operable by screen readers like JAWS and NVDA.

Quick Start

Use the agency-section-508-accessibility-specialist skill to perform a manual audit of the current login flow and generate a prioritized remediation plan.

Frequently Asked Questions about agency-section-508-accessibility-specialist

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

FAQPage Schema
How do I conduct a comprehensive Section 508 and ADA accessibility audit?

To conduct a comprehensive Section 508 and ADA accessibility audit, combine automated scanning with manual assistive-technology testing. This evaluates web applications for WCAG 2.0/2.1 AA conformance, keyboard operability, and semantic HTML integrity.

What is the difference between automated accessibility scanning and manual ARIA testing?

Automated accessibility scanning catches basic code errors, while manual ARIA testing identifies real-world usability gaps. Manual testing ensures web components follow ARIA Authoring Practices and are fully operable by screen readers like JAWS and NVDA.

How do I generate a defensible VPAT or ACR report for federal compliance?

To generate a defensible VPAT or ACR report for federal compliance, evaluate your application against WCAG 2.0/2.1 AA standards. This process produces actionable remediation plans and documentation required for Section 508 and ADA Title II.

Can I use this approach to audit a custom web component library for screen reader operability?

Yes, you can audit a custom web component library for screen reader operability. This approach provides expert guidance on fixing HTML, ARIA, and keyboard navigation issues that automated tools typically miss.

What is the best way to fix HTML and ARIA issues that automated accessibility tools miss?

The best way to fix HTML and ARIA issues missed by automated tools is through manual assistive-technology testing. This provides expert guidance on resolving keyboard navigation and semantic HTML integrity problems.