<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Inclusive Design on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/inclusive-design/</link><description>Recent content in Inclusive Design on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/inclusive-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Ensuring Accessibility (A11y) from the Start</title><link>https://ai-blog.noorshomelab.dev/design-systems-guide-2026/ensuring-accessibility/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/design-systems-guide-2026/ensuring-accessibility/</guid><description>&lt;p&gt;Imagine building a beautiful, functional digital product, only to realize a significant portion of your potential users can&amp;rsquo;t navigate it. This isn&amp;rsquo;t just a missed opportunity; it&amp;rsquo;s a barrier. In the world of design systems, ensuring everyone can use your products isn&amp;rsquo;t merely a &amp;ldquo;nice-to-have&amp;rdquo;; it&amp;rsquo;s a fundamental requirement. This chapter dives into a crucial aspect of building any successful design system: &lt;strong&gt;accessibility (A11y)&lt;/strong&gt;. We&amp;rsquo;ll explore why A11y needs to be baked into your system from day one, not bolted on as an afterthought.&lt;/p&gt;</description></item></channel></rss>