Web Accessibility Subscribe to Web Accessibility RSS feed

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

WCAG 3.0 Draft extends scope beyond web content to wearables, Web of Things, VR/AR, and the tooling ecosystem, and covers how South Korea's kiosk accessibility connects to that expansion.

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

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

WCAG 3.0 Assertions document accessibility procedures automated tests cannot verify. This post covers the 28 assertions in the March 2026 Draft and how they differ from WCAG 2.2's Conformance Claim.

Compare WCAG 3.0’s quantitative/qualitative testing flow with WCAG 2.2’s success-criteria model. We cover Atomic/Holistic concepts, view/process scope, and how tests connect to scoring from a practical perspective.

Explore how WCAG 3(3.0)'s conformance model moves beyond A/AA/AAA. Covers the Core/Supplemental/Assertions structure, the returning Bronze/Silver/Gold levels, and views/processes-based scope, based on the March 2026 draft.

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

WCAG 3.0 restructures accessibility into Guidelines, Outcomes, and Methods. Covers the 153 requirements (Core 92 + Supplemental 61), Atomic vs. Holistic Tests, and a login-form example vs WCAG 2.2.

WCAG evolved from 1.0 to 2.2 over 26 years. This post explains why WCAG 3.0 exists: the All-or-Nothing dilemma, checkbox accessibility, and the shift from pass/fail checklists to user outcomes.