navigation-wayfinding-accessibility-audit

Audits website and application navigation, orientation, and wayfinding for WCAG accessibility.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill navigation-wayfinding-accessibility-audit-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: navigation-wayfinding-accessibility-audit
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/frontend-a11y/navigation-wayfinding-accessibility-audit
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill navigation-wayfinding-accessibility-audit-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users often cannot tell where they are, what destinations exist, or how to return after navigating websites and applications, and teams lack a structured way to audit landmarks, skip links, breadcrumbs, route transitions, and mobile navigation against WCAG criteria without overclaiming conformance. ## Core Features & Use Cases - Navigation Coverage Matrix: Systematically inspects landmarks, skip links, menus, current-location cues, titles, headings, consistent navigation, route transitions, deep links, search, mobile navigation, and large application shells. - Evidence-Bounded Findings: Separates supported WCAG criterion failures from broader wayfinding observations using a shared finding contract with severity, confidence, status, and verification steps. - Runtime and Responsive Testing: Guides testing of deep links, refresh, browser back/forward, cancelled navigation, error routes, and responsive menu variants across roles and viewports. - Use Case: A team auditing a single-page application uses this Skill to verify that route changes update the document title, preserve focus and history, expose current location, and keep mobile navigation destinations intact, producing a reproducible findings report. ## Quick Start Audit the navigation and wayfinding accessibility of my web application, covering landmarks, skip links, breadcrumbs, route transitions, and mobile menus, and report findings with WCAG mappings.

Frequently Asked Questions about navigation-wayfinding-accessibility-audit

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

FAQPage Schema
How do I audit website navigation for WCAG accessibility?▼

Audit navigation by inspecting landmarks, skip links, menus, current-location cues, page titles, headings, and consistent navigation, then testing route transitions, deep links, browser back/forward, and mobile variants at runtime. Record evidence per route, role, viewport, and assistive technology, and map only criterion-supported failures to WCAG.

How do I test SPA route changes for accessibility?▼

Test initial load, internal route changes, refresh, deep links, redirects, errors, and browser history in the running application. At each transition capture the URL, document title, focused element, scroll position, current-navigation state, and recovery path rather than inferring behavior from router code.

Does WCAG require breadcrumbs or search on every page?▼

No. WCAG 2.4.5 Multiple Ways requires more than one way to locate pages within a set, but search and breadcrumbs are not individually mandatory. Evaluate the actual structure and applicable exceptions instead of treating an omitted breadcrumb as an automatic failure.

Can this audit prove full WCAG conformance?▼

No. The audit produces a bounded, evidence-based review of sampled routes, shells, roles, and environments, not a conformance certification or legal determination. Untested routes, states, and assistive-technology combinations are listed as coverage gaps, never as passes.

When should I use a different accessibility audit instead?▼

Route keyboard mechanics, focus traps, and dialog behavior to a keyboard-focus audit, live-region announcements to a dynamic-interface audit, and pure semantic HTML or heading structure with no wayfinding concern to a semantic-structure audit. This skill focuses on orientation, navigation, and return paths.