<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Oldlee</title>
    <description>The latest articles on DEV Community by Oldlee (@laoleedesign).</description>
    <link>https://dev.to/laoleedesign</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4178208%2F3f55d89b-564b-4d00-a865-d2cca4b0689c.png</url>
      <title>DEV Community: Oldlee</title>
      <link>https://dev.to/laoleedesign</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/laoleedesign"/>
    <language>en</language>
    <item>
      <title>I built an accessibility tool that haunts your designs — with Kiro, for Kiroween 2026</title>
      <dc:creator>Oldlee</dc:creator>
      <pubDate>Sat, 31 Oct 2026 08:22:26 +0000</pubDate>
      <link>https://dev.to/laoleedesign/i-built-an-accessibility-tool-that-haunts-your-designs-with-kiro-for-kiroween-2026-2bab</link>
      <guid>https://dev.to/laoleedesign/i-built-an-accessibility-tool-that-haunts-your-designs-with-kiro-for-kiroween-2026-2bab</guid>
      <description>&lt;p&gt;&lt;em&gt;This post is written as part of the Kiroween 2026 hackathon.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I'm Oldlee, a packaging and product designer in Malaysia. For years I've shipped contact-lens boxes, retail walls and landing pages, and one bug keeps coming back: text nobody can read. Pastel on pastel. Light grey on white. White on mint. Designers call it "ghost text". So for Kiroween I built &lt;strong&gt;Ghostlight&lt;/strong&gt;, a tool that finds it in any screenshot and exorcises it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Drop a screenshot or packaging proof.&lt;/strong&gt; A "ghost light" sweeps it and raises a ghost wherever text falls below the WCAG contrast line.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exorcise&lt;/strong&gt; repaints each ghost with the nearest passing colour, changing only OKLCH lightness, so the hue and the brand stay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Possession&lt;/strong&gt; re-scans the image the way people with colour-vision deficiency or low vision see it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Séance palette&lt;/strong&gt; checks every text/background pair and exports CSS variables.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fje2gxc6kutnb4iiu2l44.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fje2gxc6kutnb4iiu2l44.png" alt="Ghostlight accessibility tool highlighting ghost text on packaging" width="800" height="385"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Live demo: &lt;a href="https://old.lat/ghostlight/" rel="noopener noreferrer"&gt;https://old.lat/ghostlight/&lt;/a&gt;&lt;br&gt;
Code: &lt;a href="https://github.com/Oldleeo/ghostlight" rel="noopener noreferrer"&gt;https://github.com/Oldleeo/ghostlight&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How Kiro changed the way I built it
&lt;/h2&gt;

&lt;p&gt;I used Kiro CLI on a remote Linux box. I'm a designer first, so my usual way of coding with AI is: describe, generate, fix, repeat. Kiro pushed me to write steering docs before any code.&lt;/p&gt;

&lt;p&gt;The line that mattered most was one sentence in &lt;code&gt;tech.md&lt;/code&gt;: &lt;strong&gt;ratios are floored, never rounded up.&lt;/strong&gt; A 4.497 is a fail. Kiro carried that one rule into the requirements, the design, the code and a property-based test without me repeating it once.&lt;/p&gt;

&lt;p&gt;The spec was the second surprise. From a one-paragraph brief Kiro wrote numbered requirements, a design with correctness properties, and a task plan. Then real screenshots broke it: gradients and rounded box corners were flagged as ghosts. Instead of patching, I revised the spec twice (text-likeness, anti-aliasing core, "glyphs cross rows and columns, corners don't") and let Kiro re-implement against it. The landing-page sample went from 24 flagged places, many of them box edges, to 16 places that are all real text.&lt;/p&gt;

&lt;p&gt;I also set up two custom agents: &lt;strong&gt;ghost-smith&lt;/strong&gt; builds only from &lt;code&gt;tasks.md&lt;/code&gt;, and &lt;strong&gt;ghost-auditor&lt;/strong&gt; is read-only and runs Ghostlight's engine against Ghostlight's own UI. Every pair passes. An accessibility tool that fails its own audit would be a bad joke.&lt;/p&gt;

&lt;p&gt;Property-based tests caught a bug unit tests didn't: exorcising white text on a mint button painted a black bar on the white label next to it. Now there's a property for that.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;Font-size awareness, a Figma plugin, and batch scans of whole design systems.&lt;/p&gt;

&lt;p&gt;If you design anything with text on it, try a screenshot on Ghostlight and see how many ghosts you've been living with.&lt;/p&gt;

</description>
      <category>kiro</category>
      <category>a11y</category>
      <category>webdev</category>
      <category>design</category>
    </item>
  </channel>
</rss>
