The Accessibility export contains the individual Lighthouse accessibility audit data, page identities, site-level accessibility summary, and aggregated audit issues for one Siteimp scan. Unlike Introductory, this report preserves passing, failed, warning, manual-review, informative, and not-applicable outcomes.

Format: siteimp-accessibility-v1
Primary data root: tables
Included tables: pages, lighthouse_reports, scan_accessibility_summary, scan_accessibility_issues.

Common export metadata

All five report formats include the same core envelope. Individual files are generated independently from the scan database; they are not slices of another downloaded JSON file.

PropertyMeaning
export_formatExact format identifier; use it when selecting a parser.
export_typeHuman-readable machine-friendly profile name.
purposeShort description of the intended use.
snapshot_idUUID for the scan represented by this report. Match it when combining scan-specific exports.
websiteWebsite identity and starting URL.
exported_at_utcTime the JSON file was generated, not the time the scan ran.
schema_fingerprintNoncryptographic fnv1a64-... identifier for the database table definitions. It is not a hash of scan results.
related_exportsNames and descriptions of the other available profiles, plus instructions for downloading them. It does not embed the other reports.
export_policyScope, retained evidence, and known omissions for the selected profile.

website contains website_key, website_slug, name, start_url, and registrable_domain. related_exports.available maps each profile name to export_format, purpose, and selected; selected identifies the current report, not a report that has already been downloaded.

JSON text stored in database columns ending in _json is decoded into JSON arrays or objects in table-based exports. Do not parse those fields as JSON strings again. SQL NULL becomes JSON null. Integer columns can represent boolean-style flags (0 and 1); consult the Schema export's create_sql for their constraints. Neither object-property ordering nor numeric row IDs should be used as a durable cross-scan identity.

Structure and table inventory

{
  "export_format": "siteimp-accessibility-v1",
  "export_type": "accessibility",
  "manifest": {
    "included_tables": [
      "pages", "lighthouse_reports",
      "scan_accessibility_summary", "scan_accessibility_issues"
    ],
    "json_text_columns_decoded": true,
    "raw_artifact_files_included": false
  },
  "tables": {
    "pages": [],
    "lighthouse_reports": [],
    "scan_accessibility_summary": [],
    "scan_accessibility_issues": []
  },
  "row_counts": {
    "pages": 0, "lighthouse_reports": 0,
    "scan_accessibility_summary": 0, "scan_accessibility_issues": 0
  }
}

Minimal structural example. The common envelope fields are omitted, and the empty arrays are illustrative rather than a typical completed scan.

TableRows describePrimary way to relate them
pagesCrawled page fetch outcomes and IDs.page_key
lighthouse_reportsOne stored per-page Lighthouse record, where available.page_key
scan_accessibility_summaryAggregate accessibility coverage and results.snapshot_id
scan_accessibility_issuesOne record per aggregated audit finding/inventory item.audit_key, source_audit_id

manifest.included_tables names the tables present. row_counts records the number of exported rows per table. An included table may legitimately have [] and count zero.

Lighthouse audit result semantics

Each lighthouse_reports row has accessibility_audits_json, an object keyed by normalized audit name, such as heading_order or focus_traps. Each audit entry contains source_audit_id, score, and score_display_mode in the current format.

ValueInterpretation
score_display_mode: "binary", score: 0Failed binary audit.
score_display_mode: "binary", score: 1Passed binary audit.
score_display_mode: "manual"Needs manual assessment; not a confirmed defect.
score_display_mode: "notApplicable"Audit not applicable in the measured context; not a pass or failure.
score_display_mode: "informative"Informational outcome; not automatically a confirmed failure.

Not every audit necessarily uses a binary score. Inspect the stored score_display_mode and score together. Lighthouse category accessibility_score and other category scores use a 0–100 scale, while an individual binary audit score may be 0 or 1.

For example, a focus_traps entry marked manual is not evidence that a page has a focus trap. A heading_order entry marked binary with a score of 0 does establish that the audit failed on that page.

Per-page and aggregate evidence

tables.pages[]

Use page_key with requested_url, final_url, status_code, fetch_error, robots_blocked, fetched_at, fetch_ms, redirect_count, and the content and artifact identity fields. This is page-fetch evidence, not the accessibility diagnosis itself.

tables.lighthouse_reports[]

Important fields include:

FieldMeaning
page_keyJoin key to the page identity.
lighthouse_versionLighthouse version for this stored report.
lighthouse_modeRecorded mode, such as desktop.
requested_url, final_url, fetch_timeAudited URL and Lighthouse observation time.
performance_score, accessibility_score, best_practices_score, seo_scoreCategory scores on the 0–100 scale, nullable.
accessibility_audits_jsonDecoded map of individual accessibility audits, including N/A and manual results.
audits_summary_jsonDecoded summary of selected audits and their display modes.
metrics_jsonDecoded performance metrics, such as paint and blocking-time measurements, as available.
source_artifact_idReference to a stored source artifact; raw artifact contents are not included here.
structured_data_passNullable structured-data pass flag, not a replacement for manual validation.

tables.scan_accessibility_summary[]

This table contains site-level fields including scanned_pages, pages_with_lighthouse, pages_without_lighthouse, average_accessibility_score, lowest_accessibility_score, highest_accessibility_score, total_audit_results, total_failed_audits, total_warning_audits, total_manual_audits, total_informative_audits, total_not_applicable_audits, total_passed_audits, affected_page_count, site_wide_issue_count, recurring_issue_count, and isolated_issue_count.

It also carries top_issues_json, worst_pages_json or other stored summary fields where defined by the current schema, plus derivation/version metadata. The full column names and types are in the Schema export.

tables.scan_accessibility_issues[]

Each row summarizes one audit across recorded pages. Its important fields are:

FieldMeaning
audit_key, source_audit_idSiteimp audit key and source Lighthouse identifier.
affected_page_countPages classified as affected by the aggregated issue/inventory entry.
failed_page_count, warning_page_countConfirmed failed or warning page outcomes.
manual_page_count, informative_page_countManual or informational page outcomes.
passed_page_count, not_applicable_page_countPass and not-applicable page outcomes.
affected_pages_jsonDecoded array of supporting page identities, statuses and scores, where present.
display_modes_jsonDisplay modes represented in this aggregated record.
evidence_summary_jsonDecoded aggregated status counts and supporting evidence.
impact_hint, likely_scope_hintSiteimp's classification hints, not a guarantee of root cause.

An affected_page_count of 12 does not by itself imply 12 failures; always inspect the status-specific counters. The report retains full per-page evidence even for all-pages manual-review entries.

Example: list failed accessibility audits by URL

import json

with open("accessibility.json", encoding="utf-8") as file:
    report = json.load(file)

assert report["export_format"] == "siteimp-accessibility-v1"
pages = {p["page_key"]: p.get("final_url") or p["requested_url"]
         for p in report["tables"]["pages"]}

for lighthouse in report["tables"]["lighthouse_reports"]:
    url = pages.get(lighthouse["page_key"], lighthouse["page_key"])
    for audit_name, audit in lighthouse["accessibility_audits_json"].items():
        if (audit.get("score_display_mode") == "binary"
                and audit.get("score") == 0):
            print(url, audit_name)

This example enumerates failed binary audits, not manual reviews. It does not claim to reproduce every future Lighthouse scoring mode.

Scope, privacy, and compatibility

The Accessibility export does not contain sitemap provenance, the full internal-link graph, database DDL, or raw Lighthouse artifact files. No individual audit is removed merely because its status is notApplicable. Match snapshot_id when combining this file with other scan exports and use page_key for page relationships within the scan. For current column types and constraints, consult the Schema export.