Home /Modules/html-spec/APPRAISAL-structural-elements.md

APPRAISAL-structural-elements.md

html-spec/APPRAISAL-structural-elements.md · 191 line(s) · markdown

Structural Integrity Appraisal — div, span, table

An appraisal of HTML's three core structural primitives against the capabilities assumed of international web technology, with a safeguarding checklist. Grounded in the specifications archived under specifications/: the HTML 3.2 / 4.01 / XHTML DTDs and the WHATWG HTML Living Standard source.

Context. The concern raised was that HTML "has become unwieldy." The finding below is the opposite of what that fear implies: the three structural elements are stable, small, and well-specified. What is unwieldy is not the elements — it is the practice of using div/span as a substitute for meaningful structure. The checklist targets exactly that.


1. Executive appraisal

ElementIntroducedSemantic roleInternational supportState
divHTML 3.2 (1997)Generic block container; "no special meaning at all"dir + lang since HTML 4.0✅ Great
spanHTML 4.0 (1998)Generic inline containerdir + lang since HTML 4.0✅ Great
tableHTML 3.2 (flat) → HTML 4.0 (full model)Tabular data (NOT layout)dir + lang + scope/headers✅ Great, with conditions

Verdict: coherent and fit for purpose. All three are present, stable across 25+ years, and fully carry the internationalization attributes. The only missing capabilities are ones that by design do not belong to HTML at all — visual sizing and layout live in CSS (see §5).


2. What the archived specs actually say

div

span

table


3. International technology — capability matrix

"Assumed functionality of international technology" = the capabilities a globally-deployed page is expected to have: bidirectional text, language tagging, Unicode, assistive-tech semantics.

CapabilitydivspantableNotes
Unicode content (UTF-8)✅✅✅Character set is a document-level guarantee since HTML 2.0 / 4.0
Language tagging (lang / xml:lang)✅ (4.0+)✅ (4.0+)✅BCP 47 language codes
Bidirectional text (dir="ltr|rtl")✅ (4.0+)✅ (4.0+)✅Essential for Arabic, Hebrew, etc.
dir="auto" (heuristic direction)✅ (HTML5+)✅✅Added by the Living Standard; not in 4.01
Isolation of bidi runs (<bdi>, unicode-bidi: isolate)n/ause <bdi>n/aspan alone does not isolate; use <bdi> or CSS
Assistive-tech structure⚠️ none intrinsically⚠️ none✅ scope, headers, caption, summarydiv/span convey no semantics (see §4)
Logical reading order✅ (source order)✅✅Preserved as long as CSS does not reorder visually (see §5 risk)

Great: language + direction support on all three is complete from HTML 4.0 onward, and the Living Standard adds dir="auto". Condition: div/span are presentation/scripting hooks with zero semantics — they are international-text-capable but accessibility-neutral. A table is the only one of the three that carries structural meaning assistive technology can use. Missing (by design, not a defect): neither div nor span isolates a bidi run on its own; that is the job of <bdi> or CSS unicode-bidi.


4. Conditions: great / missing / unsupported

✅ Great (works as assumed)

⚠️ Missing / conditional

❌ Unsupported (and correctly so — out of scope for HTML)


5. "Can divs resize dynamically?" — the direct answer

Not through HTML. Yes — richly — through CSS, which is the correct layer for it.

Risk flag for the safeguarding checklist: CSS layout can visually reorder flex/grid children away from source order. That breaks logical reading order for screen readers and keyboard users. Safeguard: keep DOM source order meaningful; never rely on order/grid placement to convey sequence.


6. Safeguarding checklist (page-structure integrity)

Use this as a review gate for any page or component.

Semantic structure

Tables

Internationalization

Layout / dynamic resize (CSS layer)

Validation / conformance


7. Bottom line

The structural primitives are not the source of unwieldiness — they are small, stable, and internationally capable. div dates to 1997, span to 1998, the full accessible table to 1998, and all three remain valid and unchanged in today's Living Standard. Dynamic resizing is fully available, delivered by CSS exactly as the architecture intends. The real risk is discipline: generic-container overuse and layout misuse of tables. The checklist in §6 is the safeguard for keeping page structure coherent.