<?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>Screen-Reader on Codeslog</title>
    <link>https://www.codeslog.com/en/tags/screen-reader/</link>
    <description>Recent content in Screen-Reader 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/tags/screen-reader/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Focus Management in SPAs: Keeping Screen Readers on Track After Route Changes</title>
      <link>https://www.codeslog.com/en/posts/spa-focus-management/</link>
      <pubDate>Tue, 15 Sep 2026 11:26:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/spa-focus-management/</guid>
      <description>Why screen readers stay silent after SPA route changes, and how to fix it in React and Next.js with focus management, aria-live, and focus restoration patterns.</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>When aria-live Stays Silent — Getting ARIA Live Regions Right</title>
      <link>https://www.codeslog.com/en/posts/aria-live-regions/</link>
      <pubDate>Wed, 02 Sep 2026 01:14:30 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/aria-live-regions/</guid>
      <description>You added aria-live correctly, but the screen reader stays silent. Why the container must exist before its content, and when to use focus instead.</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>May Greetings for Everyone — The Story of Daon Card</title>
      <link>https://www.codeslog.com/en/posts/daoncard-a11y-card-family-month/</link>
      <pubDate>Fri, 08 May 2026 23:25:57 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/daoncard-a11y-card-family-month/</guid>
      <description>Digital cards are often unusable with a screen reader or low vision. Daon Card (daoncard.com) is a free WCAG 2.2 AA card service I built, with real-time contrast checks and keyboard support.</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>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>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>Code Block Accessibility Improvement: Line Numbers That Screen Reader Users Can Choose</title>
      <link>https://www.codeslog.com/en/posts/code-block-accessibility-improvement/</link>
      <pubDate>Fri, 09 Jan 2026 20:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/code-block-accessibility-improvement/</guid>
      <description>A record of improving code blocks on a Hugo PaperMod blog. We replaced table-based line numbers with CSS counters so screen reader users can read code without the noise of table markup — a more semantic, accessible approach.</description>
    </item>
  </channel>
</rss>
