The 44 controls / TS29
TS29 · HTML and semantics
Essential content remains available when scripts or styles fail.
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
- Flows whose essential content and navigation are defined.
- How to check
- Test source HTML, disabled JavaScript and degraded network conditions.
- Expectation
- Blocked-script and degraded-style scenarios preserve declared functions or an actually tested fallback.
- Evidence to retain
- Primary information and navigation remain available, or a fallback is documented.
- Non-applicability
- No relevant web flow, with a justification.
- Limitations
- Acceptable degradation depends on the component’s function.
- 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.