Click “Add to Cart” on an online store, and the badge in the top-right corner flips from 3 to 4. For someone who can see the screen, that’s feedback enough. But what about someone browsing the web with a screen reader — software that reads the screen aloud? A number quietly changing somewhere on the page tells them nothing. Whether the item was added, how many are in the cart now, whether it failed — there’s no way to know. ...
A green toast reading “Saved” pops up in the bottom-right corner of the screen. It disappears two seconds later. For someone using a mouse, that’s complete feedback. But for someone who isn’t looking at the screen? That toast never happened. There’s no way to know whether the save succeeded or not. This is exactly what live regions exist to solve. Mark a region ahead of time as one whose content can change without a page refresh, and when the text inside it changes, the screen reader reads it out automatically. One line — aria-live="polite" — is all it takes. ...
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. ...
May is a special month in Korea — packed with occasions to reach out to the people we love. Children’s Day (May 5), Parents’ Day (May 8), Teachers’ Day (May 15), Couples’ Day (May 21)… it’s no accident the whole month is called Family Month. Flower shops overflow with carnations, and KakaoTalk fills up with heartfelt digital cards. Sending a digital greeting card has become second nature. But I want to ask a simple question. ...
Introduction “How hard can a signup form be?” If that thought has ever crossed your mind… you’ve probably never tested it for accessibility. Forms are the most important interface for user input on the web. Login, checkout, search, surveys — virtually every core web function goes through a form. Yet for countless people, these forms are a complete barrier. Screen reader users can’t tell what an input field is asking for Keyboard-only users get stuck in front of a date picker People with cognitive disabilities see an error message but have no idea how to fix it A web form with multiple input fields — easy to get lost in, just like people navigating a maze. Photo: Susan Q Yin / Unsplash In this post, we’ll go through form accessibility from top to bottom, based on WCAG 2.2. No dry theory — just practical code you can use right away, paired with a demo page I built for this post. ...
Analyzing accessibility issues on Google Antigravity's homepage — behind the flashy text animations Image: AI-generated Google takes accessibility seriously. Android’s TalkBack, Chrome’s accessibility developer tools, Lighthouse’s accessibility audits… Google-built tools are used by developers worldwide every day. The same goes for Microsoft — Accessibility Insights, Narrator, Windows high-contrast mode. When it comes to accessibility tooling, these two companies are in a league of their own. ...
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 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. ...