Policy Subscribe to Policy RSS feed

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 post is a record of grappling with web accessibility, public web services, and the responsibilities of developers from direct, hands-on experience. Between law, technology, standards, and reality, I try to answer the question: “Are we really building for everyone?” In the previous post, we confirmed that the Digital Inclusion Act asks “what is usable?” Then this question remains: If AI is a system that makes decisions? If users can’t understand automated decisions? How do we distinguish between content created by generative AI? ...

This post is a record of grappling with web accessibility, public web services, and the responsibilities of developers from direct, hands-on experience. Between law, technology, standards, and reality, I try to answer the question: “Are we really building for everyone?” In the previous post, we reached this question: Even after meeting accessibility standards, why are so many people still excluded from digital services? The institutional answer to this question is the Digital Inclusion Act. ...

This piece is a record of wrestling with web accessibility, public services, and a developer’s responsibility from the field. Between law and technology, between standards and reality, I try to answer: “Are we really building for everyone?” While working on web accessibility for years, I found myself repeatedly hearing a similar question: “We’re certified and passed the checklist. Isn’t accessibility done now?” When I first heard this question, I nodded briefly. Many public websites did meet WCAG 2.1 / KWCAG 2.2 standards, passed screen reader tests, and satisfied contrast requirements. ...