TS28Content and rendering

Is the document understandable without its appearance?

The document exposes an understandable HTML structure independently of appearance.

Prepare evidence

In the app: Evidence import
You provide: HTML and content structure
Allow for: Depends on evidence needed

Prepare evidence

Understand

A structured document. A clear subject.

The document exposes an understandable HTML structure independently of appearance.

TSEP protocol criterion

TSEP compares semantic landmarks with declared content and journeys. This check is not a complete accessibility certification.

The rules and limits of this check are detailed at the bottom of this guide.

Check

Headings and regions. An order that makes sense.

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

Inspect HTML structure and the browser accessibility tree. Navigate headings, links and landmarks using the keyboard, then compare reading order with the content’s meaning.

Evidence to retain

Logical structure, one identifiable main subject and accessible components.

What this result covers

Syntax validity alone proves neither quality nor relevance.

Act

Structure the content. Clarify the reading.

Fix hierarchy and semantic elements to make the topic and navigation explicit.

Recheck

Without the styling. Does meaning remain?

After correction, gather new evidence with the same scope and expectations. Retain both dated observations to compare what changed.

Your reference points

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: Fix hierarchy and semantic elements to make the topic and navigation explicit.
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

WHATWG — HTML Living Standardhtml.spec.whatwg.org · new tab

Detailed method and rules2 rules

Control method and criteria

Method
Inspect title, language, main landmark, heading levels, links and labels on a sample.

Acceptance criteria
Title, language, structure, navigation and labels match the content and its use; human review is recorded without an accessibility certification.

Non-applicability
No relevant HTML document.

Detailed rules

TS28-A01 · Native source and supplied DOM structure

Protocol assessment mode : assisted, with supplied evidence and declarations. App availability is shown on the control card.

Scope
Prior finite TS28 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
Compare source and supplied serialization: title, language, declared main landmark, ordered headings, links and labels. H1 count follows the plan.

Acceptance criteria
Structures agree with the prior plan; qualified structural conflicts fail.

When the result remains inconclusive
Absent source/DOM, undeclared language, ambiguous tree or unqualified visual context: 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.

TS28-A02 · Meaning and navigation review

Protocol assessment mode : manual. App availability is shown on the control card.

Scope
Prior finite TS28 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
Reuse attributed structural facts and require a distinct bound review of title/language adequacy, hierarchy, main subject, navigation and labels in declared use.

Acceptance criteria
Facts are qualified and a reasoned judgment supports meaning and use; evidenced contradiction fails.

When the result remains inconclusive
Parser output alone, an unbound review or insufficient originals are not enough: 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.

Rule version 0.3.0-draft.4 · Public protocol reference · Versioned source

Put it into practice

← Back to controls