Run any Skill in Manus with one click

web-a11y-web-components

Stars4

Forks0

UpdatedApril 26, 2026 at 10:48

Applies accessibility guidance to custom elements and Shadow DOM, including progressive enhancement, slots, focus delegation, ElementInternals, ARIA limitations, and testing gaps. Use when building or auditing web components and design-system primitives.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

klovaaxel

klovaaxel/web-a11y-agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

SKILL.md

readonly

name	web-a11y-web-components
description	Applies accessibility guidance to custom elements and Shadow DOM, including progressive enhancement, slots, focus delegation, ElementInternals, ARIA limitations, and testing gaps. Use when building or auditing web components and design-system primitives.

Web A11y Web Components

Rules

Make accessible usage the easiest component API.
Prefer progressive enhancement and useful light DOM fallback.
Keep semantic reading order correct with slots and DOM order.
Avoid brittle cross-root ARIA assumptions.
Validate required labels, titles, and relationships at runtime where useful.
Test manually because scanners vary in Shadow DOM coverage.

Checklist

Web component checklist

- [ ] Component has usable fallback or failure mode
- [ ] Slot order supports semantic reading order
- [ ] Required accessibility inputs are documented and enforced
- [ ] Focus delegation behavior is intentional
- [ ] ARIA relationships do not depend on unsupported cross-root references
- [ ] Automation is paired with keyboard and screen reader smoke checks

Output

Document component contract, Shadow DOM constraints, focus behavior, and manual verification notes.

More from this repository

same repository

web-a11y-authoring

klovaaxel/web-a11y-agent-skills

Builds accessible pages and components with semantic HTML, correct names/roles/states, keyboard support, focus management, links, images, SVG, media, and native controls first. Use when implementing or refactoring frontend UI.

2026-04-264

web-a11y-forms

klovaaxel/web-a11y-agent-skills

Designs and reviews accessible forms, search, validation, errors, grouping, required state, multi-step flows, and recovery behavior. Use when implementing or auditing form-heavy UI.

2026-04-264

web-a11y-review

klovaaxel/web-a11y-agent-skills

Reviews frontend changes for accessibility regressions across semantics, keyboard/focus behavior, forms, dynamic updates, styling, ARIA, and tests. Use for pull requests, diffs, audits, and pre-merge sign-off.

2026-04-264

web-a11y-testing

klovaaxel/web-a11y-agent-skills

Validates accessibility with automated checks, keyboard walkthroughs, screen reader smoke tests, zoom/preference checks, and focused regression reporting. Use when verifying new UI or confirming fixes.

2026-04-264

web-a11y-orchestrator

klovaaxel/web-a11y-agent-skills

Central routing and orchestration skill for web accessibility work. Use as the default entrypoint for accessibility-related UI tasks to select the right authoring, review, remediation, and testing workflows.

2026-04-264

web-a11y-css

klovaaxel/web-a11y-agent-skills

Reviews and writes CSS that preserves accessibility across contrast, focus styles, reduced motion, forced colors, zoom, target size, semantic integrity, and custom-styled controls. Use for UI styling and design-system changes.

2026-04-264

name	web-a11y-web-components
description	Applies accessibility guidance to custom elements and Shadow DOM, including progressive enhancement, slots, focus delegation, ElementInternals, ARIA limitations, and testing gaps. Use when building or auditing web components and design-system primitives.

Web A11y Web Components

Rules

Make accessible usage the easiest component API.
Prefer progressive enhancement and useful light DOM fallback.
Keep semantic reading order correct with slots and DOM order.
Avoid brittle cross-root ARIA assumptions.
Validate required labels, titles, and relationships at runtime where useful.
Test manually because scanners vary in Shadow DOM coverage.

Checklist

Web component checklist

- [ ] Component has usable fallback or failure mode
- [ ] Slot order supports semantic reading order
- [ ] Required accessibility inputs are documented and enforced
- [ ] Focus delegation behavior is intentional
- [ ] ARIA relationships do not depend on unsupported cross-root references
- [ ] Automation is paired with keyboard and screen reader smoke checks

Output

Document component contract, Shadow DOM constraints, focus behavior, and manual verification notes.