Compare source HTML, parser-repaired DOM, CSS and layout state, rendered text, accessibility semantics, structured data, and browser-agent observations.
A web page has no single universally authoritative representation: source bytes become a repaired DOM, the DOM and CSSOM produce layout and pixels, accessibility mappings produce a semantic tree, and structured-data parsers build a parallel graph.
The submitted report remains byte-identical. This separate review, checked 2026-08-26, narrows implementation claims and gives visitors a decision path before they generalize from a local result.
Output produced deterministically by the local runtime.
Useful model or subset that must not be mistaken for full conformance.
Conclusion that needs an exact implementation, trust system, model, parser, or human review.
| Question | What the local page can answer | What it does not establish | Next evidence step |
|---|---|---|---|
| What exact source was submitted? | Yes — inspect the preserved raw-source view. | The DOM a browser will repair from it. | Compare with an isolated browser DOM snapshot. |
| Could machine-readable text differ from visible text? | The lab can flag selected static divergence. | Complete computed visibility or accessibility-tree state. | Use live DOM, layout, and AX-tree comparison. |
| Is the fragment safe to execute? | No execution occurs and no safety verdict is issued. | Browser exploitability, CSP behavior, or active-component safety. | Use a hardened disposable browser and application-specific policy. |
Separates raw source, static text, machine attributes, and structured data.
Expected boundary: The lab reports selected differences while explicitly reserving browser-only conclusions.
Open prepared laboratoryNo single view is automatically authoritative. Preserve the source, identify each parser or receiver, and compare their outputs before authorizing a consequential decision.
Original markup, comments, attributes, and scripts.
Tree-construction output after standardized error recovery.
Computed state, box generation, clipping, opacity, overlap, and top-layer behavior.
Text influenced by layout and visibility rather than raw descendants.
Roles, names, states, and relationships mapped for assistive technology and agents.
JSON-LD and metadata graphs that may diverge from visible content.
The workflow preserves evidence before transformation and keeps structural inspection separate from execution, remote verification, or model behavior.
These controls are contextual. They reduce a defined risk; they do not guarantee safety, truth, attribution, or resistance to every adaptive attack.
Use native semantic controls and synchronize visual, focus, and accessibility states.
Treat structured data as an independently auditable representation.
Keep closed subtrees inert rather than merely off-screen or aria-hidden.
Reject remote loads and active content during ingestion.
Use hybrid DOM, accessibility, and geometry checks for browser agents.
Definitions are linked into the site-wide glossary and back to the full report.
The object model representing parsed CSS rules and style sheets.
The resolved CSS values used by layout after cascade and inheritance.
Text derived from layout and visibility rather than raw DOM descendants.
A subtree excluded from interaction, focus navigation, and the accessibility tree.
The computed label identifying an interface object to assistive technology.
An encapsulated DOM subtree attached to a host element.
Standardized tree-construction recovery that changes malformed source into a valid DOM.
A machine-readable semantic graph, commonly JSON-LD, that exists alongside visible page content.
These links are provided for visitors who want the governing specification, paper, framework, or implementation documentation. Links open in a new tab; the site does not fetch them during runtime analysis.
HTML parsing, tree construction, interaction, and rendering requirements.
Normative or first-party specification material.DOM nodes, trees, mutation, and textContent.
Normative or first-party specification material.CSSOM interfaces and resolved style access.
Normative or first-party specification material.Roles, states, and properties.
Normative or first-party specification material.Platform accessibility mappings.
Normative or first-party specification material.Accessible-name computation.
Normative or first-party specification material.Accessibility success criteria.
Normative or first-party specification material.Linked-data syntax embedded in web pages.
Normative or first-party specification material.The full submitted report is preserved byte-for-byte in the governed research library and in durable repository documentation. The laboratory turns selected concepts into deterministic local output without external calls or hidden persistence.
A detailed analysis of source HTML, parser repair, DOM mutation, CSS visibility, accessibility trees, structured data, agent observations, and related document-container parser differentials.
Read governed reportParse a bounded inert HTML fragment and compare raw source, structural text, likely rendered text, accessibility fields, JSON-LD blocks, hidden mechanisms, and sanitized output.
Open bounded laboratory