<?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: Derek Featherstone — Designing for Accessibility</title> <atom:link href="http://www.webdirections.org/notes/derek-featherstone-designing-for-accessibility/feed/" rel="self" type="application/rss+xml" /><link>http://www.webdirections.org/notes/derek-featherstone-designing-for-accessibility/</link> <description>Just another WordPress weblog</description> <lastBuildDate>Thu, 11 Mar 2010 01:41:33 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: WD06 - Day 4 Musings at Mad Web Blog</title><link>http://www.webdirections.org/notes/derek-featherstone-designing-for-accessibility/comment-page-1/#comment-204</link> <dc:creator>WD06 - Day 4 Musings at Mad Web Blog</dc:creator> <pubDate>Mon, 23 Oct 2006 13:01:57 +0000</pubDate> <guid
isPermaLink="false">http://westciv.com/webdirections08/blog/derek-featherstone-designing-for-accessibility/#comment-204</guid> <description>[...] Derek Featherstone was next, with Designing for Accessibility. I didn&#8217;t take any notes for this talk, as I felt it was a little on the obvious side, however, there were a number of good points made which got me thinking about assistive technologies other than screen readers, like magnifiyers, hotkeys and tab indexed. [...]</description> <content:encoded><![CDATA[<p>[…] Derek Featherstone was next, with Designing for Accessibility. I didn’t take any notes for this talk, as I felt it was a little on the obvious side, however, there were a number of good points made which got me thinking about assistive technologies other than screen readers, like magnifiyers, hotkeys and tab indexed. […]</p> ]]></content:encoded> </item> <item><title>By: Amy Stephen &#187; Blog Archive &#187; links for 2006-10-03</title><link>http://www.webdirections.org/notes/derek-featherstone-designing-for-accessibility/comment-page-1/#comment-201</link> <dc:creator>Amy Stephen &#187; Blog Archive &#187; links for 2006-10-03</dc:creator> <pubDate>Tue, 03 Oct 2006 23:25:11 +0000</pubDate> <guid
isPermaLink="false">http://westciv.com/webdirections08/blog/derek-featherstone-designing-for-accessibility/#comment-201</guid> <description>[...] webdirections » Blog Archive » Derek Featherstone - Designing for Accessibility (tags: Design_Accessibility) [...]</description> <content:encoded><![CDATA[<p>[…] webdirections » Blog Archive » Derek Featherstone — Designing for Accessibility (tags: Design_Accessibility) […]</p> ]]></content:encoded> </item> <item><title>By: AndrewA</title><link>http://www.webdirections.org/notes/derek-featherstone-designing-for-accessibility/comment-page-1/#comment-203</link> <dc:creator>AndrewA</dc:creator> <pubDate>Sun, 01 Oct 2006 11:25:58 +0000</pubDate> <guid
isPermaLink="false">http://westciv.com/webdirections08/blog/derek-featherstone-designing-for-accessibility/#comment-203</guid> <description>1. While Alt attributes render as proper text for screen-magnifier users, they often don&#039;t fit on the screen depending on the level of magnification. Best approach: text as text, not images, especially for menus.
2. Source order - might not matter for a screen reader user (unless they try to discuss the page with a sighted friend). However, it matters a lot for the sighted person who has a mobility impairment that prevents them from using a mouse. These poeple expect to tab through the page in an order that approximates the visual display - ie top-left to bottom-right. So keep your code in that order.</description> <content:encoded><![CDATA[<p>1. While Alt attributes render as proper text for screen-magnifier users, they often don’t fit on the screen depending on the level of magnification. Best approach: text as text, not images, especially for menus.<br
/> 2. Source order — might not matter for a screen reader user (unless they try to discuss the page with a sighted friend). However, it matters a lot for the sighted person who has a mobility impairment that prevents them from using a mouse. These poeple expect to tab through the page in an order that approximates the visual display — ie top-left to bottom-right. So keep your code in that order.</p> ]]></content:encoded> </item> <item><title>By: Miles&#8217; Blog &#187; Web Directions - final thoughts - Thoughts and errata from Miles Burke.</title><link>http://www.webdirections.org/notes/derek-featherstone-designing-for-accessibility/comment-page-1/#comment-202</link> <dc:creator>Miles&#8217; Blog &#187; Web Directions - final thoughts - Thoughts and errata from Miles Burke.</dc:creator> <pubDate>Sat, 30 Sep 2006 08:04:36 +0000</pubDate> <guid
isPermaLink="false">http://westciv.com/webdirections08/blog/derek-featherstone-designing-for-accessibility/#comment-202</guid> <description>[...] I then introduced Derek Featherstone, who followed Thursday’s talk with Designing for accessibility: More simple techniques that make a difference. [...]</description> <content:encoded><![CDATA[<p>[…] I then introduced Derek Featherstone, who followed Thursday’s talk with Designing for accessibility: More simple techniques that make a difference. […]</p> ]]></content:encoded> </item> </channel> </rss>
<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 4/14 queries in 0.010 seconds using memcached

Served from: webdirections.org @ 2010-03-11 20:07:34 -->