<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Accessibility on Commentary of Takao</title><link>https://takao.blog/en/tags/accessibility/</link><description>Recent content in Accessibility on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/accessibility/index.xml" rel="self" type="application/rss+xml"/><item><title>Accessibility Essentials: When and How to Write WAI-ARIA</title><link>https://takao.blog/en/web/web-accessibility-aria-basics/</link><pubDate>Mon, 15 Sep 2025 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/web-accessibility-aria-basics/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Accessibility Essentials: When and How to Write WAI-ARIA" /&gt;&lt;p&gt;In modern web development, digital accessibility (commonly abbreviated as A11y) is no longer a luxury or an afterthought—it is a core quality standard. Creating interfaces that everyone can navigate, regardless of physical or cognitive ability, begins with semantic HTML.&lt;/p&gt;
&lt;p&gt;However, when building complex, custom UI components like accordions, modal dialogs, and tab panels, standard native HTML elements sometimes fall short in describing their role or state to assistive technologies. That is where &lt;strong&gt;WAI-ARIA (Web Accessibility Initiative - Accessible Rich Internet Applications)&lt;/strong&gt; comes into play.&lt;/p&gt;</description></item></channel></rss>