Accessibility Subscribe to Accessibility RSS feed

When “pass” and “grade” show up in the same document, it’s tempting to put them on one line: the passing mark is the lowest grade, and the grades climb from there. Most exams work that way. WCAG 3’s conformance and Bronze, Silver, and Gold are easy to read the same way. On October 16, I gave a talk, What the WCAG 3.0 Draft Asks of Evaluation Methods, at a meeting of the Digital Accessibility Standardization Forum’s service subcommittee. In the Q&A, someone asked: “What’s the difference between meeting conformance and Bronze, Silver, Gold? And what do you have to do to get them?” I couldn’t answer it well with only the materials I’d prepared, and I’ve regretted that since. So I went back to the WCAG 3 Working Draft published on September 10, 2026, with just that one question in mind. WCAG 3 is the standard W3C is building to succeed WCAG 2.2, and a Working Draft is one that isn’t final yet. ...

WCAG 3 September 2026 Working Draft explained: one conformance line, Bronze/Silver/Gold as reporting tiers, and 216 requirements counted by hand.

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

A first-timer's guide to Korea's Web Accessibility Certification: why get it, KWCAG 2.2, review stages, pass lines, fees, and what it doesn't guarantee.

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

Opening: treating scroll as “time” When you build scroll-based animations, you eventually hit this thought: “What if scroll were not just an input event” “but a proper timeline?” Scroll-Driven Animation is that idea made explicit. Instead of treating scroll as a trigger, you treat it as the timeline itself. In this post, I group implementation strategies into three families: Native CSS Scroll-Driven Animation IntersectionObserver for state changes scroll + requestAnimationFrame with manual progress mapping For each one, we will cover the principle, strengths, tradeoffs, and accessibility concerns. The code samples here are minimal and correct by themselves, and each section ends with a link to a live demo you can poke at directly. ...

Where WCAG 3 (3.0) stands in the March 2026 W3C Working Draft: the 12-category, 44-guideline structure, requirement counts, and the return of Bronze/Silver/Gold.

Introduction This is the seventh post in the WCAG 3.0 series. The expanded scope post looked at how far WCAG 3.0 reaches “beyond the web.” This time, I want to answer a question a lot of people keep asking me. “Should we migrate to WCAG 3.0?” Short answer up front: not yet. But there’s an important nuance to that answer. “Conformance” and “improvement” are two different conversations. Source document: This post is based on the W3C Working Draft of March 3, 2026. Drafts are generally updated on a roughly six-month cycle, so details may have shifted by the time you’re reading this. ...

This is a review of a product I paid for with my own money. There was no sponsorship or freebie involved — I’ve written honestly about both what I liked and what I didn’t. Intro: I Bought Yet Another Timer When I can’t focus, the easiest thing I reach for is a timer. You’ve probably heard of the Pomodoro technique — “focus for 25 minutes, rest for 5.” But when you actually try it, the problem shows up in a surprisingly simple place: even turning the timer on feels like a chore. ...

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