Interfaces and CSSChecked through WebDiag API

Landmark Structure Analyzer

Get a bounded inventory of semantic and ARIA landmarks, their accessible names, duplicates, and structural conflicts.

  • One safe fetch
  • Up to 150 items
  • No browser runtime
Online tool

Try the tool

Enter a URL: WebDiag will run a safe network check and show the result.

Page URL

Network check through backend

For HTTP/SEO tools, the URL is sent to the WebDiag API, where SSRF protection, DNS/IP policy, and redirect limits are applied.

Reviewed: 2026-07-17
01

How to use it

  1. 1

    Enter a public HTTP/HTTPS URL.

  2. 2

    Run the bounded static HTML scan.

  3. 3

    Review main, repeated landmarks, and distinguishable names.

02

What the tool can do

  • Semantic header, nav, main, footer, aside, form, section, and search candidates.
  • Explicit ARIA roles for banner, navigation, main, contentinfo, complementary, search, form, and region.
  • aria-label, aria-labelledby, duplicate role/name, hidden signals, and nested-main review.
03

Common use cases

  • Reviewing a layout template after a redesign.
  • Finding multiple main landmarks or identically named nav landmarks.
  • Pre-screening before a manual screen-reader audit.
04

How it works inside

Header and footer are treated as page-level candidates only outside sectioning ancestors in the static structure.

Final landmark mapping must be confirmed in the browser accessibility tree.

05

Questions and answers

Why is a section not always a region?

The analyzer treats section as a region candidate only when an accessible name is found.

Does PASS mean WCAG conformance?

No. PASS means the selected static findings were not detected in the fetched HTML.