<?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>Debounce on Codeslog</title>
    <link>https://www.codeslog.com/en/tags/debounce/</link>
    <description>Recent content in Debounce 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.150.0</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 02 Sep 2026 01:24:30 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/en/tags/debounce/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
