Static content: review observed structure and rendered completeness

The auditor observes H1 elements, regex-based H2/question patterns, summary-like text, the first eligible static paragraph and static homepage text length. Several patterns use lightweight text extraction rather than a browser.

The first paragraph is not necessarily the opener. Summary keywords do not prove a summary block. Short static text does not prove a JavaScript shell, and question headings or TL;DR sections are not universal requirements. Rendered completeness is not tested.

Compare source HTML with the rendered page if content appears missing. Evaluate headings, summaries and paragraphs against page purpose and reader needs. Keep concise utility or navigation pages concise; do not add headings or padding solely to satisfy a pattern.

<h1>Service status</h1>
<p>All services are operational.</p>

A short page can serve its purpose without H2 headings, a FAQ or a TL;DR. Static observations alone do not establish adequacy.

Public measurement separates Confirmed issue, Advisory, Unknown, Not applicable and Observed pass. An observed pass applies only to an explicit bounded rule; absence of an emitted failure is not a pass. Missing prerequisites do not earn repair credit.

Start 100. Current purpose-dependent heading, summary, paragraph and text-length observations do not deduct. A direct auditor call without a homepage returns 0; a public audit instead fails when homepage retrieval fails.

Legacy values are clamped to 0..100 and rounded. They are not readiness certification, risk indicators or predicted citation outcomes. Method changes do not rewrite historical records.

The observations above describe the local implementation, not guarantees from these sources. Protocol and provider documents help interpret purpose and perform checks this audit does not implement.

• HTML headings and sections specification