KWCAG-2.2 Subscribe to KWCAG-2.2 RSS feed

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

“I’ve looked at WCAG 2.1, but what’s new in 2.2?” I get this question a lot doing frontend work. WCAG 2.2 became a W3C Recommendation on October 5, 2023, so it’s been nearly three years now. For reference, the document currently posted at w3.org/TR/WCAG22/ is a December 12, 2024 revised recommendation — the success criteria themselves haven’t changed, it’s just a republication with post-finalization corrections folded in. Yet plenty of teams are still running their checklists against 2.1. It’s not that they don’t know the new criteria exist — it’s more that “nine new ones, do we really have to look at all of them?” has kept it on the back burner. ...

“Our site needs accessibility certification — where do we even start?” That’s usually the first overwhelming question once this lands on your desk. Running a scanner and clearing every error it flags doesn’t get you certified, and the guidance out there is scattered across too many places. This post exists to cut through that confusion — walking through what certification actually verifies, what standard it’s judged against, and where the pass line sits, aimed squarely at someone preparing for it for the first time. ...

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