The 44 controls / TS28
TS28 · HTML and semantics
The document exposes an understandable HTML structure independently of appearance.
Protocol wording · 0.1.0-draft.28 · Documentation view; no website assessment.
Control rule version : 0.1.0-draft.19
Reading guide: start with applicability and required evidence, then read expectations together with their limitations. Understand C, NC, NT and NA outcomes · Prepare a dossier
Expectations and evidence
- Required inputs (protocol identifiers)
- html, render, intent
- When it applies
- HTML documents in scope.
- How to check
- Inspect title, language, main landmark, heading levels, links and labels on a sample.
- Expectation
- Title, language, structure, navigation and labels match the content and its use; human review is recorded without an accessibility certification.
- Evidence to retain
- Logical structure, one identifiable main subject and accessible components.
- Non-applicability
- No relevant HTML document.
- Limitations
- Syntax validity alone proves neither quality nor relevance.
- Outcome clarification
- C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.
- Reference scope
- Technical reference; the TSEP acceptance rule remains an editorial proposal.
Atomic rules
This control is documented in the protocol. This version does not yet attach executable atomic rules to it.