<?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: Positioning content offscreen</title>
	<atom:link href="http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/feed/" rel="self" type="application/rss+xml" />
	<link>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/</link>
	<description>A collection of tips, guidance and practical suggestions in developing accessible websites</description>
	<lastBuildDate>Thu, 14 Jan 2010 17:51:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Kniskern</title>
		<link>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/comment-page-1/#comment-230</link>
		<dc:creator>Michael Kniskern</dc:creator>
		<pubDate>Thu, 14 Jan 2010 17:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=6#comment-230</guid>
		<description>I did discover an issue with trying to place an item off screen within an asp:UpdatePanel control.  On the initial page load, the item is hidden using the suggested CSS class.  When the panel is updated by one of the asynchronous triggers, the item looses the CSS class configuration and is displayed on the page.

This only happens in Internet Explorer 7.  It works in FireFox.</description>
		<content:encoded><![CDATA[<p>I did discover an issue with trying to place an item off screen within an asp:UpdatePanel control.  On the initial page load, the item is hidden using the suggested CSS class.  When the panel is updated by one of the asynchronous triggers, the item looses the CSS class configuration and is displayed on the page.</p>
<p>This only happens in Internet Explorer 7.  It works in FireFox.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Fitzsimons</title>
		<link>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/comment-page-1/#comment-166</link>
		<dc:creator>Nick Fitzsimons</dc:creator>
		<pubDate>Tue, 19 May 2009 13:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=6#comment-166</guid>
		<description>Also worthy of note is that on a page using a right-to-left writing system (e.g. http://news.bbc.co.uk/hi/arabic/news/), positioning to the left will cause a horizontal scrollbar to appear, allowing the positioned content to be scrolled into view; the content should be positioned to the right instead.

Clearly this isn&#039;t a problem when one has control of the site and can guarantee that only left-to-right writing systems will ever be used, but it needs to be borne in mind by those creating (for example) templates, or content management systems that may be used with other languages.</description>
		<content:encoded><![CDATA[<p>Also worthy of note is that on a page using a right-to-left writing system (e.g. <a href="http://news.bbc.co.uk/hi/arabic/news/)" rel="nofollow">http://news.bbc.co.uk/hi/arabic/news/)</a>, positioning to the left will cause a horizontal scrollbar to appear, allowing the positioned content to be scrolled into view; the content should be positioned to the right instead.</p>
<p>Clearly this isn&#8217;t a problem when one has control of the site and can guarantee that only left-to-right writing systems will ever be used, but it needs to be borne in mind by those creating (for example) templates, or content management systems that may be used with other languages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isofarro</title>
		<link>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/comment-page-1/#comment-3</link>
		<dc:creator>Isofarro</dc:creator>
		<pubDate>Wed, 04 Mar 2009 15:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=6#comment-3</guid>
		<description>Interesting point about the right: 101%.

John mentions: &quot;some times the designer is not in control of the contents of the offscreen content (supplied by a third party, for instance). Therefore, we cannot guarantee its width. 999em certainly seems like a large enough offset&quot;

It is worth fixing a width on the offscreened content in that instance, at least to something less than 999em. However, I wouldn&#039;t advise 1px. Make it something sensible.</description>
		<content:encoded><![CDATA[<p>Interesting point about the right: 101%.</p>
<p>John mentions: &#8220;some times the designer is not in control of the contents of the offscreen content (supplied by a third party, for instance). Therefore, we cannot guarantee its width. 999em certainly seems like a large enough offset&#8221;</p>
<p>It is worth fixing a width on the offscreened content in that instance, at least to something less than 999em. However, I wouldn&#8217;t advise 1px. Make it something sensible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: unscriptable</title>
		<link>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/comment-page-1/#comment-5</link>
		<dc:creator>unscriptable</dc:creator>
		<pubDate>Wed, 04 Mar 2009 13:05:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=6#comment-5</guid>
		<description>Great point, Isafarro!  Accessibility is new to me even though I&#039;ve been working on web apps since 1996.  (I know, typical story.)

I&#039;d like to mention that using the left property to prevent this problem relies on not having a horizontal scrollbar.  Horizontal scrolling is undesirable so we typically avoid it, anyways, so it almost doesn&#039;t need mentioning.

You may want to consider using the right property instead of the left property.  Here&#039;s why: some times the designer is not in control of the contents of the offscreen content (supplied by a third party, for instance).  Therefore, we cannot guarantee its width.  999em certainly seems like a large enough offset, but I&#039;ve seen third-party content that was improperly formatted (and therefore didn&#039;t word-wrap for instance).  Furthermore, IE6 (ugh) can have performance difficulties when placing content more than a few thousand pixels off the page.

Using right:101% is much more likely to place the content offscreen.  There&#039;s still no guarantee that it is truly offscreen even if we also specify other properties like overflow:hidden, but every bit helps.

.offscreen {
    position: absolute;
    right: 101%;
    overflow: hidden;
}

That&#039;s what I use .... er ... what I WILL use now that I know not to use the top property!

-- John</description>
		<content:encoded><![CDATA[<p>Great point, Isafarro!  Accessibility is new to me even though I&#8217;ve been working on web apps since 1996.  (I know, typical story.)</p>
<p>I&#8217;d like to mention that using the left property to prevent this problem relies on not having a horizontal scrollbar.  Horizontal scrolling is undesirable so we typically avoid it, anyways, so it almost doesn&#8217;t need mentioning.</p>
<p>You may want to consider using the right property instead of the left property.  Here&#8217;s why: some times the designer is not in control of the contents of the offscreen content (supplied by a third party, for instance).  Therefore, we cannot guarantee its width.  999em certainly seems like a large enough offset, but I&#8217;ve seen third-party content that was improperly formatted (and therefore didn&#8217;t word-wrap for instance).  Furthermore, IE6 (ugh) can have performance difficulties when placing content more than a few thousand pixels off the page.</p>
<p>Using right:101% is much more likely to place the content offscreen.  There&#8217;s still no guarantee that it is truly offscreen even if we also specify other properties like overflow:hidden, but every bit helps.</p>
<p>.offscreen {<br />
    position: absolute;<br />
    right: 101%;<br />
    overflow: hidden;<br />
}</p>
<p>That&#8217;s what I use &#8230;. er &#8230; what I WILL use now that I know not to use the top property!</p>
<p>&#8211; John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Amos</title>
		<link>http://accessibilitytips.com/2008/03/04/positioning-content-offscreen/comment-page-1/#comment-2</link>
		<dc:creator>Jim Amos</dc:creator>
		<pubDate>Sun, 30 Mar 2008 03:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.wp-dev.isolutia.com/?p=6#comment-2</guid>
		<description>I actually didn&#039;t realize this about position:top. Now I need to go change all instances of my usual &#039;replaced&#039; class to use left instead. Thanks!</description>
		<content:encoded><![CDATA[<p>I actually didn&#8217;t realize this about position:top. Now I need to go change all instances of my usual &#8216;replaced&#8217; class to use left instead. Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
