Say you run an accessibility checker. You feed it a site’s URL, and the checker has to decide: which pages should it actually look at? Is the homepage enough? If so, you don’t have much basis for saying “this site is accessible” or “this site isn’t.” But checking every page isn’t realistic either — forums, blogs, and shopping sites can have hundreds or thousands of posts. Auditing all of them blows the time and cost budget. ...
There’s a moment when you’re idly scrolling a running service’s logs and your hand stops. That day, I hit that moment in the audit logs of A11y Check, a web accessibility auditing service. Two audits had been stuck “scanning” for hours. Not in progress, not failed — just stuck. This is what people call a zombie task: a job left in the queue, neither dead nor alive. This is the story of catching those two zombies, of two fixes I was sure of missing, and of finding the real cause only on the third try. To skip to the end: the culprit wasn’t my logic but Vercel’s Deployment Protection — or more precisely, my internal-call code that didn’t account for it. ...
“We’re certified, so we should be fine.” It’s an easy thing to believe on the side that builds the website. Yet even on sites with a certification mark, it’s common for a screen reader user to fail to find the log-in button, or a low-vision user to be unable to read gray text on gray. Having been audited once, and being usable right now, are two different stories. The tool I built to shrink that gap is A11y Check. Put in a URL and it audits the accessibility automatically, then hands back a report and a fix guide. This article covers what A11y Check does, how it works, and why I opened the code. Let’s start with where it came from. ...
Prologue I’d prepared for this talk as a natural extension of the work I do every day, so I didn’t expect to be particularly nervous. But when I saw the list of other presenters ahead of time, I found myself wanting to do justice to the occasion — to make sure my talk held its own alongside theirs. Event poster — AI Accessibility Seminar: Accessibility for All. Date: Thursday, April 23, 2026, 10:00 AM – 12:20 PM. Venue: NIA Seoul Office, Basement Conference Room. Hosted by: Digital Accessibility Standardization Forum. Organized by: Universal Design Society. Event poster So I put together clean slides, wrote out a full script, ran through a few rehearsals — and headed to Seoul. The trip from Daegu isn’t exactly short, but I was in good spirits. There’s something about being needed, about being put to use, that makes you feel alive. ...
Introduction I just returned from the AI Agent Scenario Competition Citizen Evaluation Panel held in Seoul. The panel consisted of expert judges and citizen evaluators, with the final scores reflecting both expert evaluation and citizen evaluation. Since the evaluation details are confidential, I can’t discuss individual teams or specific results. However, through this experience, I was able to clearly define what standards I use when evaluating AI public services. So in this post, rather than “how this team performed,” I want to record what questions I asked and why I thought those questions mattered. ...
Introduction Let me be honest — this choice is a losing deal on paper. I’m spending a whole day, paying for transportation out of my own pocket, and the compensation is only about $35 (50,000 KRW). Yet, I’m heading to Seoul tomorrow. I wanted to organize my reasons step by step. View from a train window - a journey to somewhere Photo: Dieter K / Unsplash The Evaluation Panel Offer and My Decision One day, while browsing the NIA (National Information Society Agency) website as usual, I discovered the Public Institution Website Citizen Evaluation Panel. Since then, I’ve been grateful to participate in the public web/app citizen evaluation activities for two years straight. The rewards and achievements may seem small, but the process and experience have been building up as personal assets. ...