Inspiration

A page can look beautiful and still leave people outside. An image may have no description, a menu button may have no name, and pale text may disappear into its background. Ghostlight makes those quiet barriers visible and gives the person maintaining the page a clear next action.

What it does

Ghostlight is an accessibility repair workshop for designers, learners, and developers working on self-contained HTML pages. Start with the original Midnight Museum demo or bring your own HTML. Select a finding, understand why it matters, supply a meaningful repair, and see the checks rerun.

The eight focused categories cover language and title presence, image alternatives, form labels, button and link names, heading skips, and text contrast on supported solid backgrounds. The sample page begins with seven deliberate findings. Repairing them reaches zero findings in these checks, then explicitly points to the human review that still remains.

Compare preserves the original page alongside the repaired version. Undo restores the preceding state. Source inspection, sanitized HTML export, and a JSON report make the changes reviewable. The report retains original findings, remaining findings, repair history, and human-review status.

Costume Contest design

The spooky theme has a job: barriers hide in the shadows, a lantern brings them into view, and each repair opens the door a little wider. A quiet museum palette and restrained ghostly details support the workflow. The page preview, explanation, and repair controls remain the focus.

How it was built with Kiro

Development used Kiro CLI 2.37.1 with the requirements, design, tasks, and product steering committed at the repository root under .kiro/. The specifications established static HTML as the scope, reversible repairs as the interaction model, and browser-local processing and honest limitations as constraints.

Kiro read those documents and generated the initial substantive audit/repair engine, color utilities, color tests, and initial structural tests. It ran tests and began fixing failures; service throttling interrupted the session before a completed passing run. Codex then built the interface and integration, reviewed the generated code, corrected observed edge cases, and completed verification. This division is documented in docs/kiro-usage.md and the implementation prompt.

Kiro Web was explored, but the implementation contribution came from Kiro CLI. No hooks, custom agents, Kiro MCP integrations, powers, or property-based testing are claimed. The running application uses deterministic browser checks and makes no AI inference calls.

The demo script was narrated with ElevenLabs, then edited and exported locally in Wondershare Filmora.

Technical implementation

Ghostlight is static HTML, CSS, and JavaScript. DOMPurify sanitizes imported HTML before an isolated iframe preview. Scripts, event handlers, nested frames, external resources, and active media are excluded. The preview has no script permission and retains a restrictive CSP. There is no HTML upload endpoint, database, or account requirement; edits remain in browser memory and are discarded when the page is reloaded or replaced.

The audit engine keeps repair targets stable, reruns findings after each change, and serializes a static export without internal targeting attributes. Happy DOM supports development regression tests; it is not used by the running app.

Challenges and what changed

The difficult cases were the ones that could make a workshop misleading: translucent colors, ancestor opacity, complex backgrounds, hidden text in accessible names, decorative versus meaningful images, nested image-button names, wrapping labels, duplicate IDs, and SVG serialization.

The implementation now composites supported colors, flags unsupported rendering for human review, requires an explicit decorative-image choice, and preserves safe, consistent HTML serialization. Initial synthetic DOM tests were replaced with real DOM tests. Numerical and structural regression tests pass, and the full seven-repair browser journey was verified.

Honest limits and next steps

Ghostlight is a focused static-page workshop, not a WCAG certification or a complete accessibility audit. Descriptions, names, language choice, keyboard use, screen-reader meaning, zoom/reflow, dynamic behavior, and complex rendering need human judgment. Exported HTML is sanitized and static; it does not reproduce a JavaScript application's full behavior.

Next steps would be assistive-technology testing with users, a broader browser matrix, and carefully expanded check coverage. No user-study outcomes or adoption metrics are claimed.

Try it

Open the public workshop, repair the seven Midnight Museum findings, compare the two versions, then inspect and export the result. No credentials are needed.

Built With

Share this project:

Updates

Submission history