Introduction Running a blog in both Korean and English revealed an interesting problem. When sharing blog links internationally, visitors often land on the Korean page. Those who can’t read Korean are confused, right? Similarly, when Korean readers click on English post links shared in Korean communities, they face the same issue. While there’s a language switcher button in the header, new visitors often struggle to find it. This isn’t user-friendly, and from an accessibility perspective, it’s not ideal either. ...

Developers often make the same mistake after learning ARIA. They understand the concept, but they are unsure when and how to apply it in real projects. ARIA practical guide main visual with ARIA attributes highlighted in a code editor Cover image example: visual that symbolizes applying ARIA attributes · Generated by Nanobanana AI You may have heard the phrase: “ARIA is a last resort.” Use semantic HTML first, and add ARIA only when native HTML is not enough. This guide follows that principle and shows how to use ARIA effectively in real work. ...

Introduction “1.3.1 Info and Relationships - Level A” If you’ve worked with WCAG 2.2, you’re familiar with this format of Success Criteria. Numbers, levels, and clear test conditions. This structure has been the standard for web accessibility for over 15 years. However, as we explored in the previous article, this approach had limitations. “Websites that pass checkboxes but are actually unusable” are proof of this. WCAG 3.0 has completely redesigned the structure itself to address this issue. It didn’t just add items—it changed the way we evaluate accessibility. ...

Introduction Blogs built with Static Site Generators (SSG) are incredibly fast and secure. However, adding dynamic features like comments requires careful consideration. This blog uses Giscus, a GitHub Discussions-based comment system, but there was one inconvenience. Comments only appear at the bottom of each post, making it difficult to see at a glance which articles have active discussions. So I built three features: Display comment counts in post lists - See which articles have ongoing conversations Show recent comments on the explore page - View recent blog activity at a glance Create an all comments page - Browse all comments in one place This article shares the process of bringing dynamic comment information to a static site using GitHub GraphQL API while maintaining optimal performance. ...

Introduction “Our site passed WCAG 2.1 AA 100%, but screen reader users still can’t sign up.” I keep thinking about this comment I heard at a conference last year. They passed accessibility audits, got the green badge, but users with disabilities still couldn’t use core features. This is the biggest dilemma facing WCAG 2.x today. If you’re a developer or designer working on web accessibility, you’ve probably heard of WCAG (Web Content Accessibility Guidelines). Recently, a new guideline called WCAG 3.0 has emerged, and many people are wondering: ...

Introduction Recently, I started building and operating a blog using Hugo with the PaperMod theme. Using someone else’s theme has the advantage of quick setup, but not everything fits my needs perfectly. After customizing many parts to match my preferences, I noticed some issues with the code blocks. Line numbers were implemented with <table> tags. While this doesn’t violate accessibility guidelines, it felt not semantic. Moreover, I wondered: what’s the experience for screen reader users? I found a better approach using CSS Counters. ...

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

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