<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: AI and Web Accessibility: What Happens When Agents Bypass the Interface?	</title>
	<atom:link href="https://www.designwhine.com/ai-web-accessibility-agents-bypass-interface/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.designwhine.com/ai-web-accessibility-agents-bypass-interface/</link>
	<description>Tech Through A Design Lens</description>
	<lastBuildDate>Wed, 30 Sep 2026 14:47:36 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>
		By: DesignWhine Editorial Team		</title>
		<link>https://www.designwhine.com/ai-web-accessibility-agents-bypass-interface/#comment-322</link>

		<dc:creator><![CDATA[DesignWhine Editorial Team]]></dc:creator>
		<pubDate>Sat, 26 Sep 2026 06:28:33 +0000</pubDate>
		<guid isPermaLink="false">https://www.designwhine.com/?p=17544#comment-322</guid>

					<description><![CDATA[If an AI agent can successfully complete a task that a screen reader user cannot, has the product become more accessible, or have we simply moved the accessibility problem into another layer?]]></description>
			<content:encoded><![CDATA[<p>If an AI agent can successfully complete a task that a screen reader user cannot, has the product become more accessible, or have we simply moved the accessibility problem into another layer?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
