semantic-structure-accessibility-audit

Reviews HTML templates and components for semantic structure and ARIA accessibility issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessibility reviews of web pages often produce vague claims or false conformance statements. This Skill performs an evidence-based audit of semantic HTML and document structure, separating confirmed WCAG failures from probable issues, manual-test requirements, and best-practice advice. ## Core Features & Use Cases - Structured Semantic Audit: Inspects headings, landmarks, page titles, document language, lists, tables, labels, reading order, link and button semantics, ARIA usage, and accessible names against WCAG 2.2 criteria. - Evidence-Based Classification: Classifies every check into confirmed failures, passes, probable issues, manual-test requirements, not-applicable checks, or unavailable evidence with severity, confidence, and framework mappings. - Scoped Handoffs: Routes out-of-scope concerns like keyboard behavior, visual presentation, and dynamic-widget interaction to specialist skills instead of silently dropping them. - Use Case: A frontend developer asks for an accessibility review of a React route template. The Skill inspects the JSX, reports a missing document language as a confirmed failure, flags a client-side title update as needing runtime validation, and produces a coverage matrix showing exactly what was and was not verified. ## Quick Start Audit the semantic HTML and ARIA structure of the templates in src/pages and report evidence-backed WCAG 2.2 findings.

Frequently Asked Questions about semantic-structure-accessibility-audit

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

FAQPage Schema
How do I audit semantic HTML for accessibility issues?▼

Run a semantic structure audit that inspects headings, landmarks, lists, tables, labels, reading order, and ARIA against WCAG 2.2 criteria. Each finding is classified by evidence strength, from confirmed failures to probable issues requiring runtime validation.

How to check ARIA roles and accessible names in components?▼

Validate role values, required states and properties, permitted ARIA on native elements, and accessible-name computation including precedence and name-from-content behavior. Broken aria-labelledby references and missing visible labels in accessible names are flagged with evidence.

Can a source code review prove WCAG conformance?▼

No. Source review can confirm specific failures and passes, but runtime composition, shadow DOM, localization, and conditional rendering can change final semantics. The audit records manual-test requirements and unavailable evidence instead of claiming complete conformance.

Does this audit cover keyboard navigation and focus management?▼

No. Keyboard behavior, focus visibility, visual presentation, form validation, and dynamic-widget interaction are out of scope. These concerns are recorded as specialist handoffs with the triggering evidence rather than being silently dropped.

Is a skipped heading level or multiple h1 elements a WCAG failure?▼

Not automatically. Skipped heading levels and multiple h1 elements require contextual review and are treated as quality concerns unless evidence shows an unmet requirement. The audit separates WCAG failures from authoring best practices.