OPEN INSTRUMENTS

SEMANTIC HTML · ARCHIVED RESULTS

Semantic HTML.
Compare what tools preserve.

The same text. One markup change.
Two outputs to inspect, with evidence.

Explore an archived run from 20 September 2026, re-evaluated on 21 September. No extraction runs during your visit.

EXPLORE THE CONTROLLED CORPUS

Table

readability-lxml 0.8.4.1 · Extractor / reading tool · English document

All 42 comparisons

Values must match exactly in the same row. An XML caption is not a column header; a Markdown table does not prove the input’s HTML semantics. Test scope.

A

VARIANT A

Headers with th + scope

Output produced

Expected value row : Exact values, in order · Column headers : Explicit relationship · Row header : Explicit relationship. Source

01 · The HTML change

<table><caption>Synthetic measurements</caption><thead><tr><th class="case-cell" scope="col">Indicator</th><th class="case-cell" scope="col">Unit</th><th class="case-cell" scope="col">Period</th><th class="case-cell" scope="col">Value</th></tr></thead><tbody><tr><th class="case-cell" scope="row">Response time</th><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table>

Exact input excerpt · Original HTML ↓

02 · What the tool produces HTML

…
<table><caption>Synthetic measurements</caption><thead><tr><th class="case-cell" scope="col">Indicator</th><th class="case-cell" scope="col">Unit</th><th class="case-cell" scope="col">Period</th><th class="case-cell" scope="col">Value</th></tr></thead><tbody><tr><th class="case-cell" scope="row">Response time</th><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></main></body></div>

Excerpt identified by the corrected evaluator. Full output below.

03 · The documented observation

Expected value row
Exact values, in order
Column headers
Explicit relationship
Row header
Explicit relationship
Output structure
Present

Verdict source: results.json · table-en-1 / readability_lxml

Inspect the full evidence

The verdicts above come from corrected results.json. The raw file’s evaluation fields are historical and are not authoritative here.

results.json/cases/8/evaluation/relation/readability_lxml

Corrected verdict, unchanged
{
  "status": "ok",
  "tool_class": "content_extractor",
  "format": "html",
  "table_structure": "present",
  "expected_data_row": "exact_values_in_order",
  "column_header_relation": "explicit",
  "row_header_relation": "explicit",
  "column_labels": [
    "Indicator",
    "Unit",
    "Period",
    "Value"
  ],
  "data_values": [
    "Response time",
    "seconds",
    "May 2026",
    "1.8"
  ],
  "evidence": {
    "header_row": "<th class=\"case-cell\" scope=\"col\">Indicator</th><th class=\"case-cell\" scope=\"col\">Unit</th><th class=\"case-cell\" scope=\"col\">Period</th><th class=\"case-cell\" scope=\"col\">Value</th>",
    "data_row": "<th class=\"case-cell\" scope=\"row\">Response time</th><td class=\"case-cell\">seconds</td><td class=\"case-cell\">May 2026</td><td class=\"case-cell\">1.8</td>",
    "table_excerpt": "<table><caption>Synthetic measurements</caption><thead><tr><th class=\"case-cell\" scope=\"col\">Indicator</th><th class=\"case-cell\" scope=\"col\">Unit</th><th class=\"case-cell\" scope=\"col\">Period</th><th class=\"case-cell\" scope=\"col\">Value</th></tr></thead><tbody><tr><th class=\"case-cell\" scope=\"row\">Response time</th><td class=\"case-cell\">seconds</td><td class=\"case-cell\">May 2026</td><td class=\"case-cell\">1.8</td></tr></tbody></table>"
  },
  "output_field": "additional_extractors.readability_lxml.html",
  "output_sha256": "dd0d4776a404ecb7e226e3cda9b66fd53711dbe5a979e0f0d0bc58d141dc645c",
  "source_column_headers_explicit": true
}
Complete studied output field

additional_extractors.readability_lxml.html

<div><body id="readabilityBody"><main><article><h1>Offline protocol for preserving relationships</h1><p>This synthetic document compares two markups while text, order, classes and surroundings remain identical. The data are fictional and describe neither Edikka nor a client.</p><h2>Synthetic measurements</h2><table><caption>Synthetic measurements</caption><thead><tr><th class="case-cell" scope="col">Indicator</th><th class="case-cell" scope="col">Unit</th><th class="case-cell" scope="col">Period</th><th class="case-cell" scope="col">Value</th></tr></thead><tbody><tr><th class="case-cell" scope="row">Response time</th><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></main></body></div>
Archived version and options

readability-lxml 0.8.4.1 · Execution 2026-09-20

{
  "version": "0.8.4.1",
  "configuration": "No configuration field in this output; consult the archived runner."
}

Archived runner · Python options

