social links without a static accessible-name signal
Five repeated footer links appeared on each of the three National Park Service pages.
Public evidence · 13 August 2026
Accessibility signals,
open to inspection.
A reproducible static-markup baseline across six public nonprofit and civic pages—built for Project Keystone’s first accessibility pilot.
2organizations
6/6pages completed
48signals to confirm
6/6stable reruns
01
What the baseline found
Patterns worth a closer look.
These are conservative signals from public HTML, not confirmed defects. Each item needs browser and assistive-technology review before remediation.
image elements without an alt attribute
Observed on Wikimedia Foundation’s “What we do” page; decorative intent must be checked manually.
moderate hierarchy or duplicate-ID signals
Heading jumps and repeated IDs can affect navigation or references, subject to browser confirmation.
Page-level ledger
48 total signals| Organization | Public page | Signals | Open source page |
|---|---|---|---|
| Wikimedia Foundation | Home | 8 | Open ↗ |
| Wikimedia Foundation | Who we are | 7 | Open ↗ |
| Wikimedia Foundation | What we do | 14 | Open ↗ |
| National Park Service | Agency accessibility | 6 | Open ↗ |
| National Park Service | Program index | 6 | Open ↗ |
| National Park Service | Program about | 7 | Open ↗ |
02
Bounded by design
Small scope.
Traceable output.
The runner makes one public HTTPS GET per allowlisted page, stores no raw page HTML, and evaluates eleven documented static checks.
Select
Two public-interest organizations, three representative pages each, with explicit non-goals.
Observe
Public markup only. No crawl, authentication, interaction, submission, or protected paths.
Reproduce
A clean second run matched all six content hashes and all six deterministic category counts.
Verify
Twenty automated release checks validate scope, outputs, hashes, limitations, and safety declarations.
03
Evidence package
Inspect every claim.
Results, rerun comparison, source, release metadata, and lessons are published as static files with SHA-256 checksums.
AuditMap question workflow demoInteractive prototype
13 tests · 7 needsQuestion workflow acceptance reportMarkdown9e3d7058…c53bcabQuestion workflow snapshotJSONb9c87b29…62bb714Question workflow implementation specMarkdown40147689…c594a2aQuestion workflow review queueJSON9edb8649…54a7a07Question workflow exact sourceZIPfb3583a6…12b4759AuditMap 50-park reportMarkdown49c66777…f0a8198AuditMap detailed recordsJSON · 50 recordse1c0959a…436fdceAuditMap import tableCSV87349ab3…344f23fAuditMap review queueJSON · 62 items50b53406…6749dfaAuditMap release manifestJSON9a6afc6c…eaf6a49AuditMap exact sourceZIP88aeee48…a0ac6b7Readiness panel copyMarkdown7e06b105…b3a6aeReadiness copy deckJSONbb13f66a…54daffReadiness copy releaseJSON81 checksReadiness copy sourceZIPfce268b8…45260fCommunity review rubricMarkdown01ba2175…a2eabThree example reviewsMarkdownd2d5d925…ddbb8Rubric releaseJSON26 checksRubric sourceZIPf70d422b…cde71Full reportMarkdowndd110d4f…bd7b3bCandidate manifestJSONcdc1bfe5…0983Primary resultsJSON9e6b9efb…f9a8Clean rerunJSON30a231f4…d1f1ReproducibilityJSON98635f2a…e8eLessons learnedMarkdowndeaac7f5…579Release manifestJSONa4ffe028…d83Exact sourceZIPbee582f2…65d4