<?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 AI VOID</title><link>https://ai-blog.noorshomelab.dev/categories/accessibility/</link><description>Recent content in Accessibility on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 20 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/categories/accessibility/index.xml" rel="self" type="application/rss+xml"/><item><title>Angular ARIA: Building Accessible Components</title><link>https://ai-blog.noorshomelab.dev/angular-v21-mastery/chapter-12-angular-aria/</link><pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-v21-mastery/chapter-12-angular-aria/</guid><description>&lt;h2 id="angular-aria-building-accessible-components"&gt;Angular ARIA: Building Accessible Components&lt;/h2&gt;
&lt;p&gt;Accessibility (often shortened to &lt;code&gt;a11y&lt;/code&gt;) is a crucial aspect of web development, ensuring that applications can be used by everyone, including people with disabilities. Building accessible components often requires careful management of ARIA (Accessible Rich Internet Applications) attributes, keyboard interactions, and focus management. This can be complex and error-prone.&lt;/p&gt;
&lt;p&gt;Angular v21 introduces the &lt;strong&gt;Angular ARIA library&lt;/strong&gt;, a significant step towards simplifying the creation of accessible UI components. This library provides a collection of &lt;strong&gt;headless directives&lt;/strong&gt; that implement common accessibility patterns without any predefined styles. This empowers developers to fully control the visual appearance of their components while ensuring they are semantically correct and usable for assistive technologies.&lt;/p&gt;</description></item></channel></rss>