skills.rest
pedropenha
pedropenhaCOMMUNITY
Explore all skills by this author →
GitHub

web-a11y-orchestrator

Routes accessibility tasks to authoring, review, remediation, and testing workflows.

Updated Sep 8, 2026
Search Tags:#accessibility#a11y#audit#orchestration#wcag#web ui#aria
One-click install
npx skills add https://github.com/pedropenha/project-skills --skill web-a11y-orchestrator-pedropenha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-a11y-orchestrator
Source: https://github.com/pedropenha/project-skills/tree/main/.agents/skills/web-a11y-orchestrator
Command: npx skills add https://github.com/pedropenha/project-skills --skill web-a11y-orchestrator-pedropenha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessibility work spans many concerns—semantics, forms, navigation, dynamic UI, CSS, and testing—and it is easy to pick the wrong workflow or miss a critical check. This Skill acts as the default entrypoint for accessibility-related UI tasks, routing each request to the right specialized workflow. ## Core Features & Use Cases - Routing Map: Maps task types (forms, navigation, overlays, tables, Shadow DOM, audits) to the appropriate specialized accessibility skills. - Structured Workflow: Provides a checklist from scope definition through implementation, review, remediation, and validation. - Severity Policy: Classifies issues as Critical, High, Medium, or Low so teams know what blocks release. - Use Case: When asked to make a checkout form accessible, the orchestrator routes to the forms workflow, then produces an accessibility report with blocking issues and verification status for automation, keyboard, and screen reader checks. ## Quick Start Ask the assistant to review the accessibility of a page or component and route the work through the appropriate accessibility workflows.

Frequently Asked Questions about web-a11y-orchestrator

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

FAQPage Schema
How do I start an accessibility review of a web page?▼

Begin by defining the scope and changed user journeys, then select the relevant workflow passes from the routing map. Finish with an accessibility report covering blocking issues and verification results for automation, keyboard, and screen reader smoke checks.

Which accessibility workflow should I use for forms and validation?▼

Forms, validation, search, and multi-step flows route to the web-a11y-forms workflow. Navigation and landmarks go to web-a11y-navigation, while styling, focus, and contrast issues go to web-a11y-css.

How are accessibility issues prioritized by severity?▼

Issues are classified as Critical (blocks core task completion for keyboard or assistive technology users), High (major confusion or lost state), Medium (degraded usability with a workable path), or Low (polish and consistency).

Does this cover web components and Shadow DOM accessibility?▼

Yes, web components and Shadow DOM work is routed to the dedicated web-a11y-web-components workflow. Audits, triage, and CI checks route to the debugging, review, and testing workflows.

What references does the accessibility workflow rely on?▼

It points to public references including W3C WCAG, WAI Tutorials, the WAI-ARIA Authoring Practices Guide, MDN Web Docs, WebAIM, and axe documentation with browser DevTools accessibility docs.

Related Skills

Explore More Software Engineering Skills→
DagimAlemayehuuDagimAlemayehuu

agentic-engineering-experience

Define user journeys, page purpose, and accessibility behavior before visual design.

Community
Intermediate
mkolb22mkolb22

Accessibility Checking

Identify and report WCAG accessibility issues in web interfaces.

Community
Advanced
mtsatryanmtsatryan
1

accessibility-auditor

Audit web applications for WCAG compliance using axe-core and Playwright.

Community
Advanced
ringlochidringlochid

coding-router

Route coding requests to the most appropriate first skill using evidence-based rules.

Community
Basic