<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>W3C on Codeslog</title>
    <link>https://www.codeslog.com/en/tags/w3c/</link>
    <description>Recent content in W3C on Codeslog</description>
    <image>
      <title>Codeslog</title>
      <url>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</url>
      <link>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</link>
    </image>
    <generator>Hugo -- 0.168.0</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 17 Oct 2026 12:00:00 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/en/tags/w3c/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why axe and IBM Disagree, Tested Against W3C ACT Rules</title>
      <link>https://www.codeslog.com/en/posts/act-rules-format-1-1/</link>
      <pubDate>Fri, 09 Oct 2026 00:45:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/act-rules-format-1-1/</guid>
      <description>Why do accessibility checkers disagree? I ran 558 approved W3C ACT Rules test cases (556 measurable) through axe-core and IBM Equal Access.</description>
    </item>
    <item>
      <title>What Changed in the WCAG 3 September 2026 Draft: Levels Move from Conformance to Reporting</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-draft-september-2026/</link>
      <pubDate>Thu, 10 Sep 2026 14:37:24 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-draft-september-2026/</guid>
      <description>WCAG 3 September 2026 Working Draft explained: one conformance line, Bronze/Silver/Gold as reporting tiers, and 216 requirements counted by hand.</description>
    </item>
    <item>
      <title>WCAG 3 Status Check: A Complete Rundown of the March 2026 Draft</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-status-2026/</link>
      <pubDate>Tue, 04 Aug 2026 09:08:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-status-2026/</guid>
      <description>Where WCAG 3 (3.0) stands in the March 2026 W3C Working Draft: the 12-category, 44-guideline structure, requirement counts, and the return of Bronze/Silver/Gold.</description>
    </item>
    <item>
      <title>Accessibility Evaluation Has a Standard Too — WCAG-EM 2.0, Twelve Years Later</title>
      <link>https://www.codeslog.com/en/posts/wcag-em-2-evaluation-methodology/</link>
      <pubDate>Fri, 24 Jul 2026 10:05:57 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-em-2-evaluation-methodology/</guid>
      <description>W3C has published WCAG-EM 2.0, its accessibility evaluation methodology, twelve years after 1.0. What changed — from websites to apps, e-books and kiosks — the five-step procedure, sampling and random checks, and how it maps to Korea&amp;#39;s certification.</description>
    </item>
    <item>
      <title>WCAG 3.0 Conformance Model: Moving Beyond A/AA/AAA</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-scoring-conformance/</link>
      <pubDate>Sun, 25 Jan 2026 00:10:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-scoring-conformance/</guid>
      <description>Explore how WCAG 3(3.0)&amp;#39;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.</description>
    </item>
    <item>
      <title>WCAG 3.0 Structure Anatomy: From Success Criteria to Outcomes</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-structure-outcomes/</link>
      <pubDate>Mon, 19 Jan 2026 08:30:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-structure-outcomes/</guid>
      <description>WCAG 3.0 restructures accessibility into Guidelines, Outcomes, and Methods. Covers the 153 requirements (Core 92 &#43; Supplemental 61), Atomic vs. Holistic Tests, and a login-form example vs WCAG 2.2.</description>
    </item>
    <item>
      <title>The Dawn of WCAG 3.0: Why We Need New Guidelines</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-era-why-new-guidelines/</link>
      <pubDate>Mon, 12 Jan 2026 23:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-era-why-new-guidelines/</guid>
      <description>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.</description>
    </item>
  </channel>
</rss>
