The 44 controls / TS26
TS26 · JavaScript and rendering
Resources required for rendering are neither blocked nor failing.
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)
- http, render, robots, intent
- When it applies
- Resources needed to render the tested templates.
- How to check
- Inspect network activity, robots rules, CSP and console errors on priority templates.
- Expectation
- No tested critical resource is prevented by network error, robots policy or CSP; console and network evidence are retained.
- Evidence to retain
- Critical resources accessible and no error removes essential content.
- Non-applicability
- No dependent rendering resource, supported by an inventory.
- Limitations
- An error-free console does not prove indexing.
- 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.