Guide

Introduction “1.3.1 Info and Relationships - Level A” If you’ve worked with WCAG 2.2, you’re familiar with this format of Success Criteria. Numbers, levels, and clear test conditions. This structure has been the standard for web accessibility for over 15 years. However, as we explored in the previous article, this approach had limitations. “Websites that pass checkboxes but are actually unusable” are proof of this. WCAG 3.0 has completely redesigned the structure itself to address this issue. It didn’t just add items—it changed the way we evaluate accessibility. ...

Introduction “Our site passed WCAG 2.1 AA 100%, but screen reader users still can’t sign up.” I keep thinking about this comment I heard at a conference last year. They passed accessibility audits, got the green badge, but users with disabilities still couldn’t use core features. This is the biggest dilemma facing WCAG 2.x today. If you’re a developer or designer working on web accessibility, you’ve probably heard of WCAG (Web Content Accessibility Guidelines). Recently, a new guideline called WCAG 3.0 has emerged, and many people are wondering: ...

Introduction As a web developer, you’ve probably encountered code like this: html 라인 넘버 읽기: OFF 라인 넘버 읽기 기능 이 버튼은 스크린 리더 사용자를 위한 기능입니다. ...

Introduction We live in an age where generative AI like ChatGPT, Claude, and Gemini has become part of daily life. AI chatbots have established themselves on websites, and automated content generation has become commonplace. Amid this rapid technological advancement, we must ask an important question: “Is the web created by AI usable by everyone?” Web Accessibility means ensuring that everyone—people with disabilities, elderly users, those with slow network connections, and more—can use the web equally. In the AI era, or rather because it is the AI era, web accessibility has become even more critical. ...