Run any Skill in Manus with one click

web-a11y-navigation

Stars4

Forks0

UpdatedApril 26, 2026 at 10:48

Builds accessible navigation and wayfinding with landmarks, headings, skip links, breadcrumbs, nav lists, current-page state, disclosure navigation, and menu-vs-navigation decisions. Use when implementing headers, sidebars, nav bars, or complex page structure.

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-navigation
description	Builds accessible navigation and wayfinding with landmarks, headings, skip links, breadcrumbs, nav lists, current-page state, disclosure navigation, and menu-vs-navigation decisions. Use when implementing headers, sidebars, nav bars, or complex page structure.

Web A11y Navigation

Navigation Rules

Use landmarks to communicate page regions.
Label repeated landmarks clearly and uniquely.
Use headings to expose information hierarchy.
Represent navigation lists semantically when count and structure help orientation.
Mark the current page or item semantically and visually.
Do not use ARIA menu roles for ordinary site navigation.

Checklist

Navigation checklist

- [ ] Main content and navigation are easy to jump to
- [ ] Skip links are available where repeated content creates friction
- [ ] Breadcrumbs use a labeled nav, list semantics, and current-item indication
- [ ] Current page state does not rely on color alone
- [ ] Disclosure navigation uses buttons for toggles and links for navigation
- [ ] Responsive navigation preserves keyboard and screen reader flow

Output

Explain landmark labels, current state, skip-link strategy, keyboard behavior, and any menu/navigation trade-offs.

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-navigation
description	Builds accessible navigation and wayfinding with landmarks, headings, skip links, breadcrumbs, nav lists, current-page state, disclosure navigation, and menu-vs-navigation decisions. Use when implementing headers, sidebars, nav bars, or complex page structure.

Web A11y Navigation

Navigation Rules

Use landmarks to communicate page regions.
Label repeated landmarks clearly and uniquely.
Use headings to expose information hierarchy.
Represent navigation lists semantically when count and structure help orientation.
Mark the current page or item semantically and visually.
Do not use ARIA menu roles for ordinary site navigation.

Checklist

Navigation checklist

- [ ] Main content and navigation are easy to jump to
- [ ] Skip links are available where repeated content creates friction
- [ ] Breadcrumbs use a labeled nav, list semantics, and current-item indication
- [ ] Current page state does not rely on color alone
- [ ] Disclosure navigation uses buttons for toggles and links for navigation
- [ ] Responsive navigation preserves keyboard and screen reader flow

Output

Explain landmark labels, current state, skip-link strategy, keyboard behavior, and any menu/navigation trade-offs.