<?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: Creating an Accessible Checkout Progress Bar</title>
	<atom:link href="http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/</link>
	<description></description>
	<lastBuildDate>Wed, 14 Jul 2010 18:19:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert Spangler</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-8481</link>
		<dc:creator>Robert Spangler</dc:creator>
		<pubDate>Tue, 02 Feb 2010 19:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-8481</guid>
		<description>Hey Ian, I think your solution is right on.

One thing that might be helpful would be to make the text more conversational such as &quot;You&#039;re currently on step: Confirm Your Order.&quot;

Thanks for the input, great idea.</description>
		<content:encoded><![CDATA[<p>Hey Ian, I think your solution is right on.</p>
<p>One thing that might be helpful would be to make the text more conversational such as &#8220;You&#8217;re currently on step: Confirm Your Order.&#8221;</p>
<p>Thanks for the input, great idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-8479</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Sat, 30 Jan 2010 10:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-8479</guid>
		<description>Hi Andy

This is an interesting and informative post. I am currently implementing something similar and I have a couple of observations on which I&#039;d be interested in your (and anyone else&#039;s) feedback.

1. How do you indicate to a screen-reader which item is highlighted? In order to satisfy DDA requirements, information that is conveyed by an image (e.g. the progress bar image) also needs to be conveyed by screen-reader accessible text on the page. For step 3 from your example page I would implement it as below; inserting &quot; (selected)&quot; after the step name provided within the  tags.

Step 3

	&lt;a title=&quot;Return to Checkout&quot; href=&quot;#&quot; rel=&quot;nofollow&quot;&gt;Checkout&lt;/a&gt;
	&lt;a title=&quot;Return to Billing and Shipping&quot; href=&quot;#&quot; rel=&quot;nofollow&quot;&gt;Billing and Shipping&lt;/a&gt;
	Confirm Your Order (selected)
	Complete Order


2. When I last researched the issue, most screen-readers do not come pre-configured to read out the title text of a link. It is entirely possible that this situation has changed, but if this is still the case I would be inclined to further modify the example by placing the &quot;Return to&quot; text inside   instead of using title text. I would also be consider using &quot;Back to&quot; and &quot;Forward to&quot;, rather than &quot;Return to&quot; as these re-enforce the ordering by indicating the direction through the process that the user would be moving. Further modifying the above example with the steps above and to add a forward link for the final step this would become:

Step 3

	&lt;a href=&quot;#&quot; rel=&quot;nofollow&quot;&gt;Back to Checkout&lt;/a&gt;
	&lt;a href=&quot;#&quot; rel=&quot;nofollow&quot;&gt;Back to Billing and Shipping&lt;/a&gt;
	Confirm Your Order (selected)
	&lt;a href=&quot;#&quot; rel=&quot;nofollow&quot;&gt;Forward to Complete Order&lt;/a&gt;


Many thanks

Ian</description>
		<content:encoded><![CDATA[<p>Hi Andy</p>
<p>This is an interesting and informative post. I am currently implementing something similar and I have a couple of observations on which I&#8217;d be interested in your (and anyone else&#8217;s) feedback.</p>
<p>1. How do you indicate to a screen-reader which item is highlighted? In order to satisfy DDA requirements, information that is conveyed by an image (e.g. the progress bar image) also needs to be conveyed by screen-reader accessible text on the page. For step 3 from your example page I would implement it as below; inserting &#8221; (selected)&#8221; after the step name provided within the  tags.</p>
<p>Step 3</p>
<p>	<a title="Return to Checkout" href="#" rel="nofollow">Checkout</a><br />
	<a title="Return to Billing and Shipping" href="#" rel="nofollow">Billing and Shipping</a><br />
	Confirm Your Order (selected)<br />
	Complete Order</p>
<p>2. When I last researched the issue, most screen-readers do not come pre-configured to read out the title text of a link. It is entirely possible that this situation has changed, but if this is still the case I would be inclined to further modify the example by placing the &#8220;Return to&#8221; text inside   instead of using title text. I would also be consider using &#8220;Back to&#8221; and &#8220;Forward to&#8221;, rather than &#8220;Return to&#8221; as these re-enforce the ordering by indicating the direction through the process that the user would be moving. Further modifying the above example with the steps above and to add a forward link for the final step this would become:</p>
<p>Step 3</p>
<p>	<a href="#" rel="nofollow">Back to Checkout</a><br />
	<a href="#" rel="nofollow">Back to Billing and Shipping</a><br />
	Confirm Your Order (selected)<br />
	<a href="#" rel="nofollow">Forward to Complete Order</a></p>
<p>Many thanks</p>
<p>Ian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Higdon</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-3785</link>
		<dc:creator>Craig Higdon</dc:creator>
		<pubDate>Thu, 09 Apr 2009 17:32:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-3785</guid>
		<description>Great post!

You might be interested in a similar article that creates &lt;a href=&quot;http://blog.vortx.com/adnsf/fast-and-easy-custom-buttons/&quot; rel=&quot;nofollow&quot;&gt;CSS custom buttons&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Great post!</p>
<p>You might be interested in a similar article that creates <a href="http://blog.vortx.com/adnsf/fast-and-easy-custom-buttons/" rel="nofollow">CSS custom buttons</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-1593</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Fri, 05 Dec 2008 17:32:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-1593</guid>
		<description>Thank you for that link! I was dying to find samples for this progress bar I have to design. you just saved my day!!!</description>
		<content:encoded><![CDATA[<p>Thank you for that link! I was dying to find samples for this progress bar I have to design. you just saved my day!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TraiaN</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-1153</link>
		<dc:creator>TraiaN</dc:creator>
		<pubDate>Tue, 18 Nov 2008 20:25:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-1153</guid>
		<description>The link to the article should be www.pitstopmedia.com/sem/checkout-progress-bar-survey.

Thanks!</description>
		<content:encoded><![CDATA[<p>The link to the article should be <a href="http://www.pitstopmedia.com/sem/checkout-progress-bar-survey" rel="nofollow">http://www.pitstopmedia.com/sem/checkout-progress-bar-survey</a>.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TraiaN</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-1152</link>
		<dc:creator>TraiaN</dc:creator>
		<pubDate>Tue, 18 Nov 2008 20:24:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-1152</guid>
		<description>Hi ,

Talking about the progress bars, I also did some research on major etailers and how do they display the bar. I wrote an article about the findings, called CHECKOUT - Progress Bar Survey&lt;/a&gt;. Take a look and please let me know what you think.


Cheers,
TraiaN</description>
		<content:encoded><![CDATA[<p>Hi ,</p>
<p>Talking about the progress bars, I also did some research on major etailers and how do they display the bar. I wrote an article about the findings, called CHECKOUT &#8211; Progress Bar Survey. Take a look and please let me know what you think.</p>
<p>Cheers,<br />
TraiaN</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Spangler</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-38</link>
		<dc:creator>Robert Spangler</dc:creator>
		<pubDate>Fri, 07 Dec 2007 21:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-38</guid>
		<description>Thanks Andy! I&#039;m glad you found it helpful.</description>
		<content:encoded><![CDATA[<p>Thanks Andy! I&#8217;m glad you found it helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Stratton</title>
		<link>http://www.groovecommerce.com/ecommerce-blog/ecommerce-web-site-design/creating-an-accessible-checkout-progress-bar/comment-page-1/#comment-37</link>
		<dc:creator>Andy Stratton</dc:creator>
		<pubDate>Fri, 07 Dec 2007 16:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovecommerce.com/ecommerce-blog/featured/creating-an-accessible-checkout-progress-bar/#comment-37</guid>
		<description>This is a great post, Rob.  Nothing better than some accessibly aesthetic and semantic markup.</description>
		<content:encoded><![CDATA[<p>This is a great post, Rob.  Nothing better than some accessibly aesthetic and semantic markup.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
