Presentational–Semantic Mismatch¶
Core Idea¶
Presentational–Semantic Mismatch occurs when an artifact's rendered or human-facing layer carries distinctions that its underlying explicit, structured, or machine-consumable representation does not encode. A human reading the presentation sees headings, grouping, status, hierarchy, or exceptions; a consumer restricted to the model receives a different or impoverished structure. The defect is silent because the presentation can look complete while the model passes syntactic checks.
Broad Use¶
- Accessible interfaces: visual roles and states are absent from the accessibility tree.
- Documents: font size or whitespace carries headings that the document structure does not mark.
- Spreadsheets: color or placement carries categories and exceptions absent from typed values or formulas.
- Charts and dashboards: visual encoding communicates distinctions not exposed in underlying data or annotations.
- APIs and schemas: prose or examples carry constraints the machine-readable contract cannot validate.
Clarity¶
The abstraction separates a content omission from a layer divergence. The information may be present for one consumer and absent for another because the two consume different representations. Pixel-level correction cannot repair a defect in the semantic model, and a syntactically valid model does not prove semantic parity with the presentation.
Manages Complexity¶
Many surface bugs reduce to a parity audit: enumerate the distinctions carried by the presentation, inspect whether the semantic model encodes each one, and test the consumers that read only that model. The repair family narrows to moving load-bearing meaning into explicit structure and maintaining the layers as one invariant.
Abstract Reasoning¶
Identify the two representations and the consumers bound to each. Compare roles, relations, hierarchy, state, and exceptions across the layers. Any distinction present only in presentation predicts a failure for model-bound consumers. Repair the semantic layer, then re-test through that consumer rather than through visual review.
Knowledge Transfer¶
The roles travel unchanged: a presentation, an explicit model, a meaning-bearing distinction, a consumer restricted to one layer, and silent divergence. HTML and ARIA, PDF tags, spreadsheet types, chart metadata, and API schemas are local carriers of the same structure.
Example¶
A spreadsheet uses red fill to mark values excluded from totals but stores no exclusion flag. A human follows the color; an export process sums every row. The values are present in both views, but the exclusion semantics live only in presentation, so the machine consumes a different dataset.
Relationships to Other Abstractions¶
Current abstraction Presentational–Semantic Mismatch Prime
Parents (1) — more general patterns this builds on
-
Presentational–Semantic Mismatch is a kind of Representational Structure Mismatch Prime
Presentational–Semantic Mismatch is the species in which one presentation carries a task-relevant relation that a parallel explicit semantic representation omits.
Children (1) — more specific cases that build on this
-
Screen-Reader Ambiguity Domain-specific is a kind of Presentational–Semantic Mismatch
Screen-Reader Ambiguity is Presentational–Semantic Mismatch specialized to visual interface structure missing or wrong in the accessibility tree consumed by assistive technology.
Hierarchy path (1) — routes to 1 parentless root
- Presentational–Semantic Mismatch → Representational Structure Mismatch → Representation → Abstraction
Not to Be Confused With¶
- Missing data: content absent from every representation.
- Representation: the parent relation; the mismatch is a failure of parity between layered representations.
- Formatting error: presentation may be visually correct while the semantic model is wrong.
- Interoperability: systems may exchange the model successfully and still exchange the wrong meaning because presentation-only distinctions were never encoded.
Notes¶
Authored when Screen-Reader Ambiguity exposed a missing cross-domain parent shared by accessibility trees, tagged documents, spreadsheets, and machine-readable schemas. Queued for house-style harmonization and citation verification.