Skip to content
How Accessible Is Google's New IDE Homepage? — Analyzing Google Antigravity thumbnail

How Accessible Is Google's New IDE Homepage? — Analyzing Google Antigravity

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

Published date: 2026-03-17 · Reading time: 5 min · Word count: 2470 words · Author: Isaac
Color Accessibility: Designing Colors That Everyone Can Perceive thumbnail

Color Accessibility: Designing Colors That Everyone Can Perceive

Introduction “We used red and green to distinguish them, so it should be fine.” It’s a thought that comes up naturally during development. But more people than you’d expect have difficulty telling those two colors apart. Statistics based on Northern European ancestry suggest that roughly 1 in 12 men and 1 in 200 women have red-green color vision deficiency. The exact ratio varies by region and genetic background, but the fact remains: there are always users who struggle to distinguish red from green. ...

Published date: 2026-03-06 · Reading time: 24 min · Word count: 5080 words · Author: Isaac
WCAG 3.0 Expanded Scope: Beyond the Web thumbnail

WCAG 3.0 Expanded Scope: Beyond the Web

↻ 2026-07-30 Updated Updated the basis document to the W3C Working Draft of March 3, 2026 — one draft newer than the version cited at publication time. Introduction This is the sixth post in the WCAG 3.0 series. This time I want to unpack what “beyond the web” actually means in practice. The earlier posts looked at structure, testing, and Assertions — now it’s time to get clear on “how far does the scope actually reach?” ...

Published date: 2026-02-23 · Updated 2026-07-30 · Reading time: 5 min · Word count: 2370 words · Author: Isaac
Seollal Holiday Information Isn’t Visible to Everyone thumbnail

Seollal Holiday Information Isn’t Visible to Everyone

This essay records what I have wrestled with on the ground about web accessibility, public web services, and the responsibilities of developers. Between law and technology, standards and reality, I try to answer the question: “Are we truly building for everyone?” Is today’s Seollal(Korean Lunar New Year) really providing equal information to everyone? Produced by: Nano Banana Ahead of the Seollal(Korean Lunar New Year) holiday, I browse the web to find helpful information. Seollal(Korean Lunar New Year) is a uniquely Korean holiday. As I visit site after site, the first thing I often encounter is an auto-rotating banner or card news. Around Seollal, these banners include important government notices like emergency information. ...

Published date: 2026-02-15 · Reading time: 4 min · Word count: 1708 words · Author: Isaac
Thoughts on Writing Blog Posts thumbnail

Thoughts on Writing Blog Posts

Since I started this blog, I have written in several directions. The areas I keep digging into are web accessibility and frontend. I want to write more, and new ideas keep coming, but the speed of writing is not as fast as I hope. Right now I still have eight unfinished drafts. Starting is easy, but wrapping up always feels surprisingly hard. AI has made research and organization much faster, but my time and energy are still limited, so it often feels frustrating. I work during the day, and after work I take care of family responsibilities, side projects, this blog, and certification prep. Honestly, I wish I had ten bodies. ^^;; Still, I want to keep going, so today I am writing a candid note about how I approach blog writing. ...

Published date: 2026-02-05 · Reading time: 3 min · Word count: 579 words · Author: Isaac
Keyboard Accessibility A to Z: Building Websites Everyone Can Use Without a Mouse thumbnail

Keyboard Accessibility A to Z: Building Websites Everyone Can Use Without a Mouse

Introduction Have you ever tried using the internet without a mouse? Most people take their mouse for granted. But there are many people who can’t use one. People with physical disabilities who can’t operate a mouse People with repetitive strain injuries like carpal tunnel syndrome People with temporary arm injuries Power users who simply find keyboards more efficient For these users, the question “Can I use this site with just a keyboard?” is crucial. ...

Published date: 2026-02-03 · Reading time: 23 min · Word count: 4691 words · Author: Isaac
Assertions: A New Unit for Accessibility Evaluation thumbnail

Assertions: A New Unit for Accessibility Evaluation

↻ 2026-07-30 Updated This post reflects the W3C Working Draft of March 3, 2026. Foundational was renamed to Core, so related wording has been corrected, and the Assertions count (28) and their role in level determination have been updated to match the current draft. Introduction In Atomic Tests vs. Holistic Tests: A New Testing Methodology, we discussed balancing Atomic and Holistic tests. Now we need to address how we’ll “assert” and “document” these results. This is where Assertions come in. ...

Published date: 2026-02-01 · Updated 2026-07-30 · Reading time: 3 min · Word count: 1100 words · Author: Isaac
Scheduled Publishing with GitHub Actions Every 3 Hours thumbnail

Scheduled Publishing with GitHub Actions Every 3 Hours

Introduction When running a static blog, “scheduled publishing” and “build limits” often become problems at the same time. In particular, building on every commit can easily hit build limits on platforms like Cloudflare Pages. In this post, I’ll walk you through the approach I’m actually using: running a publish check with GitHub Actions every 3 hours to handle scheduled publishing. The key idea is “check only at set intervals, and publish only when needed.” ...

Published date: 2026-01-30 · Reading time: 11 min · Word count: 2254 words · Author: Isaac
Atomic Tests vs. Holistic Tests: A New Testing Approach thumbnail

Atomic Tests vs. Holistic Tests: A New Testing Approach

↻ 2026-07-30 Updated This post reflects the W3C Working Draft of March 3, 2026. It accounts for Foundational being renamed to Core, and the basis-document reference has been corrected to the current draft. Introduction When people hear “accessibility testing,” they often think of a checklist: “Does this button have alternative text?” “Is the contrast ratio high enough?” WCAG 2.2 is built around clear pass/fail checks like these. WCAG 3.0 moves toward a broader unit of evaluation, aiming to consider overall user experience quality. That shift naturally changes how we test. We now combine fine-grained checks (Atomic) with real-world contextual evaluation (Holistic). ...

Published date: 2026-01-26 · Updated 2026-07-30 · Reading time: 5 min · Word count: 1034 words · Author: Isaac
WCAG 3.0 Conformance Model: Moving Beyond A/AA/AAA thumbnail

WCAG 3.0 Conformance Model: Moving Beyond A/AA/AAA

↻ 2026-07-30 Updated The W3C Working Draft of March 3, 2026 brought major changes to the conformance model, so this post has been revised. Foundational was renamed to Core, and the Bronze/Silver/Gold levels, which had been absent from the draft for a while, are back. That said, level thresholds are still “to be determined,” and the old points-based scoring approach is no longer in the current draft — since this part is easy to misread, I’ve called it out separately. Requirement counts (Core 92 · Supplemental 61 · Assertions 28) and the diagram have also been updated to match the current draft. Introduction In the previous post, we looked at why WCAG 3.0 reorganized “Success Criteria” into “Outcomes.” ...

Published date: 2026-01-25 · Updated 2026-07-30 · Reading time: 10 min · Word count: 1928 words · Author: Isaac
맨 위로