<?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>ARIA on Codeslog</title>
    <link>https://www.codeslog.com/en/tags/aria/</link>
    <description>Recent content in ARIA 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/aria/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Lighthouse Agentic Browsing, Tested: 2/2 for a Button You Can&#39;t Tab To</title>
      <link>https://www.codeslog.com/en/posts/lighthouse-agentic-browsing-accessibility/</link>
      <pubDate>Sat, 10 Oct 2026 23:55:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/lighthouse-agentic-browsing-accessibility/</guid>
      <description>On test pages, a div button no keyboard can press scored Accessibility 100 and Agentic Browsing 2/2. What the check sees, what it misses, and where agent tools split.</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>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>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>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>Improving Multilingual Blog UX: Building a Smart Language Suggestion Banner</title>
      <link>https://www.codeslog.com/en/posts/language-switcher-banner/</link>
      <pubDate>Fri, 23 Jan 2026 08:00:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/language-switcher-banner/</guid>
      <description>Built a banner that detects browser language via navigator.language and auto-suggests the right version of a Hugo blog, with WCAG 2.2 AA keyboard navigation and screen reader support built in.</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>
    <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>