SHA-256 hashes
HTML input
374211644b0d1ad2d4ae9647d84e7e3e518ff392b9f4aaa108e438677c2b05da
Evaluated output field
dd0d4776a404ecb7e226e3cda9b66fd53711dbe5a979e0f0d0bc58d141dc645c

Complete raw output file ↗

B

VARIANT B

Ordinary td cells

Output produced

Expected value row : Exact values, in order · Column headers : Relationship not demonstrated · Row header : Relationship not demonstrated. Source

01 · The HTML change

<table><caption>Synthetic measurements</caption><thead><tr><td class="case-cell">Indicator</td><td class="case-cell">Unit</td><td class="case-cell">Period</td><td class="case-cell">Value</td></tr></thead><tbody><tr><td class="case-cell">Response time</td><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table>

Exact input excerpt · Original HTML ↓

02 · What the tool produces HTML

…
<table><caption>Synthetic measurements</caption><thead><tr><td class="case-cell">Indicator</td><td class="case-cell">Unit</td><td class="case-cell">Period</td><td class="case-cell">Value</td></tr></thead><tbody><tr><td class="case-cell">Response time</td><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></main></body></div>

Excerpt identified by the corrected evaluator. Full output below.

03 · The documented observation

Expected value row
Exact values, in order
Column headers
Relationship not demonstrated
Row header
Relationship not demonstrated
Output structure
Present

Verdict source: results.json · table-en-2 / readability_lxml

Inspect the full evidence

The verdicts above come from corrected results.json. The raw file’s evaluation fields are historical and are not authoritative here.

results.json/cases/9/evaluation/relation/readability_lxml

Corrected verdict, unchanged
{
  "status": "ok",
  "tool_class": "content_extractor",
  "format": "html",
  "table_structure": "present",
  "expected_data_row": "exact_values_in_order",
  "column_header_relation": "not_explicit",
  "row_header_relation": "not_explicit",
  "column_labels": [
    "Indicator",
    "Unit",
    "Period",
    "Value"
  ],
  "data_values": [
    "Response time",
    "seconds",
    "May 2026",
    "1.8"
  ],
  "evidence": {
    "header_row": "<td class=\"case-cell\">Indicator</td><td class=\"case-cell\">Unit</td><td class=\"case-cell\">Period</td><td class=\"case-cell\">Value</td>",
    "data_row": "<td class=\"case-cell\">Response time</td><td class=\"case-cell\">seconds</td><td class=\"case-cell\">May 2026</td><td class=\"case-cell\">1.8</td>",
    "table_excerpt": "<table><caption>Synthetic measurements</caption><thead><tr><td class=\"case-cell\">Indicator</td><td class=\"case-cell\">Unit</td><td class=\"case-cell\">Period</td><td class=\"case-cell\">Value</td></tr></thead><tbody><tr><td class=\"case-cell\">Response time</td><td class=\"case-cell\">seconds</td><td class=\"case-cell\">May 2026</td><td class=\"case-cell\">1.8</td></tr></tbody></table>"
  },
  "output_field": "additional_extractors.readability_lxml.html",
  "output_sha256": "061bafa129843240a20b1ce58d03f912d9e027b1f776484d38b3aea44838045b",
  "source_column_headers_explicit": false
}
Complete studied output field

additional_extractors.readability_lxml.html

<div><body id="readabilityBody"><main><article><h1>Offline protocol for preserving relationships</h1><p>This synthetic document compares two markups while text, order, classes and surroundings remain identical. The data are fictional and describe neither Edikka nor a client.</p><h2>Synthetic measurements</h2><table><caption>Synthetic measurements</caption><thead><tr><td class="case-cell">Indicator</td><td class="case-cell">Unit</td><td class="case-cell">Period</td><td class="case-cell">Value</td></tr></thead><tbody><tr><td class="case-cell">Response time</td><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table><p>The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.</p></article></main></body></div>
Archived version and options

readability-lxml 0.8.4.1 · Execution 2026-09-20

{
  "version": "0.8.4.1",
  "configuration": "No configuration field in this output; consult the archived runner."
}

Archived runner · Python options

SHA-256 hashes
HTML input
f047171076d291106cd77b19fe1195a11b287e101144a134317cf2a3f64dd654
Evaluated output field
061bafa129843240a20b1ce58d03f912d9e027b1f776484d38b3aea44838045b

Complete raw output file ↗

Identical text and isolated intervention within this pair, according to the protocol witnesses. Translations are not independent observations. View pair witnesses.

LOOK FURTHER

Every result has a scope.

These observations do not rank tools. They do not measure overall accessibility, search ranking, or understanding or citation by AI.

Claims excluded by the protocol
The eight real pagesA separate corpus, with documented instability. ↗Evaluator counter-testsChecking evaluation without rerunning extractors. ↗Reproduce the runsA local procedure, separate from this interface. ↗