KWCAG Subscribe to KWCAG RSS feed

If you’ve ever run an accessibility checker, you’ve probably seen a line somewhere in the results like, “This result was verified on a specific browser and screen reader combination.” Every accessibility evaluation starts from some baseline environment. But what exactly counts as that “baseline environment” is something standards documents have rarely defined with any precision. The March 2026 Working Draft of WCAG 3 (3.0) puts a name to this gap — the accessibility-support set — and structures it into a formal clause (§3.2.2). The term itself existed in earlier drafts too; what this draft adds is splitting it into a default set and an alternative set, numbering the clause, and giving it a proper place within the conformance requirements. Read the definition closely, though, and you’ll find a line stating that the baseline is oriented toward English content. This post walks through exactly what that clause says, and what it means for local assistive technology environments like Sense Reader (센스리더), Korea’s dominant local screen reader. ...

“Once WCAG 3 ships, what happens to the KWCAG we’re following right now?” That’s the question I get most often since publishing our complete KWCAG 2.2 guide. “WCAG 3” has started coming up often enough in accessibility newsletters and conference talks that it’s only natural to wonder how KWCAG, our domestic standard, should respond to this shift. Short answer up front: the two standards are moving at different speeds right now, and there’s no need to relearn KWCAG anytime soon. That said, a fairly significant structural shift is on the horizon, so it’s worth knowing the general direction if you work in this space. This post walks through what’s different between the two standards and why that difference matters. ...

“Your project spec says ‘must comply with KWCAG 2.2.’ But what does that actually mean you have to do?” If you’ve ever worked on an accessibility project in Korea, you’ve probably paused at a line like that at least once. Search around and you’ll find WCAG mentioned in one place, KWCAG in another, versions 2.1 and 2.2 tangled together — it’s easy to lose track of which standard you’re actually supposed to follow. This post breaks down what KWCAG 2.2 actually is and how it’s structured, from a practitioner’s point of view. ...

↻ 2026-08-12 Updated Corrected the legal basis of Korea’s quality certification. With the Digital Inclusion Act taking effect on January 22, 2026, Article 47 of the Framework Act on Intelligent Informatization was repealed and the certification scheme moved to Articles 21–22 of the Digital Inclusion Act — this post had been citing the old provision. The body, FAQ, and comparison diagram are updated together. “Can we actually say our service is accessible?” ...

“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. ...

This post is part of an ongoing effort to monitor public websites as a web accessibility professional. It is written with the goal of improving information accessibility and advancing technology — not as a political statement. I only recently found out the Cheong Wa Dae website had been redesigned. Life gets busy, and I was a bit late to the news — but as soon as I heard, I was curious enough to check it out. ...

Imagine a webpage with five images. Four of them have no alt text. When a blind user visits this page using a screen reader, those images are announced simply as “image” — or worse, as a raw filename. No meaning. No context. This isn’t a hypothetical. It’s the reality measured by South Korea’s 2025 Web Information Accessibility Survey, published on March 27, 2026. A user sitting in front of a laptop — without alt text, all image information is completely blocked Photo: Ardalan Hamedani / Unsplash What Changed This Year South Korea’s 2025 survey adopted a new standard. The guidelines were updated from KWCAG 2.1 (24 criteria) to KWCAG 2.2 (32 criteria), with 9 new items added. ...

This essay records what I have wrestled with on the ground about web accessibility, public web services, and the responsibilities of developers. Between law and technology, standards and reality, I try to answer the question: “Are we truly building for everyone?” Is today’s Seollal(Korean Lunar New Year) really providing equal information to everyone? Produced by: Nano Banana Ahead of the Seollal(Korean Lunar New Year) holiday, I browse the web to find helpful information. Seollal(Korean Lunar New Year) is a uniquely Korean holiday. As I visit site after site, the first thing I often encounter is an auto-rotating banner or card news. Around Seollal, these banners include important government notices like emergency information. ...