SkillVaultskills Browse all 1,000+ skills

Frontend · Version 1.3.0 · Reviewed 2026-08-02

Accessible Heading Presence Auditor

Improve page heading presence and region labeling review with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 4 diagnostic checks 7 quality gates

Finds pages and major regions that lack headings needed for orientation and assistive-technology navigation. It grounds the decision in rendered routes, accessibility trees, major regions, dynamic states, page titles, and heading outlines and explicitly prevents a visually prominent text block substituting for a semantic heading or repeated cards creating a false page outline.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Page heading presence
  • Region labeling review
  • Heading navigation validation

How Accessible Heading Presence Auditor works

You provide

Component code, field metrics, and the failing interaction

It inspects

Semantics, focus, and render behavior for page heading presence

It decides

A region labeling review fix using native elements where possible

You verify

Keyboard traversal and assistive output re-checked

What it checks first

Accessible Heading Presence Auditor finds pages and major regions that lack headings needed for orientation and assistive-technology navigation. It grounds the decision in rendered routes, accessibility trees, major regions, dynamic states, page titles, and heading outlines and explicitly prevents a visually prominent text block substituting for a semantic heading or repeated cards creating a false page outline. Use it when the work involves Page heading presence, Region labeling review, Heading navigation validation.

  1. Whether the control uses a native element with real semantics or a div reconstructed with ARIA.
  2. Focus behavior across route changes, dialogs, and dynamic content insertion.
  3. Which Core Web Vital is failing, since LCP, INP, and CLS have unrelated causes.
  4. Whether state lives at the level that actually needs it, since misplaced state re-renders unrelated subtrees.

Failure modes it recognizes

  • A dialog that never moves focus into itself, leaving keyboard users stranded on the page behind it.
  • Layout shift from media without reserved dimensions, damaging CLS after content loads.
  • A long task blocking the main thread so interactions queue and INP degrades.
  • An inline object or function in props defeating memoization on every render.
  • Hydration mismatch from rendering time, randomness, or browser APIs during server render.

Answers it will reject

  • Patching a non-semantic control with ARIA instead of using the native element that behaves correctly.
  • Measuring performance in development mode, where the framework runs work that never ships.
  • Wrapping everything in memo, which adds comparison cost without removing identity churn.

Decision rules it applies

  • Prefer native semantic elements; ARIA is a correction layer rather than a foundation.
  • Reserve space for anything that loads asynchronously so layout stays stable.
  • Derive during render instead of synchronizing with an effect; effects are for external systems.

Evidence it asks for

  • Collect field Core Web Vitals rather than lab scores, since lab conditions hide real-device behavior.
  • Profile renders to attribute them to a specific trigger before optimizing.
  • Test keyboard-only traversal and screen-reader output for any interactive change.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to page heading presence.
  2. Trace concrete failure or abuse paths for region labeling review; do not report checklist items without a mechanism.
  3. Prioritize heading navigation validation findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Page heading presence assessment
  • Region labeling review decision and action plan
  • Heading navigation validation verification checklist

Evidence requirements

  • Interface code, rendered behavior, and user journey
  • Browser/device matrix and accessibility tree
  • Performance and usability observations

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the accessible heading presence auditor to our current page heading presence work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with rendered routes, accessibility trees, major regions, dynamic states, page titles, and heading outlines. The highest-risk failure is a visually prominent text block substituting for a semantic heading or repeated cards creating a false page outline. Require one programmatic page topic and headings for meaningful regions without manufacturing hierarchy for decoration. Verify the result by navigating every representative route and state through the accessibility-tree heading list.

Boundaries and compatibility

Ideal for

  • Page heading presence: produce a decision or artifact grounded in supplied evidence.
  • Region labeling review: produce a decision or artifact grounded in supplied evidence.
  • Heading navigation validation: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Treating automated accessibility scans as complete
  • Changing visual style without preserving behavior

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.