<?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: 12 Accessibility Pitfalls to Avoid</title>
	<atom:link href="http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid/feed" rel="self" type="application/rss+xml" />
	<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid</link>
	<description>Inspiration, CSS Gallery &#38; Community News</description>
	<lastBuildDate>Thu, 18 Mar 2010 02:32:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: nail tek</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-4959</link>
		<dc:creator>nail tek</dc:creator>
		<pubDate>Wed, 17 Mar 2010 09:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-4959</guid>
		<description>I am happy to find result here in the post, thanks for sharing.</description>
		<content:encoded><![CDATA[<p>I am happy to find result here in the post, thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zoya nail polish</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-3543</link>
		<dc:creator>zoya nail polish</dc:creator>
		<pubDate>Tue, 19 Jan 2010 11:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-3543</guid>
		<description>This is very useful information, especially for web designers. Thanks!</description>
		<content:encoded><![CDATA[<p>This is very useful information, especially for web designers. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeff</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-2995</link>
		<dc:creator>jeff</dc:creator>
		<pubDate>Sat, 26 Dec 2009 18:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-2995</guid>
		<description>&quot;Not Using “alt” Attributes on Images&quot;
Dude when was this article written, 1994? Who can&#039;t download images?  Ok I&#039;m done ranting and anxiously look forward to your upcoming article &quot;10 tips for Netscape 3.0&quot;</description>
		<content:encoded><![CDATA[<p>&#8220;Not Using “alt” Attributes on Images&#8221;<br />
Dude when was this article written, 1994? Who can&#8217;t download images?  Ok I&#8217;m done ranting and anxiously look forward to your upcoming article &#8220;10 tips for Netscape 3.0&#8243;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne State Web Communications Blog &#187; Blog Archive &#187; [Friday Links] The Thanksgiving Edition</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1765</link>
		<dc:creator>Wayne State Web Communications Blog &#187; Blog Archive &#187; [Friday Links] The Thanksgiving Edition</dc:creator>
		<pubDate>Sun, 29 Nov 2009 15:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1765</guid>
		<description>[...] 12 Accessibility Pitfalls to Avoid &#124; Design Shack [...]</description>
		<content:encoded><![CDATA[<p>[...] 12 Accessibility Pitfalls to Avoid | Design Shack [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Axe</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1746</link>
		<dc:creator>Web Axe</dc:creator>
		<pubDate>Fri, 27 Nov 2009 20:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1746</guid>
		<description>Nice article. Would love to see Headings on the list (markup as well as usage). Also, requiring JavaScript for core functionality is a big no-no.</description>
		<content:encoded><![CDATA[<p>Nice article. Would love to see Headings on the list (markup as well as usage). Also, requiring JavaScript for core functionality is a big no-no.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Autocrat</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1726</link>
		<dc:creator>Autocrat</dc:creator>
		<pubDate>Thu, 26 Nov 2009 00:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1726</guid>
		<description>What concerns me is that even today - after Years of design development, studies, articles etc. - there are Still people asking questions about this stuff!

There is No lack of information about Better Design/Coding Practices.
If people actually bothered to learn what they were doing - rather than being reliant on Dreamweaver and Photoshop - we wouldn&#039;t have so many sucky sites!

Worse - you do Not know who to trust.
Jsut go look at the Guild of Accessible Web Designers (GAWD) - and resize your text!
Possible one of the Most Common requirements of users is to be able to adjust the text size - and so many sites literally break (I know - bad pun too).

There&#039;s no excuse people.
The information is out there.
It&#039;s jsut down to plain ignorance and laziness that you don&#039;t already have the answers.
It also goes to show that you are Not testing your stuff out!

Go look at things like CSS Gardens etc.
Look at how many of those &quot;beautiful&quot; designs actually suck when it comes to being functional!

.

So - here&#039;s the general idea.
Build it plain.
Make sure it works.

Make sure that it works with the keyboard and gives responses in the same ways as it does for Mouse.
Yes, that means you should be using :focus and :active (cover ie6) as well as  :hover.

Make sure you can resize text.
Do Not make things of fixed height - and if you do - set overflow on it!
If you want set measuerment - use EMs, and set heights in EMs - then things scale.

Check the colours you are using - make sure there is Contrast!
MAke sure there is contrast before you start slappign in image backgrounds ... and after the images are in - make sure there is still contrast!

Stuff like that is written All Over the Net!
Seriously - try Googling for it!

.

The distinction between Usability/Acessibility can be a little slim at times.
Increasing the response zone of a link with padding ... is both A and U.
Making sure that labels/inputs respond visually ... is both A and U.

Lets face it - if you improve the Accessibiltiy of the site (or at least bring it up to the bsics it should be at), you are improving the Usability of the site for that user-group, yes?

.

Okay - lecture over.
Sorry
;)</description>
		<content:encoded><![CDATA[<p>What concerns me is that even today &#8211; after Years of design development, studies, articles etc. &#8211; there are Still people asking questions about this stuff!</p>
<p>There is No lack of information about Better Design/Coding Practices.<br />
If people actually bothered to learn what they were doing &#8211; rather than being reliant on Dreamweaver and Photoshop &#8211; we wouldn&#8217;t have so many sucky sites!</p>
<p>Worse &#8211; you do Not know who to trust.<br />
Jsut go look at the Guild of Accessible Web Designers (GAWD) &#8211; and resize your text!<br />
Possible one of the Most Common requirements of users is to be able to adjust the text size &#8211; and so many sites literally break (I know &#8211; bad pun too).</p>
<p>There&#8217;s no excuse people.<br />
The information is out there.<br />
It&#8217;s jsut down to plain ignorance and laziness that you don&#8217;t already have the answers.<br />
It also goes to show that you are Not testing your stuff out!</p>
<p>Go look at things like CSS Gardens etc.<br />
Look at how many of those &#8220;beautiful&#8221; designs actually suck when it comes to being functional!</p>
<p>.</p>
<p>So &#8211; here&#8217;s the general idea.<br />
Build it plain.<br />
Make sure it works.</p>
<p>Make sure that it works with the keyboard and gives responses in the same ways as it does for Mouse.<br />
Yes, that means you should be using :focus and :active (cover ie6) as well as  :hover.</p>
<p>Make sure you can resize text.<br />
Do Not make things of fixed height &#8211; and if you do &#8211; set overflow on it!<br />
If you want set measuerment &#8211; use EMs, and set heights in EMs &#8211; then things scale.</p>
<p>Check the colours you are using &#8211; make sure there is Contrast!<br />
MAke sure there is contrast before you start slappign in image backgrounds &#8230; and after the images are in &#8211; make sure there is still contrast!</p>
<p>Stuff like that is written All Over the Net!<br />
Seriously &#8211; try Googling for it!</p>
<p>.</p>
<p>The distinction between Usability/Acessibility can be a little slim at times.<br />
Increasing the response zone of a link with padding &#8230; is both A and U.<br />
Making sure that labels/inputs respond visually &#8230; is both A and U.</p>
<p>Lets face it &#8211; if you improve the Accessibiltiy of the site (or at least bring it up to the bsics it should be at), you are improving the Usability of the site for that user-group, yes?</p>
<p>.</p>
<p>Okay &#8211; lecture over.<br />
Sorry<br />
;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Big D</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1723</link>
		<dc:creator>Big D</dc:creator>
		<pubDate>Wed, 25 Nov 2009 16:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1723</guid>
		<description>&quot;Usability isn’t an exact science.&quot;  You are correct.  It&#039;s not.  Usability is also not accessibility, either.  

So what is your article really about? Since you offer tips about accessibility and usability and do not distinguish between the two, you leave people just as confused as when they arrived here.  You&#039;ve caused more problems than you attempted to solve.</description>
		<content:encoded><![CDATA[<p>&#8220;Usability isn’t an exact science.&#8221;  You are correct.  It&#8217;s not.  Usability is also not accessibility, either.  </p>
<p>So what is your article really about? Since you offer tips about accessibility and usability and do not distinguish between the two, you leave people just as confused as when they arrived here.  You&#8217;ve caused more problems than you attempted to solve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mes favoris du 24-11-09 au 25-11-09</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1718</link>
		<dc:creator>Mes favoris du 24-11-09 au 25-11-09</dc:creator>
		<pubDate>Wed, 25 Nov 2009 09:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1718</guid>
		<description>[...] 12 Accessibility Pitfalls to Avoid &#124; Design Shack&#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] 12 Accessibility Pitfalls to Avoid | Design Shack&nbsp; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lane</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1705</link>
		<dc:creator>Lane</dc:creator>
		<pubDate>Tue, 24 Nov 2009 16:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1705</guid>
		<description>I think the word you are looking for near the beginning is &quot;granted&quot; not &quot;grant it&quot;.

And why didn&#039;t you follow your own advice about alt tags on images? I don&#039;t think many people would consider &quot;screenshot&quot; to be a helpful alternative to seeing the actual picture.</description>
		<content:encoded><![CDATA[<p>I think the word you are looking for near the beginning is &#8220;granted&#8221; not &#8220;grant it&#8221;.</p>
<p>And why didn&#8217;t you follow your own advice about alt tags on images? I don&#8217;t think many people would consider &#8220;screenshot&#8221; to be a helpful alternative to seeing the actual picture.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Design Informer</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1695</link>
		<dc:creator>Design Informer</dc:creator>
		<pubDate>Tue, 24 Nov 2009 01:41:34 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1695</guid>
		<description>great article! Thank you for this awesome article. Going through my site now and applying these.</description>
		<content:encoded><![CDATA[<p>great article! Thank you for this awesome article. Going through my site now and applying these.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1693</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Mon, 23 Nov 2009 20:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1693</guid>
		<description>AKA, Usability 101. Good deal reiterating these points to those who have not burned them into their brains yet (for lack of intuitively realizing them), though.

But on the last point (Complicated Drop Down Menus), I would say that in some applications (ie: ecommerce) they increase usability as they reduce the time it takes to reach a subcategory.</description>
		<content:encoded><![CDATA[<p>AKA, Usability 101. Good deal reiterating these points to those who have not burned them into their brains yet (for lack of intuitively realizing them), though.</p>
<p>But on the last point (Complicated Drop Down Menus), I would say that in some applications (ie: ecommerce) they increase usability as they reduce the time it takes to reach a subcategory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor Saint</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1686</link>
		<dc:creator>Trevor Saint</dc:creator>
		<pubDate>Mon, 23 Nov 2009 11:53:36 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1686</guid>
		<description>Love the article. Well written, and easy to read. And a nice memory refresher.</description>
		<content:encoded><![CDATA[<p>Love the article. Well written, and easy to read. And a nice memory refresher.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Federica Sibella</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1683</link>
		<dc:creator>Federica Sibella</dc:creator>
		<pubDate>Mon, 23 Nov 2009 08:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1683</guid>
		<description>Hi Joshua, useful post indeed. I completely agree on the overuse of Flash: it&#039;s maybe very pleasant but too often hard to use. The correct use of label in the forms is also a very good reminder. On the other side I&#039;m not so convinced about the vague link paragraph: sometimes a &quot;click to download&quot; is clearer for the user if the explanation about what is to be downloaded was previously given.</description>
		<content:encoded><![CDATA[<p>Hi Joshua, useful post indeed. I completely agree on the overuse of Flash: it&#8217;s maybe very pleasant but too often hard to use. The correct use of label in the forms is also a very good reminder. On the other side I&#8217;m not so convinced about the vague link paragraph: sometimes a &#8220;click to download&#8221; is clearer for the user if the explanation about what is to be downloaded was previously given.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepak Chaudhary</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1681</link>
		<dc:creator>Deepak Chaudhary</dc:creator>
		<pubDate>Mon, 23 Nov 2009 06:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1681</guid>
		<description>Hey Joshua, Very interesting and correctly evaluated and written article!! Some of the things like &quot;title&quot; for images etc are very common but designers tend to ignore them in a hurry!! Thanks for this!!</description>
		<content:encoded><![CDATA[<p>Hey Joshua, Very interesting and correctly evaluated and written article!! Some of the things like &#8220;title&#8221; for images etc are very common but designers tend to ignore them in a hurry!! Thanks for this!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 12 Accessibility Pitfalls from Design Shack &#171; Blog of Northwich Web Designer TheDaveyB</title>
		<link>http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid#comment-1680</link>
		<dc:creator>12 Accessibility Pitfalls from Design Shack &#171; Blog of Northwich Web Designer TheDaveyB</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:18:02 +0000</pubDate>
		<guid isPermaLink="false">http://designshack.co.uk/?p=3245#comment-1680</guid>
		<description>[...] Read it &#8211; http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid [...]</description>
		<content:encoded><![CDATA[<p>[...] Read it &#8211; <a href="http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid" rel="nofollow">http://designshack.co.uk/articles/accessibility/12-accessibility-pitfalls-to-avoid</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
