Run any Skill in Manus with one click

web-a11y-dynamic-ui

Stars4

Forks0

UpdatedApril 26, 2026 at 10:48

Handles accessible dynamic interfaces such as filtering, sorting, pagination, progress, live regions, status messages, data tables, and client-rendered result updates. Use when UI changes without a full page load.

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-dynamic-ui
description	Handles accessible dynamic interfaces such as filtering, sorting, pagination, progress, live regions, status messages, data tables, and client-rendered result updates. Use when UI changes without a full page load.

Web A11y Dynamic UI

Rules

Client-side updates need non-visual feedback.
Use live regions for status updates that should not move focus.
Move focus only when it improves task flow and orientation.
Use table semantics for tabular relationships, not layout.
Communicate sort, current page, result count, and progress state semantically and visually.

Checklist

Dynamic UI checklist

- [ ] Active filters and result counts are discoverable
- [ ] Loading, empty, error, and success states are announced when needed
- [ ] Pagination exposes current page and available movement
- [ ] Progress indicators expose current step/value where meaningful
- [ ] Tables have captions or labels, headers, and sort state
- [ ] Interactive controls inside data views preserve context

Output

Document update announcement strategy, focus strategy, table/result semantics, and regression checks.

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-dynamic-ui
description	Handles accessible dynamic interfaces such as filtering, sorting, pagination, progress, live regions, status messages, data tables, and client-rendered result updates. Use when UI changes without a full page load.

Web A11y Dynamic UI

Rules

Client-side updates need non-visual feedback.
Use live regions for status updates that should not move focus.
Move focus only when it improves task flow and orientation.
Use table semantics for tabular relationships, not layout.
Communicate sort, current page, result count, and progress state semantically and visually.

Checklist

Dynamic UI checklist

- [ ] Active filters and result counts are discoverable
- [ ] Loading, empty, error, and success states are announced when needed
- [ ] Pagination exposes current page and available movement
- [ ] Progress indicators expose current step/value where meaningful
- [ ] Tables have captions or labels, headers, and sort state
- [ ] Interactive controls inside data views preserve context

Output

Document update announcement strategy, focus strategy, table/result semantics, and regression checks.