<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Vernon Fowler</title>
	<atom:link href="https://vfowler.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://vfowler.com/</link>
	<description>Designing inclusive and engaging digital experiences</description>
	<lastBuildDate>Fri, 11 Apr 2025 08:46:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>

<image>
	<url>https://vfowler.com/wp-content/uploads/2017/07/cropped-12093240_919711241399290_1980059382_n-32x32.jpg</url>
	<title>Vernon Fowler</title>
	<link>https://vfowler.com/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Task ease metric to focus usability improvements</title>
		<link>https://vfowler.com/task-ease-metric-to-focus-usability-improvements/</link>
					<comments>https://vfowler.com/task-ease-metric-to-focus-usability-improvements/#respond</comments>
		
		<dc:creator><![CDATA[Vernon]]></dc:creator>
		<pubDate>Thu, 27 Feb 2025 22:48:49 +0000</pubDate>
				<category><![CDATA[Portfolio]]></category>
		<category><![CDATA[metrics]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[usability]]></category>
		<guid isPermaLink="false">https://vfowler.com/?p=2244</guid>

					<description><![CDATA[<p>Gathering task ease ratings in usability testing proved valuable for collecting task-level insights and focusing usability improvements.</p>
<p>The post <a href="https://vfowler.com/task-ease-metric-to-focus-usability-improvements/">Task ease metric to focus usability improvements</a> appeared first on <a href="https://vfowler.com">Vernon Fowler</a>.</p>
]]></description>
		
					<wfw:commentRss>https://vfowler.com/task-ease-metric-to-focus-usability-improvements/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The art of writing accessibility issue documentation</title>
		<link>https://vfowler.com/the-art-of-writing-accessibility-issue-documentation/</link>
					<comments>https://vfowler.com/the-art-of-writing-accessibility-issue-documentation/#respond</comments>
		
		<dc:creator><![CDATA[Vernon]]></dc:creator>
		<pubDate>Tue, 18 Feb 2025 23:42:00 +0000</pubDate>
				<category><![CDATA[Portfolio]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[testing]]></category>
		<guid isPermaLink="false">https://vfowler.com/?p=2236</guid>

					<description><![CDATA[<p>There are several ingredients for effective accessibility issue documentation. In this post, I describe what I include in writing accessibility issues and how that helps progress remediation work.</p>
<p>The post <a href="https://vfowler.com/the-art-of-writing-accessibility-issue-documentation/">The art of writing accessibility issue documentation</a> appeared first on <a href="https://vfowler.com">Vernon Fowler</a>.</p>
]]></description>
		
					<wfw:commentRss>https://vfowler.com/the-art-of-writing-accessibility-issue-documentation/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Faster and better component documentation with AI</title>
		<link>https://vfowler.com/faster-and-better-component-documentation-with-ai/</link>
		
		<dc:creator><![CDATA[Vernon]]></dc:creator>
		<pubDate>Mon, 04 Dec 2023 02:52:03 +0000</pubDate>
				<category><![CDATA[Portfolio]]></category>
		<category><![CDATA[design system]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[processes]]></category>
		<guid isPermaLink="false">https://vfowler.com/?p=1972</guid>

					<description><![CDATA[<p>I use generative AI to batch write component documentation drafts so that I can produce them faster and with higher quality.</p>
<p>The post <a href="https://vfowler.com/faster-and-better-component-documentation-with-ai/">Faster and better component documentation with AI</a> appeared first on <a href="https://vfowler.com">Vernon Fowler</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Uplifted team capability for continuous accessibility</title>
		<link>https://vfowler.com/accessibility-acceptance-criteria-design-stories-development-testing/</link>
					<comments>https://vfowler.com/accessibility-acceptance-criteria-design-stories-development-testing/#comments</comments>
		
		<dc:creator><![CDATA[Vernon]]></dc:creator>
		<pubDate>Thu, 30 Nov 2023 01:49:42 +0000</pubDate>
				<category><![CDATA[Case studies]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[processes]]></category>
		<guid isPermaLink="false">https://vfowler.com/?p=1934</guid>

					<description><![CDATA[<p>Accessibility Acceptance Criteria gave us a fast way to design, build, and test a product feature with accessibility baked in from the start.</p>
<p>The post <a href="https://vfowler.com/accessibility-acceptance-criteria-design-stories-development-testing/">Uplifted team capability for continuous accessibility</a> appeared first on <a href="https://vfowler.com">Vernon Fowler</a>.</p>
]]></description>
		
					<wfw:commentRss>https://vfowler.com/accessibility-acceptance-criteria-design-stories-development-testing/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
