<?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>Accessibility Tips &#187; top</title>
	<atom:link href="http://accessibilitytips.com/tag/top/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessibilitytips.com</link>
	<description>A collection of tips, guidance and practical suggestions in developing accessible websites</description>
	<lastBuildDate>Sat, 02 May 2009 05:07:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Positioning content offscreen</title>
		<link>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/</link>
		<comments>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/#comments</comments>
		<pubDate>Wed, 05 Mar 2008 04:52:42 +0000</pubDate>
		<dc:creator>Isofarro</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[absolute]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[focus]]></category>
		<category><![CDATA[keyboard]]></category>
		<category><![CDATA[left]]></category>
		<category><![CDATA[offscreen]]></category>
		<category><![CDATA[position]]></category>
		<category><![CDATA[screenreaders]]></category>
		<category><![CDATA[scroll]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[top]]></category>

		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=6</guid>
		<description><![CDATA[In cases where we need to hide content from a visitor but still make it available to the screenreader, we position it offscreen. The simplest way to do that with CSS is to use the following style: .offscreen { position: absolute; left: -999em; } Avoid offscreen using top A typical mistake is also to set [...]]]></description>
			<content:encoded><![CDATA[<p>In cases where we need to hide content from a visitor but still make it available to the screenreader, we position it offscreen.</p>
<p>The simplest way to do that with CSS is to use the following style:</p>
<pre>
<code>
.offscreen {
    position: absolute;
    left: -999em;
}
</code>
</pre>
<h2>Avoid offscreen using <code>top</code></h2>
<p>A typical mistake is also to set the <code>top</code> property to a negative value in the same style rule. This just about works when the content originally appears at the very top of the page &#8211; like a set of skiplinks.</p>
<p>But, if the content you are hiding is originally below the fold on the screen, when a focusable element in the off-screen styled content receives focus, the page scrolls right to the top of the document trying to bring this content into view. This jump in content creates confusion for keyboard users, and screen magnifier users.</p>
<p>What is just as bad is when the user tabs again, the page again jumps, this time downward to the next focusable element.</p>
<p>When a container of content is positioned offscreen, the focusable elements within still remain in their original tab orders, so they will receive focus as if the content were still in its original place in the document flow.</p>
<p>Offscreen positioning using <code>top</code> interfers with the expectation that focusable content is in a top down order. Offscreen left doesn&#8217;t suffer the same fate because the vertical positioning of the content hasn&#8217;t changed, so no upwards scrolling is required.</p>
<h2>Move focused offscreen content back onscreen</h2>
<p><strong>Note:</strong> When positioning content offscreen which contains focusable elements, you should also ensure that when those focusable elements receive focus that they are brought back into the current viewport. This is necessary so that keyboard users can see the content.</p>
]]></content:encoded>
			<wfw:commentRss>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

