Static Landmark Region Auditor
Inventory declared/native landmark candidates and limited naming evidence in pasted HTML source.
Loading tool…
How to use Static Landmark Region Auditor
Review major document regions before real keyboard and assistive-technology tests. The source profile distinguishes explicit roles from native candidates and reports what naming rules it did not compute.
- Enter input.
- Choose the settings for static landmark region auditor, then run the tool.
- Review the result and any limitations before copying or downloading it.
Good to know
- 100,000 source characters,20,000 nodes and1000 region candidates. No HTML is mounted or navigated.
- Naming evidence uses aria-label and unique aria-labelledby text only. Contextual appropriateness and native/ARIA mapping completeness require human/browser review.
- Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.
Common questions
Does one main candidate prove a well-structured page?
No. It is one source fact. Region purpose,names and actual user navigation still require review.
Is this input sent to a server?
No. The application processes this input inside your browser tab and does not save it to persistent storage.
Keep going with related tools
All accessibility →Heading Outline Auditor
List h1–h6 headings and flag empty text or skipped levels in supplied HTML.
AccessibilityARIA Markup Auditor
Inspect a limited set of declared roles, common ARIA value tokens and local ID references in pasted HTML.
AccessibilityDocument Language and Direction Auditor
Inspect inherited HTML lang/dir declarations over literal text regions with explicit uncertainty.
AccessibilityStatic Focus Order Inspector
Inspect a limited source-order model of explicit tabindex and common native focus candidates.