<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Quiz 2.4.2: Now you see me, now you don&#8217;t</title>
	<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/</link>
	<description>Seeking Best Accessibility Practices</description>
	<pubDate>Sun, 21 Mar 2010 23:19:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: çeviri</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-47428</link>
		<pubDate>Sun, 08 Jul 2007 20:38:25 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-47428</guid>
					<description>Joe: What if I don’t want to read several pages of content to get to the “About Us” link? If I were to follow your suggestion(s), I would need a “Skip to Navigation” link instead. That doesn’t solve anything.</description>
		<content:encoded><![CDATA[<p>Joe: What if I don’t want to read several pages of content to get to the “About Us” link? If I were to follow your suggestion(s), I would need a “Skip to Navigation” link instead. That doesn’t solve anything.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Gino</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-905</link>
		<pubDate>Fri, 06 Jan 2006 03:56:23 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-905</guid>
					<description>I would have to go with b or c. Most users do not need the links, and "a" would just clutter the page. If a page doesn't scroll on forever and if the navigation is well-planned, "a" would not be necessary.</description>
		<content:encoded><![CDATA[<p>I would have to go with b or c. Most users do not need the links, and &#8220;a&#8221; would just clutter the page. If a page doesn&#8217;t scroll on forever and if the navigation is well-planned, &#8220;a&#8221; would not be necessary.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bart Simons</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-243</link>
		<pubDate>Thu, 14 Apr 2005 15:21:09 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-243</guid>
					<description>I don't like a: Dotjay is right (cf. 39).
I'd prefer b.
I am not in favour of c: it should not be left to the designer to create multiple stylesheets with varying accessiblity features. If he would do so, how is he going to explain the differences among them? Will the user understand (a) that he has a choice, (b) what are his options and (c) which options fits best
I personally use D: content first and an 1x1 transparent image entitled "skip text and move to main navigation". The skip link has the first tabindex and the link tot he homepage has the second tabindex. No more tabindexes are available.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t like a: Dotjay is right (cf. 39).<br />
I&#8217;d prefer b.<br />
I am not in favour of c: it should not be left to the designer to create multiple stylesheets with varying accessiblity features. If he would do so, how is he going to explain the differences among them? Will the user understand (a) that he has a choice, (b) what are his options and (c) which options fits best<br />
I personally use D: content first and an 1&#215;1 transparent image entitled &#8220;skip text and move to main navigation&#8221;. The skip link has the first tabindex and the link tot he homepage has the second tabindex. No more tabindexes are available.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Stenhouse</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-216</link>
		<pubDate>Tue, 12 Apr 2005 15:59:13 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-216</guid>
					<description>I'd vote thoeretically for A but practically for B. We all want to do the best job we can for accessibility users but the vast majority of visitors to the vast majority of sites will be completely unaware that some people &lt;em&gt;need&lt;/em&gt; the sort of help that skip links provide. Those folk will be confused and maybe even disoriented by the presence and function of this mystery link. I think it's best to provide the link for 'those in the know' but keep the extras to a minimum for those who don't. B allows you to offer extra functionality to those at the extremes (with screenreaders for example) who really need it and people savvy enough to spot it, but keeps things clean. That said, if you can integrate skip links nicely into the design, then great.

Incidentally, I'd be interested to know what wording people favour for skip links. I favour the positive 'skip to' structure... Future quiz Bob?</description>
		<content:encoded><![CDATA[<p>I&#8217;d vote thoeretically for A but practically for B. We all want to do the best job we can for accessibility users but the vast majority of visitors to the vast majority of sites will be completely unaware that some people <em>need</em> the sort of help that skip links provide. Those folk will be confused and maybe even disoriented by the presence and function of this mystery link. I think it&#8217;s best to provide the link for &#8216;those in the know&#8217; but keep the extras to a minimum for those who don&#8217;t. B allows you to offer extra functionality to those at the extremes (with screenreaders for example) who really need it and people savvy enough to spot it, but keeps things clean. That said, if you can integrate skip links nicely into the design, then great.</p>
<p>Incidentally, I&#8217;d be interested to know what wording people favour for skip links. I favour the positive &#8217;skip to&#8217; structure&#8230; Future quiz Bob?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: vdebolt</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-188</link>
		<pubDate>Sun, 10 Apr 2005 15:27:03 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-188</guid>
					<description>The best way to be sure that it will work for those who need it is A. </description>
		<content:encoded><![CDATA[<p>The best way to be sure that it will work for those who need it is A.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bob Easton</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-187</link>
		<pubDate>Sat, 09 Apr 2005 20:25:13 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-187</guid>
					<description>Mike says:

&lt;blockquote&gt;... Another way to solve to is to make a visible jump link pulldown I suppose. ...&lt;/blockquote&gt;

Oh boy, we're going to have fun when we get to the quiz about making pulldowns accessible.  In a couple of weeks.</description>
		<content:encoded><![CDATA[<p>Mike says:</p>
<blockquote><p>&#8230; Another way to solve to is to make a visible jump link pulldown I suppose. &#8230;</p></blockquote>
<p>Oh boy, we&#8217;re going to have fun when we get to the quiz about making pulldowns accessible.  In a couple of weeks.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike Cherim</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-186</link>
		<pubDate>Sat, 09 Apr 2005 14:26:38 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-186</guid>
					<description>I'd have to go with D, though the switcher seems like a good idea. On a site I'm building right now I have a visible skip navigation link top and left, first link, but from that point I incorporated tab indexes next to each headline. Seems like a decent way to hop around the page by-passing blocks of whatever. Another way to solve to is to make a visible jump link pulldown I suppose. 

Regarding visibility, I say make it visible if the feature is useful to someone. The skip nav on my portfolio site doesn't do much on a 1024x768 res monitor, but it does on an 800x600 or with styles turned off. Thus it's visible. On that site I forewent that checklist requirement on every link block or link list as I felt it would overly clutter the site.</description>
		<content:encoded><![CDATA[<p>I&#8217;d have to go with D, though the switcher seems like a good idea. On a site I&#8217;m building right now I have a visible skip navigation link top and left, first link, but from that point I incorporated tab indexes next to each headline. Seems like a decent way to hop around the page by-passing blocks of whatever. Another way to solve to is to make a visible jump link pulldown I suppose. </p>
<p>Regarding visibility, I say make it visible if the feature is useful to someone. The skip nav on my portfolio site doesn&#8217;t do much on a 1024&#215;768 res monitor, but it does on an 800&#215;600 or with styles turned off. Thus it&#8217;s visible. On that site I forewent that checklist requirement on every link block or link list as I felt it would overly clutter the site.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dotjay</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-185</link>
		<pubDate>Sat, 09 Apr 2005 14:01:15 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-185</guid>
					<description>I just wanted to add a comment about keeping "skip links" visible at all times - my apologies if something similar has already been commented. Personally, I tend to use the "appear on focus" method.

Other times, when I have tried incorporating a visible link into a design, users have come back they don't "get" it. OK, again, it's down to education, but some people are still confused by it. Some of these users are Web-savvy too - one of which has come back saying that the navigation was broken. This was based on the fact that they expected to be taken somewhere by the skip link - they didn't expect such an internal page link.

As far as I see it, if skip links are going to be visible, some sort of standard symbolisation would be the best way to go, with a link to an explanation for such additional meta navigation. However, then you're getting even more visual elements to work into each page.</description>
		<content:encoded><![CDATA[<p>I just wanted to add a comment about keeping &#8220;skip links&#8221; visible at all times - my apologies if something similar has already been commented. Personally, I tend to use the &#8220;appear on focus&#8221; method.</p>
<p>Other times, when I have tried incorporating a visible link into a design, users have come back they don&#8217;t &#8220;get&#8221; it. OK, again, it&#8217;s down to education, but some people are still confused by it. Some of these users are Web-savvy too - one of which has come back saying that the navigation was broken. This was based on the fact that they expected to be taken somewhere by the skip link - they didn&#8217;t expect such an internal page link.</p>
<p>As far as I see it, if skip links are going to be visible, some sort of standard symbolisation would be the best way to go, with a link to an explanation for such additional meta navigation. However, then you&#8217;re getting even more visual elements to work into each page.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bruce Lawson</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-184</link>
		<pubDate>Sat, 09 Apr 2005 08:31:59 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-184</guid>
					<description>I'm with Joe Clark on content-first. In a job I'm on, I can't change the code order, so I'm fighting for  a small icon that is a visible skiplinks. (My next door neighbour has terrible arthritis and hates having to tab-tab-tab-tab-tab to content, but she isn't visually impaired and would miss an invisible skiplinks link).

Charles Belov said, "Some versions or modes of JAWS ignore 1x1 transparent gifs. ". Can you be more specific, Charles? Hard facts will help me win the visible/ invisible battle</description>
		<content:encoded><![CDATA[<p>I&#8217;m with Joe Clark on content-first. In a job I&#8217;m on, I can&#8217;t change the code order, so I&#8217;m fighting for  a small icon that is a visible skiplinks. (My next door neighbour has terrible arthritis and hates having to tab-tab-tab-tab-tab to content, but she isn&#8217;t visually impaired and would miss an invisible skiplinks link).</p>
<p>Charles Belov said, &#8220;Some versions or modes of JAWS ignore 1&#215;1 transparent gifs. &#8220;. Can you be more specific, Charles? Hard facts will help me win the visible/ invisible battle
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: redux</title>
		<link>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-183</link>
		<pubDate>Fri, 08 Apr 2005 22:46:02 +0000</pubDate>
		<guid>http://www.access-matters.com/2005/04/07/quiz-242-now-you-see-me-now-you-dont/#comment-183</guid>
					<description>so, again, the chicken and egg problem: while browser manufacturers don't follow UAAG, it's once again up to us to shoulder the burden via WCAG...*sigh*</description>
		<content:encoded><![CDATA[<p>so, again, the chicken and egg problem: while browser manufacturers don&#8217;t follow UAAG, it&#8217;s once again up to us to shoulder the burden via WCAG&#8230;*sigh*
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
