<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Daring Fireball Footnotes</title>
	<link>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/</link>
	<description>Seeking Best Accessibility Practices</description>
	<pubDate>Fri, 25 Jul 2008 03:46:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: Andy Affleck</title>
		<link>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-504</link>
		<author>Andy Affleck</author>
		<pubDate>Sat, 23 Jul 2005 15:43:50 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-504</guid>
					<description>I tried to test this in MacOS X Tiger's VoiceOver but I cannot for the life of me figure out how to make links within a single page work. When I select footnote link 1, for example, the page itself scrolls down to the footnote but nothing is read. If I select Control-Option-right arrow (the command to read the next thing) it continues right after the link with "In print..." rather than with the text of the footnote. In messing with settings, I finally did make it jump down and read footnotes but clicking on 1 made it read footnote #2! None of the return buttons worked at all. I have found similar problems with skip-nav links which scroll the page but leave the cursor at the top of the page. I cannot figure out how to make a link within a page ALSO move the cursor of what the screen reader is currently looking at.

So, unless someone can shed some light on this, this doesn't work at all in VoiceOver under MacOS X 10.4.x.

-A</description>
		<content:encoded><![CDATA[<p>I tried to test this in MacOS X Tiger&#8217;s VoiceOver but I cannot for the life of me figure out how to make links within a single page work. When I select footnote link 1, for example, the page itself scrolls down to the footnote but nothing is read. If I select Control-Option-right arrow (the command to read the next thing) it continues right after the link with &#8220;In print&#8230;&#8221; rather than with the text of the footnote. In messing with settings, I finally did make it jump down and read footnotes but clicking on 1 made it read footnote #2! None of the return buttons worked at all. I have found similar problems with skip-nav links which scroll the page but leave the cursor at the top of the page. I cannot figure out how to make a link within a page ALSO move the cursor of what the screen reader is currently looking at.</p>
<p>So, unless someone can shed some light on this, this doesn&#8217;t work at all in VoiceOver under MacOS X 10.4.x.</p>
<p>-A</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Derek Featherstone</title>
		<link>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-505</link>
		<author>Derek Featherstone</author>
		<pubDate>Thu, 28 Jul 2005 12:02:53 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-505</guid>
					<description>Nice one Bob. We'll have to add that to the list of things for the Accessibility Task Force to take to vendors such as GWMicro. Window Eyes should recognize the id fragment identifier as an in-page link, and if they don't, it needs to be fixed.</description>
		<content:encoded><![CDATA[<p>Nice one Bob. We&#8217;ll have to add that to the list of things for the Accessibility Task Force to take to vendors such as GWMicro. Window Eyes should recognize the id fragment identifier as an in-page link, and if they don&#8217;t, it needs to be fixed.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Adrian Higginbotham</title>
		<link>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-513</link>
		<author>Adrian Higginbotham</author>
		<pubDate>Wed, 03 Aug 2005 13:08:47 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-513</guid>
					<description>INTERESTING THAT THE REVIEWER TALKS ABOUT LISTENING TO THE PAGE AS A STREAM AND THE DIFFICULTIES THIS CAUSES. THE ONLY PEOPLE i'VE COME ACROSS WHW EVER USE A SCREENREADER IN THIS WAY ARE DEVELOPERS. IT ISN'T IN MY EXPERIENCE HOW vi PEOPLE USE SCREENREADERS. HAPPY TO BE CONTRADICTED BY ANY SCREENREADER USERS BUT IT'S NOT WHAT i'VE SEEN OR WHAT i HAVE TRAINED.</description>
		<content:encoded><![CDATA[<p>INTERESTING THAT THE REVIEWER TALKS ABOUT LISTENING TO THE PAGE AS A STREAM AND THE DIFFICULTIES THIS CAUSES. THE ONLY PEOPLE i&#8217;VE COME ACROSS WHW EVER USE A SCREENREADER IN THIS WAY ARE DEVELOPERS. IT ISN&#8217;T IN MY EXPERIENCE HOW vi PEOPLE USE SCREENREADERS. HAPPY TO BE CONTRADICTED BY ANY SCREENREADER USERS BUT IT&#8217;S NOT WHAT i&#8217;VE SEEN OR WHAT i HAVE TRAINED.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Anna</title>
		<link>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-904</link>
		<author>Anna</author>
		<pubDate>Fri, 06 Jan 2006 03:46:05 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/07/23/daring-fireball-footnotes/#comment-904</guid>
					<description>Interesting point. The workshops I've gone to stress using the stream. maybe we should test more with those who rely on screenreaders.</description>
		<content:encoded><![CDATA[<p>Interesting point. The workshops I&#8217;ve gone to stress using the stream. maybe we should test more with those who rely on screenreaders.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
