TS29Content and rendering
Content and renderingDoes essential content survive script failure?
Essential content remains available when scripts or styles fail.
Prepare evidence
- In the app
- Evidence import
- You provide
- Workflows and failure conditions
- Allow for
- Depends on evidence needed
In the app
You provide
Allow forUnderstand
A script fails. Does the essential remain?
Essential content remains available when scripts or styles fail.
According to Google
JavaScript rendering is a separate stage from fetching HTML. The fallback behavior expected for visitors is a project resilience choice.
Check
Disable the script. Observe the essentials.
In TSEP Control
You import evidence for this control. The engine assesses it within the declared scope; missing items remain visible.
Your contribution
Define the scope and expectations before collection. Gather the items below and supply the requested reviews.
With your own tools
In browser tools, disable JavaScript or block a critical resource in your test environment. Check that planned fallback content and actions remain usable.
Evidence to retain
Primary information and navigation remain available, or a fallback is documented.
What this result covers
Acceptable degradation depends on the component’s function.
Act
A usable fallback. Even when things fail.
Provide fallback content or a fallback workflow for essential functions.
Recheck
The same failure. A usable journey?
After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.
To go further.
Statuses, sources and method.
Understand the statusesC · NC · NT · NA
The same legend in guides, analysis and demo. Each status depends on the control’s evidence and rules.
- C · Verified
- The criterion is met within the assessed scope. Keep dated evidence for the next comparison.
- NC · To correct
- Provide fallback content or a fallback workflow for essential functions.
- NT · Not established
- Evidence or confirmations are insufficient to conclude. Supply what is missing; this status does not establish an SEO error.
- NA · Not applicable
- The control does not apply to the scope under its rules, with a retained justification. Missing evidence alone does not make it non-applicable.
Sources and references1 reference
Detailed method and rules2 rules
Control method and criteria
Method
Test source HTML, disabled JavaScript and degraded network conditions.
Acceptance criteria
Blocked-script and degraded-style scenarios preserve declared functions or an actually tested fallback.
Non-applicability
No relevant web flow, with a justification.
Detailed rules
TS29-A01 · Blocked-script scenario and tested fallback
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Prior finite TS29 population under render-transport-v1; see docs/render-transport-evidence.md.
Evidence
Exact originals, plan and dates/context, fingerprints, diagnostics and reasoned review bound to the entire dossier. Kinds: html, render, intent.
Method
Read source and a supplied state explicitly marked scripts-blocked; compare every essential content/link or the prior fallback within that same state. Require action and operation review.
Acceptance criteria
All main expectations or all tested fallback expectations are supported. Qualified failures of both main and fallback fail; text alone does not establish function.
When the result remains inconclusive
Normal condition, partial capture, merely described fallback, hidden context or missing review: NT.
Non-applicability
No atomic NA. Empty population or claimed absent domain without evidence remains NT in this profile.
Assumptions
Supplied unauthenticated provenance, inventory, browser state, conditions and judgment; two static HTML readings are not two navigations. TLS trust depends on supplied roots.
Limitations
No real audit inferred from synthetic cases. No indexing, ranking, global conformity, accessibility certification, exhaustive security or universal browser trust. Reviews may be wrong and captures may omit states.
TS29-A02 · Degraded-style scenario and tested fallback
Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.
Scope
Prior finite TS29 population under render-transport-v1; see docs/render-transport-evidence.md.
Evidence
Exact originals, plan and dates/context, fingerprints, diagnostics and reasoned review bound to the entire dossier. Kinds: html, render, intent.
Method
Apply the same examination in an explicitly styles-degraded state with action observations and a bound review. Script disabling does not qualify this scenario.
Acceptance criteria
Essential functions or tested fallback remain supported in this distinct scenario.
When the result remains inconclusive
Missing degraded-style scenario, fallback evidence or attributed judgment: NT.
Non-applicability
No atomic NA. Empty population or claimed absent domain without evidence remains NT in this profile.
Assumptions
Supplied unauthenticated provenance, inventory, browser state, conditions and judgment; two static HTML readings are not two navigations. TLS trust depends on supplied roots.
Limitations
No real audit inferred from synthetic cases. No indexing, ranking, global conformity, accessibility certification, exhaustive security or universal browser trust. Reviews may be wrong and captures may omit states.
Rule version 0.3.0-draft.4 · Public protocol reference · Versioned source
Put it into practice
Workflows and their failure conditions.