<?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: Does your screen reader read phone numbers properly?</title>
	<atom:link href="http://www.nicksmith.co.uk/blog/2007/11/09/does-your-screen-reader-read-phone-numbers-properly/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nicksmith.co.uk/blog/2007/11/09/does-your-screen-reader-read-phone-numbers-properly/</link>
	<description>Spotlight on random items from the web</description>
	<lastBuildDate>Wed, 28 Jul 2010 19:03:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: zaubyw</title>
		<link>http://www.nicksmith.co.uk/blog/2007/11/09/does-your-screen-reader-read-phone-numbers-properly/comment-page-1/#comment-420</link>
		<dc:creator>zaubyw</dc:creator>
		<pubDate>Wed, 05 May 2010 04:57:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicksmith.co.uk/blog/?p=58#comment-420</guid>
		<description>SI49OX  &lt;a href=&quot;http://pimyufovhpol.com/&quot; rel=&quot;nofollow&quot;&gt;pimyufovhpol&lt;/a&gt;, [url=http://eauegehmvtys.com/]eauegehmvtys[/url], [link=http://nvfolznkcwnf.com/]nvfolznkcwnf[/link], http://ctrtikbdmoic.com/</description>
		<content:encoded><![CDATA[<p>SI49OX  <a href="http://pimyufovhpol.com/" rel="nofollow">pimyufovhpol</a>, [url=http://eauegehmvtys.com/]eauegehmvtys[/url], [link=http://nvfolznkcwnf.com/]nvfolznkcwnf[/link], <a href="http://ctrtikbdmoic.com/" rel="nofollow">http://ctrtikbdmoic.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick</title>
		<link>http://www.nicksmith.co.uk/blog/2007/11/09/does-your-screen-reader-read-phone-numbers-properly/comment-page-1/#comment-233</link>
		<dc:creator>nick</dc:creator>
		<pubDate>Tue, 08 Jan 2008 10:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicksmith.co.uk/blog/?p=58#comment-233</guid>
		<description>Thanks Benjamin for the pointer and the link, I hadn&#039;t heard of this. By typing &#039;JAWS E.123&#039; into Google I managed to come across &lt;a href=&quot;http://www.webaim.org/discussion/mail_thread.php?thread=1195&quot; title=&quot;screen readers and telephone numbers&quot; rel=&quot;nofollow&quot;&gt;this discussion&lt;/a&gt; that seems to offer a good background to the issue. I agree with you and the general consensus on the thread that writing phone numbers in a standardised way is the best place to start. From it, a posting by Kynn on 3 March 2003 even describes a solution similar to (although far more tag/css heavy than) the one I&#039;ve described above.

One comment states that any incorrect reading of a phone number is &#039;an inconvenience rather than an obstacle&#039;. I&#039;m not yet convinced of this. As I demonstrated in my example above, if one section of the number is preceded by zero(s), only the succeeding numbers make it into the auditory output; as with the first example where &#039;07000&#039; is interpreted as &#039;seven thousand&#039;. This could be a barrier and the user is left guessing - at least on Mac OS 10.4, which some of us penny-pinchers  are still using ;)

It might look like I&#039;m being pedantic with all of this, in fact this started as a niggle I had with a page that otherwise seemed to work perfectly (so it&#039;s not mission critical). This is more a discussion that I hoped might benefit others and I thank Benjamin and anyone else who wishes to contribute.</description>
		<content:encoded><![CDATA[<p>Thanks Benjamin for the pointer and the link, I hadn&#8217;t heard of this. By typing &#8216;JAWS E.123&#8242; into Google I managed to come across <a href="http://www.webaim.org/discussion/mail_thread.php?thread=1195" title="screen readers and telephone numbers" rel="nofollow">this discussion</a> that seems to offer a good background to the issue. I agree with you and the general consensus on the thread that writing phone numbers in a standardised way is the best place to start. From it, a posting by Kynn on 3 March 2003 even describes a solution similar to (although far more tag/css heavy than) the one I&#8217;ve described above.</p>
<p>One comment states that any incorrect reading of a phone number is &#8216;an inconvenience rather than an obstacle&#8217;. I&#8217;m not yet convinced of this. As I demonstrated in my example above, if one section of the number is preceded by zero(s), only the succeeding numbers make it into the auditory output; as with the first example where &#8217;07000&#8242; is interpreted as &#8216;seven thousand&#8217;. This could be a barrier and the user is left guessing &#8211; at least on Mac OS 10.4, which some of us penny-pinchers  are still using ;)</p>
<p>It might look like I&#8217;m being pedantic with all of this, in fact this started as a niggle I had with a page that otherwise seemed to work perfectly (so it&#8217;s not mission critical). This is more a discussion that I hoped might benefit others and I thank Benjamin and anyone else who wishes to contribute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin Hawkes-Lewis</title>
		<link>http://www.nicksmith.co.uk/blog/2007/11/09/does-your-screen-reader-read-phone-numbers-properly/comment-page-1/#comment-232</link>
		<dc:creator>Benjamin Hawkes-Lewis</dc:creator>
		<pubDate>Mon, 07 Jan 2008 18:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.nicksmith.co.uk/blog/?p=58#comment-232</guid>
		<description>You could give tools like screen readers a better fighting chance by using a standardized notation for telephone numbers:

http://en.wikipedia.org/wiki/E.123</description>
		<content:encoded><![CDATA[<p>You could give tools like screen readers a better fighting chance by using a standardized notation for telephone numbers:</p>
<p><a href="http://en.wikipedia.org/wiki/E.123" rel="nofollow">http://en.wikipedia.org/wiki/E.123</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
