<?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>Web Accessibility on Codeslog</title>
    <link>https://www.codeslog.com/en/categories/web-accessibility/</link>
    <description>Recent content in Web Accessibility 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, 24 Oct 2026 01:20:00 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/en/categories/web-accessibility/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WCAG 3 Conformance vs. Bronze, Silver, Gold: How to Claim a Tier</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-conformance-vs-bronze-silver-gold/</link>
      <pubDate>Sun, 18 Oct 2026 00:13:44 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-conformance-vs-bronze-silver-gold/</guid>
      <description>WCAG 3 conformance vs. Bronze, Silver, Gold reporting tiers in the September 2026 draft: what differs, the four steps to claim one, and why no one can yet.</description>
    </item>
    <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>WebAIM Million 2026&#39;s &#43;22.5% Was the Wrong Number — Rereading Web Page Complexity</title>
      <link>https://www.codeslog.com/en/posts/webaim-million-2026-page-complexity/</link>
      <pubDate>Fri, 25 Sep 2026 23:35:52 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/webaim-million-2026-page-complexity/</guid>
      <description>WebAIM Million 2026&amp;#39;s 22.5% jump in page complexity was a miscalculation; one-year growth was 14.3%. How to read DOM size, means, and error density.</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>How Screen Readers Read aria-live Status Messages (WCAG 4.1.3)</title>
      <link>https://www.codeslog.com/en/posts/aria-live-status-messages/</link>
      <pubDate>Wed, 02 Sep 2026 01:24:30 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/aria-live-status-messages/</guid>
      <description>How do screen readers handle aria-live status messages? A demo-driven look at WCAG 4.1.3, polite vs. assertive, debounce timers, and icon or sound status.</description>
    </item>
    <item>
      <title>WCAG 3 Accessibility-Support Sets: Korea&#39;s Blank</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-accessibility-support-sets/</link>
      <pubDate>Wed, 19 Aug 2026 18:20:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-accessibility-support-sets/</guid>
      <description>WCAG 3&amp;#39;s March 2026 draft structures accessibility-support sets into a formal clause (§3.2.2) — what its English default leaves blank for Korea&amp;#39;s Sense Reader.</description>
    </item>
    <item>
      <title>KWCAG 2.2 vs. WCAG 3: What&#39;s Actually Different</title>
      <link>https://www.codeslog.com/en/posts/kwcag-vs-wcag-3/</link>
      <pubDate>Wed, 19 Aug 2026 18:15:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/kwcag-vs-wcag-3/</guid>
      <description>Comparing KWCAG 2.2 (Korean Web Content Accessibility Guidelines) with WCAG 3 (3.0) on structure, conformance model, and timeline — and what it means for Korea.</description>
    </item>
    <item>
      <title>WCAG 2.2&#39;s 6 New Criteria: Target Size Hits 24px</title>
      <link>https://www.codeslog.com/en/posts/wcag-22-new-criteria/</link>
      <pubDate>Wed, 19 Aug 2026 18:10:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-22-new-criteria/</guid>
      <description>A code-first, try-it-yourself rundown of WCAG 2.2&amp;#39;s 6 most-used new success criteria, plus the 3 AAA criteria and how KWCAG 2.2 and global standards stack up.</description>
    </item>
    <item>
      <title>WA Certification: Cost, Process, How to Get It</title>
      <link>https://www.codeslog.com/en/posts/web-accessibility-certification-guide/</link>
      <pubDate>Wed, 19 Aug 2026 18:05:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/web-accessibility-certification-guide/</guid>
      <description>A first-timer&amp;#39;s guide to Korea&amp;#39;s Web Accessibility Certification: why get it, KWCAG 2.2, review stages, pass lines, fees, and what it doesn&amp;#39;t guarantee.</description>
    </item>
    <item>
      <title>KWCAG 2.2 Explained: 4 Principles, 33 Checkpoints</title>
      <link>https://www.codeslog.com/en/posts/kwcag-22-guide/</link>
      <pubDate>Wed, 19 Aug 2026 18:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/kwcag-22-guide/</guid>
      <description>KWCAG 2.2, Korea&amp;#39;s national web accessibility standard: 4 principles, 14 guidelines, 33 checkpoints under KS X OT0003:2022, and why its revision year gets misreported.</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>WCAG 3 Migration: Do You Need It Yet? Moving On from WCAG 2.2</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-migration-strategy/</link>
      <pubDate>Mon, 03 Aug 2026 01:37:27 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-migration-strategy/</guid>
      <description>Do you need a WCAG 3 (3.0) migration yet? Why it is still a Working Draft, and a phased strategy for borrowing its Core and Outcomes mindset to improve accessibility today.</description>
    </item>
    <item>
      <title>The EU AI Act Is Now in Force — Where Accessibility Hooks In</title>
      <link>https://www.codeslog.com/en/posts/eu-ai-act-accessibility/</link>
      <pubDate>Thu, 30 Jul 2026 01:02:04 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/eu-ai-act-accessibility/</guid>
      <description>The EU AI Act&amp;#39;s high-risk obligations begin August 2, 2026. Article 16 ties accessibility to the Web Accessibility Directive and the European Accessibility Act — and how Korea&amp;#39;s AI Basic Act compares.</description>
    </item>
    <item>
      <title>The Web Is Less Accessible Than a Year Ago — The WebAIM Million 2026 Report</title>
      <link>https://www.codeslog.com/en/posts/webaim-million-2026/</link>
      <pubDate>Tue, 28 Jul 2026 01:42:21 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/webaim-million-2026/</guid>
      <description>WebAIM Million 2026 scanned the top million home pages: errors per page rose to 56.1, up 10.1% in a year, reversing years of progress. Covers the top 6 recurring errors and the ARIA paradox.</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>71% Accessible Is Not Accessible — The Carrefour Ruling and One Year of the EAA</title>
      <link>https://www.codeslog.com/en/posts/eaa-carrefour-ruling/</link>
      <pubDate>Tue, 14 Jul 2026 00:40:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/eaa-carrefour-ruling/</guid>
      <description>A court in Caen gave Carrefour six months to fix its site and app or pay 500 euros a day — Europe&amp;#39;s first EAA enforcement ruling. Why 71% RGAA conformity wasn&amp;#39;t enough.</description>
    </item>
    <item>
      <title>The Redesigned Cheong Wa Dae Website — But What About Accessibility?</title>
      <link>https://www.codeslog.com/en/posts/president-site-redesign-accessibility/</link>
      <pubDate>Tue, 21 Apr 2026 00:00:57 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/president-site-redesign-accessibility/</guid>
      <description>We audited the redesigned Cheong Wa Dae website (president.go.kr) against KWCAG 2.2 — skip navigation and dark mode are wins, but ARIA landmarks, tabindex, and image alt text still need fixes.</description>
    </item>
    <item>
      <title>Form Accessibility Mastery: Designing Accessible Input Forms for Everyone</title>
      <link>https://www.codeslog.com/en/posts/form-accessibility-mastery/</link>
      <pubDate>Sat, 11 Apr 2026 00:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/form-accessibility-mastery/</guid>
      <description>A complete guide to form accessibility based on WCAG 2.2 — from label associations and ARIA usage to error handling and keyboard navigation. Learn with a live demo.</description>
    </item>
    <item>
      <title>17.1% Alt Text Compliance: What South Korea&#39;s 2025 Web Accessibility Survey Reveals</title>
      <link>https://www.codeslog.com/en/posts/2025-web-accessibility-survey/</link>
      <pubDate>Mon, 30 Mar 2026 23:40:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/2025-web-accessibility-survey/</guid>
      <description>South Korea&amp;#39;s 2025 web accessibility survey, now measured against KWCAG 2.2&amp;#39;s 32 checkpoints: the average score rose to 70.4, yet alt text compliance is only 17.1 percent, the lowest of all items.</description>
    </item>
    <item>
      <title>How Accessible Is Google&#39;s New IDE Homepage? — Analyzing Google Antigravity</title>
      <link>https://www.codeslog.com/en/posts/google-antigravity-accessibility/</link>
      <pubDate>Tue, 17 Mar 2026 16:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/google-antigravity-accessibility/</guid>
      <description>An accessibility teardown of Google Antigravity&amp;#39;s homepage: wrapping every letter in its own div breaks screen readers and browser translation. Covers WCAG violations, ADA context, and fixes.</description>
    </item>
    <item>
      <title>Color Accessibility: Designing Colors That Everyone Can Perceive</title>
      <link>https://www.codeslog.com/en/posts/color-accessibility/</link>
      <pubDate>Fri, 06 Mar 2026 00:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/color-accessibility/</guid>
      <description>Color design for color vision deficiency and low vision: the WCAG 2.2 contrast ratio of 4.5:1 and how it&amp;#39;s calculated, never relying on color alone, dark mode contrast, and brand colors that fail.</description>
    </item>
    <item>
      <title>WCAG 3.0 Expanded Scope: Beyond the Web</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-expanded-scope-beyond-web/</link>
      <pubDate>Mon, 23 Feb 2026 00:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-expanded-scope-beyond-web/</guid>
      <description>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&amp;#39;s kiosk accessibility connects to that expansion.</description>
    </item>
    <item>
      <title>Seollal Holiday Information Isn’t Visible to Everyone</title>
      <link>https://www.codeslog.com/en/posts/seollal-gov-accessibility/</link>
      <pubDate>Sun, 15 Feb 2026 02:40:12 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/seollal-gov-accessibility/</guid>
      <description>One month after Korea&amp;#39;s Digital Inclusion Act took effect, I compare the Blue House&amp;#39;s image-only Seollal card news, which has no alt text, against the Ministry of Health and Welfare&amp;#39;s text-based approach.</description>
    </item>
    <item>
      <title>Keyboard Accessibility A to Z: Building Websites Everyone Can Use Without a Mouse</title>
      <link>https://www.codeslog.com/en/posts/keyboard-accessibility-a-to-z/</link>
      <pubDate>Tue, 03 Feb 2026 00:01:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/keyboard-accessibility-a-to-z/</guid>
      <description>Making a site fully usable without a mouse: tabindex and Tab order, skip links, focus traps and focus restoration in modals, :focus-visible focus styling, and keyboard alternatives to drag and drop.</description>
    </item>
    <item>
      <title>Assertions: A New Unit for Accessibility Evaluation</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-assertions/</link>
      <pubDate>Sun, 01 Feb 2026 00:10:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-assertions/</guid>
      <description>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&amp;#39;s Conformance Claim.</description>
    </item>
    <item>
      <title>Atomic Tests vs. Holistic Tests: A New Testing Approach</title>
      <link>https://www.codeslog.com/en/posts/wcag-3-atomic-holistic-tests/</link>
      <pubDate>Mon, 26 Jan 2026 01:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/wcag-3-atomic-holistic-tests/</guid>
      <description>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.</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>ARIA Practical Guide: Implementing Accessible Web Interfaces</title>
      <link>https://www.codeslog.com/en/posts/aria-practical-guide/</link>
      <pubDate>Thu, 22 Jan 2026 02:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/aria-practical-guide/</guid>
      <description>A practical guide to applying ARIA in real projects: when to use it and when not to, plus code patterns for aria-live regions, custom tab/accordion/dropdown widgets, and accessible modal dialogs.</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>
    <item>
      <title>Beyond Regulation, Toward Trust - The AI Basic Act and Accessibility</title>
      <link>https://www.codeslog.com/en/posts/ai-basic-act-accessibility/</link>
      <pubDate>Wed, 07 Jan 2026 18:59:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/ai-basic-act-accessibility/</guid>
      <description>Reading Korea&amp;#39;s AI Basic Act (effective Jan 22, 2026) through a web accessibility lens: mapping WCAG&amp;#39;s four principles onto its transparency, high-impact AI, and generative AI labeling duties.</description>
    </item>
    <item>
      <title>Beyond Technology, Toward People – Understanding the Digital Inclusion Act</title>
      <link>https://www.codeslog.com/en/posts/digital-inclusion-act/</link>
      <pubDate>Tue, 06 Jan 2026 18:59:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/digital-inclusion-act/</guid>
      <description>A people-centered look at Korea&amp;#39;s Digital Inclusion Act (effective Jan 22, 2026): how it differs from the Framework Act on Intelligent Informatization, kiosk usability obligations, and impact assessment duties developers should know.</description>
    </item>
    <item>
      <title>Beyond Accessibility to Digital Inclusion - The Beginning of a New Era</title>
      <link>https://www.codeslog.com/en/posts/digital-inclusion-new-era/</link>
      <pubDate>Mon, 05 Jan 2026 23:50:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/digital-inclusion-new-era/</guid>
      <description>Ahead of the Digital Inclusion Act (Jan 22), this piece shows how accessibility is expanding to digital inclusion through real cases and frames the questions we must ask for inclusive design.</description>
    </item>
    <item>
      <title>The Complete Guide to Semantic HTML: Escaping Div Hell</title>
      <link>https://www.codeslog.com/en/posts/semantic-html-guide/</link>
      <pubDate>Tue, 23 Dec 2025 02:32:17 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/semantic-html-guide/</guid>
      <description>Move from div-only markup to semantic HTML: when to use header, nav, main, article, and section, how article and section differ, plus heading levels and ARIA landmarks, with before-and-after examples.</description>
    </item>
    <item>
      <title>Web Accessibility in the AI Era: Universal Values That Must Evolve With Technology</title>
      <link>https://www.codeslog.com/en/posts/web-accessibility-ai-era/</link>
      <pubDate>Tue, 23 Dec 2025 00:29:12 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/web-accessibility-ai-era/</guid>
      <description>Can everyone use the web that AI builds? The accessibility gaps generative AI tends to miss, the four WCAG 2.2 principles in code, AI-generated alt text, and building an accessible AI chatbot.</description>
    </item>
  </channel>
</rss>
