# Audit Page Structure > Audits page structure for accessibility: landmark regions, heading hierarchy, navigation patterns, skip links, and document metadata. Use ONLY when the user explicitly asks about landmarks, heading order, page outline, or navigation structure — NOT for general accessibility scans or fix workflows (use scan-accessibility for those). - Skill: `web-dna/audit-page-structure` (Agent Skill) - Install (CLI): `npx skillmds@latest add web-dna/audit-page-structure` - Raw SKILL.md: https://api.skillmd.com/api/skills/web-dna/audit-page-structure/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - License: MIT - Author: web-DnA (https://skillmd.com/u/web-dna) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/web-dna/audit-page-structure --- # Page Structure Audit ## What This Checks 1. **Landmark regions** — header, nav, main, footer, aside (correct nesting and labeling) 2. **Heading hierarchy** — single h1, no skipped levels, meaningful text 3. **Navigation patterns** — skip links, consistent navigation, labeled nav regions 4. **Document metadata** — lang attribute, title element, viewport meta ## Procedure ### With Browser (URL provided) 1. Call `run_accessibility_scan` with the URL. For an audit (one-shot, high-confidence review), prefer dual-engine: `run_accessibility_scan({ url, engines: ["axe", "htmlcs"] })`. The extra ~2–4 s is acceptable for audits and surfaces structural issues axe alone can miss (e.g. deprecated `align` attributes, missing iframe titles). 2. Filter results for structural rules: - `region`, `landmark-one-main`, `landmark-no-duplicate-main`, `landmark-banner-is-top-level`, `landmark-contentinfo-is-top-level`, `landmark-main-is-top-level`, `landmark-unique` - `heading-order`, `page-has-heading-one`, `empty-heading`, `p-as-heading` - `document-title`, `html-has-lang`, `html-lang-valid` - `bypass` 3. Present findings grouped by category (landmarks, headings, navigation, metadata) ### Without Browser (source files provided) 1. Identify the layout/page component files (layout.tsx, App.vue, index.html, etc.) 2. Check for landmark elements per `navable://docs/semantic-html` reference: - Is there a `
` / `