W3C Subscribe to W3C RSS feed

“Can we actually say our service is accessible?” Is it done when the checker reports zero errors? If a service has hundreds of screens, do you have to scan them all — or is checking a few enough? And if you pick a few, which screens, how many, and on what grounds can you claim “we comply”? A hand ticking checkboxes one by one on a tablet screen - accessibility evaluation is a matter of following a procedure, not intuition Photo: Jakub Żerdzicki / Unsplash When you study accessibility, there is plenty of material about the standard (WCAG), but surprisingly little about this “how do we evaluate” question. As it turns out, the W3C has had an official answer all along. And on July 23, 2026, that document got its first new version in twelve years: WCAG Evaluation Methodology (WCAG-EM) 2.0. ...

Introduction In the previous post, we looked at why WCAG 3.0 reorganized “Success Criteria” into “Outcomes.” This post focuses on changes to the conformance model. WCAG 3.0 aims for a different approach than WCAG 2.x, but it is still in the Editor’s Draft (2026-01-05) stage and is not finalized. Conformance levels, scoring approaches, and evaluation methods are still being explored. Important: This post is based on the WCAG 3.0 Editor’s Draft (2026-01-05). The draft can change at any time, and the document itself is explicitly marked as a work in progress. ...

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