<?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>Paper to Pixel &#187; web accessibility</title>
	<atom:link href="http://www.papertopixel.org/category/web-accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.papertopixel.org</link>
	<description>web design tips for graphic designers</description>
	<lastBuildDate>Sun, 08 Aug 2010 09:05:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Multiscreen setup and productivity research</title>
		<link>http://www.papertopixel.org/2010/multiscreen-setup-and-productivity-research/</link>
		<comments>http://www.papertopixel.org/2010/multiscreen-setup-and-productivity-research/#comments</comments>
		<pubDate>Sat, 09 Jan 2010 15:09:34 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/2010/multiscreen-setup-and-productivity-research/</guid>
		<description><![CDATA[I am doing a little research on productivity for one of our projects and I thought I&#8217;d ask you for a little help. 
It&#8217;s really a question for those of you who use double (or more) screen setup at work. Do you find that you are more productive with two screens? Could you give some [...]]]></description>
			<content:encoded><![CDATA[<p>I am doing a little research on productivity for one of our projects and I thought I&#8217;d ask you for a little help. </p>
<p>It&#8217;s really a question for those of you who use double (or more) screen setup at work. Do you find that you are more productive with two screens? Could you give some examples of how you use your two screens setup? Also, if you could let me know how your productivity was affected when you got the 2nd screen.</p>
<p>I know how it affected me but I don&#8217;t want to base this project on my own experiences. So any help would be greatly appreciated.</p>
<p>You can either leave your answers in comments or <a href="http://www.papertopixel.org/contact/">email me</a> directly. </p>
<p>Many thanks for your help.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2010/multiscreen-setup-and-productivity-research/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>7 really basic accessibility tips to remember</title>
		<link>http://www.papertopixel.org/2009/7-really-basic-accessibility-tips-to-remember/</link>
		<comments>http://www.papertopixel.org/2009/7-really-basic-accessibility-tips-to-remember/#comments</comments>
		<pubDate>Mon, 04 May 2009 07:34:12 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[design tips]]></category>
		<category><![CDATA[web accessibility]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=255</guid>
		<description><![CDATA[Do you sometimes wonder who is using your site? Who is your average user, how does he interact with your site, how does he react on graphics and design solutions you used?

Probably yes, we like to do that, it is part of the design process to know how our site will be used
But do you [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Do you sometimes wonder who is using your site? Who is your average user, how does he interact with your site, how does he react on graphics and design solutions you used?<br />
</strong><br />
Probably yes, we like to do that, it is part of the design process to know how our site will be used</p>
<p>But do you sometimes wonder how a person with disabilities will use your site? Will a color blind person be able to still distill information from it? Will he finds a hyperlink somewhere in the text?</p>
<p><span id="more-255"></span>When developing a site we all sometimes overlook some basic methods that we can use to make our site more accessible for everyone. I am ashamed to admit that it happens to me to.</p>
<p>So for you and me I compiled a list of few really basic things to remember and check for to make sure your site is accessible on a basic level at least.</p>
<p><strong>1. Make sure your site works with all css switched off</strong><br />
Your visitors with cognitive disabilities may disable complex layouts to get a more linear presentation, users with color deficiencies or low vision may override your site colors or font sizes. So always make sure that all information on your site’s pages display well without any css styling.</p>
<p><strong>2. Construct your links to have a meaning</strong>, avoid &#8220;click here&#8221;, include a description of where the visitor will be taken if he clicks on a hyperlink i.e. &#8220;read more about our product&#8221;</p>
<p><strong>3. Separate your links</strong><br />
Don&#8217;t use only one white space between consecutive links, screen readers may interpret two or more non-separated links as one</p>
<p><strong>4. Provide text equivalent for non-text data.</strong><br />
Simply, include ALT tag to describe the image, use LONGDESC for longer descriptions. Also, you can simply describe non-text content in your sites copy.</p>
<p><strong>5. Try not using images for links.</strong><br />
Screen readers will not interpret them as a link. If you have to do so though, use ALT attribute to allow screen readers use it as a link.</p>
<p><strong>6. Design color elements in a way that they can be viewed and understand without color as well. </strong>Otherwise color blind visitors may have difficulties to see them.</p>
<p><strong>7. Make sure that your site works with JavaScript switched off. </strong>This is especially important if you use some fancy script for navigation. Make sure that your content can be accessed when the script is turned off as well.</p>
<p><strong>And last but not least, always validate your site to look for potential errors.</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/7-really-basic-accessibility-tips-to-remember/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
