Hi there 👋

Introduction After you run a survey, someone always asks for a printed copy of the results. If you built the form in Google Forms, the Responses tab already draws you nice charts, so printing that screen straight off should just work, right? Try hitting print from the responses page, though, and you get one broken page — even though there are plenty more questions below the fold. The pie charts in the Summary tab get sliced in half at the page boundary, too. I ran into this wall myself, and eventually built a tool for it: PrintImg, which splits a tall screenshot into as many A4 pages as it needs. ...

Introduction Standards documents change quietly. One morning an email titled “For Review” shows up in your inbox, and when you open the link, the document you read last time has a different structure. On September 10, 2026, the W3C Web Accessibility Initiative (WAI) published a new WCAG 3 (3.0) Working Draft and sent out a call for review comments. A red pen resting beside the fanned-out pages of an open book - standards drafts get revised this quietly, and this often Photo: Emmanuel Phaeton / Unsplash This post is a direct comparison between that September draft and its immediate predecessor, the March 3, 2026 draft. I covered the March draft in WCAG 3 Status Check: A Complete Rundown of the March 2026 Draft — and one of that post’s key sections just got flipped on its head. ...

Safari’s top-level await bug was reported back in July 2022 (WebKit bug 242740), and by October 2025 it had gotten bad enough that top-level await dropped to “Limited” on Baseline (the cross-browser support signal for web platform features). The fix merged in April 2026, shipped starting with Safari Technology Preview 243 in May, and on September 2 the WebKit team posted the postmortem: Fixing top-level await in Safari. ...

On September 1st, the Claude Code v2.1.257 release notes carried one short line: the default model for the Fable line had switched to 5.1. If you use Fable and have never touched the model setting, the brain writing your code got quietly swapped out that day. The same release notes had an exception, too — the fable alias in Claude app gateway sessions stays on Fable 5 for now. Read this as a story about the regular Claude Code you run from the terminal. ...

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

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