Prompt · Intermediate

Prompt to audit semantic HTML

Review an existing page for element meaning, landmarks, headings, names, forms, links, and progressive structure without scoring theater.

Author: Editorial team
Reviewer: Publication review pending
Review tier: 180-day

Version 1.0.0 · code-review

Variables

[PAGE_MARKUP] · Page markup: The rendered or source HTML with secrets removed. Required.

Expected output

Page Purpose
Findings
Evidence
Patch
Remaining Tests

Common failures

Replacing every div
Unsupported conformance claims
Cosmetic findings

Compatible modes: Chat, Agent, Ide Assistant

Audit this page markup for semantic HTML:

[PAGE_MARKUP]

First infer the page purpose and content hierarchy. Then review document
language, title context, landmarks, heading order, sections, articles, lists,
tables, links versus buttons, images, form names, and source order.

For each material finding, provide severity, exact markup, user consequence,
the relevant standard or guidance, and the smallest corrected markup. Do not
replace every div when no semantic element fits. Do not claim WCAG conformance
or screen-reader testing from static markup alone.

Return a corrected sample, a list of behavior requiring browser or assistive
technology testing, and no numeric “semantic score.”

Complete prompt

Audit this page markup for semantic HTML:

[PAGE_MARKUP]

First infer the page purpose and content hierarchy. Then review document
language, title context, landmarks, heading order, sections, articles, lists,
tables, links versus buttons, images, form names, and source order.

For each material finding, provide severity, exact markup, user consequence,
the relevant standard or guidance, and the smallest corrected markup. Do not
replace every div when no semantic element fits. Do not claim WCAG conformance
or screen-reader testing from static markup alone.

Return a corrected sample, a list of behavior requiring browser or assistive
technology testing, and no numeric “semantic score.”

Verification checklist

Inspect the browser accessibility tree, validate corrected syntax, navigate by headings and landmarks, and confirm buttons and links match actual behavior.

Follow-up prompts

Ask the reviewer to separate confirmed source issues from runtime questions.