<?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/"
	>

<channel>
	<title>WebAIM Blog</title>
	<atom:link href="http://webaim.org/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://webaim.org/blog</link>
	<description>The WebAIM Web Accessibility Blog</description>
	<pubDate>Mon, 29 Jun 2009 23:20:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Working in Web Accessibility</title>
		<link>http://webaim.org/blog/working-in-web-accessibility/</link>
		<comments>http://webaim.org/blog/working-in-web-accessibility/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 23:20:13 +0000</pubDate>
		<dc:creator>Jared Smith</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=276</guid>
		<description><![CDATA[This fall marks WebAIM&#8217;s 10th anniversary. During that time, the WebAIM team has evolved and changed a lot. The work WebAIM does is truly a team effort from a diverse group of men and women with whom it has been an honor to work and become friends.
I&#8217;m especially happy to see two employees that I [...]]]></description>
			<content:encoded><![CDATA[<p>This fall marks WebAIM&#8217;s 10th anniversary. During that time, the WebAIM team has evolved and changed a lot. The work WebAIM does is truly a team effort from a diverse group of men and women with whom it has been an honor to work and become friends.</p>
<p><img src="http://webaim.org/blog/media/stefandaaron2.jpg" alt="Stefanie Walker and Aaron Andersen" style="float:right; margin:10px;"/>I&#8217;m especially happy to see two employees that I helped hire get married this month. Congratulations Aaron and Stefanie!</p>
<p>The field of web accessibility is not a typical work field. I struggle sometimes to explain what it is I do every day. I know my mother doesn&#8217;t really understand it. In many ways, those of us in web accessibility are trying to work ourselves out of a job. If we were entirely successful at what we want to accomplish, we&#8217;d no longer have work to do. Of course, that&#8217;s not likely to happen any time soon. Yet we try.</p>
<p>When people ask me how I became interested in web accessibility, I usually tell them that I love it because I&#8217;m a geek and I like people. Web accessibility gives me a unique opportunity to play with cool toys, learn amazing new skills, stay on top of new technology, but most importantly, to truly make a difference in the lives of people with disabilities.</p>
<p>While <a href="http://webaim.org/about#mission">WebAIM&#8217;s mission</a> is to expand the potential of the web for people with disabilities, it&#8217;s interesting that most of our work is not with people with disabilities directly. While the friendships and acquaintances we&#8217;ve made with many people with disabilities is what inspires us to do what we do, most of our days are spent working with and influencing those who typically do not have disabilities. We&#8217;ve found that by empowering web developers, administrators, and others to make their web sites accessible, that we have a broader, more significant impact on the lives of people with disabilities - those who benefit the most from the accessibility of the sites we help influence.</p>
<p>When WebAIM began, few people were aware of web accessibility issues. One of our primary goals has been to increase awareness. Today, while there is still debate in some places whether accessibility is even a human right, awareness has increased. Most people that we work with are aware of the issues and are truly interested in seeing the web become a better place for people with disabilities - and not simply because some law or policy says they have to. The dilemma of the next decade will be increasing commitment to web accessibility and dispelling myths and misunderstandings about accessibility and people with disabilities. We also have the ongoing challenge of decreasing the gap between cutting edge and accessible.</p>
<p>And we&#8217;re not alone in doing this. Some of the smartest, most passionate people on the planet work in web accessibility. I dare not name names, but I am constantly amazed at those in this field who continue to advance technology and accessibility.</p>
<p>So, while the field of web accessibility is a bit anomalous and always adventurous, there is tremendous need for intelligent, dedicated people to help further our efforts. As technology continues to advance, we need to redouble our efforts in ensuring that people with disabilities are given the opportunity to enjoy a truly accessible web experience. Why don&#8217;t you come join us?</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/working-in-web-accessibility/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Screen Reader Testing is Back in Style</title>
		<link>http://webaim.org/blog/screen-reader-testing-is-back-in-style/</link>
		<comments>http://webaim.org/blog/screen-reader-testing-is-back-in-style/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 22:36:43 +0000</pubDate>
		<dc:creator>Jon Whiting</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=273</guid>
		<description><![CDATA[In the earlier years of web accessibility (pre-1999 to 2004), screen readers were buggy and temperamental. They would sometimes respond erratically to even simple content. Several of the out-dated recommendations of WCAG 1.0 were put in place to address these screen reader-specific issues (see almost any checkpoint that starts with &#8220;Until user agents…&#8221;), but problems [...]]]></description>
			<content:encoded><![CDATA[<p>In the earlier years of web accessibility (pre-1999 to 2004), screen readers were buggy and temperamental. They would sometimes respond erratically to even simple content. Several of the out-dated recommendations of WCAG 1.0 were put in place to address these screen reader-specific issues (see almost any checkpoint that starts with &#8220;Until user agents…&#8221;), but problems remained and screen reader testing was often a necessity, even for relatively basic pages.</p>
<p>Since then, screen readers have improved. They are far from perfect, but they have fewer bugs and tend to reliably read correctly-structured content. If you build a simple web page following solid accessibility guidelines, you can be relatively confident that your page would be accessible to a screen reader without actually testing it with a screen reader. I think this was one of the main reasons that, between around 2004 and 2007,  I relied less on screen reader testing as part of my accessibility evaluations. It was still important in some cases, but many pages could be evaluated using a good evaluation tool like <a href="http://wave.webaim.org/">WAVE</a> (provided by WebAIM) and by performing a few other manual checks, such as testing keyboard accessibility.</p>
<p>The web is much more dynamic and interactive than it was just a few years ago. Some of these changes have promising implications for accessibility, but they also introduce new accessibility challenges. Highly dynamic content, which is becoming more common, needs to be tested in a screen reader. This means screen reader testing as part of a larger accessibility evaluation is becoming more common as well. Today, it is a key part of almost all my accessibility evaluation work. Not only is my screen reader testing more frequent, it is more focused. In addition to listening to a page being read from start to finish, I usually concentrate my testing on certain areas, such as forms and navigation.</p>
<p>I have heard, and likely said, that testing with a screen reader very difficult. That it takes weeks or months to learn even the basics. I don’t agree with this statement anymore. Basic screen reader testing really only requires familiarity with a few simple keyboard commands and an understanding of what to listen for. Resources are available (e.g., our articles on <a href="http://webaim.org/articles/jaws/">testing with JAWS</a> and <a href="http://webaim.org/articles/nvda/">testing with NVDA</a>) to help users learn the basic shortcuts. In my opinion, the knowledge required to implement accessibility is much more difficult to acquire than knowledge of how to actually use the screen reader. If anyone feels like screen reader testing is an unnecessary or overly difficult part of accessibility testing, I hope you give it another chance.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/screen-reader-testing-is-back-in-style/feed/</wfw:commentRss>
		</item>
		<item>
		<title>WAVE now available in Spanish</title>
		<link>http://webaim.org/blog/wave-now-available-in-spanish/</link>
		<comments>http://webaim.org/blog/wave-now-available-in-spanish/#comments</comments>
		<pubDate>Thu, 28 May 2009 20:02:26 +0000</pubDate>
		<dc:creator>Jon Whiting</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=259</guid>
		<description><![CDATA[We are happy to announce that an updated version of WAVE web accessibility evaluation tool (wave.webaim.org) launched yesterday. This version includes several updates and bug fixes, and a couple of new rules. Most importantly, it is also available in Spanish.
WebAIM has been interested in translation of WAVE for years. We are very happy that this [...]]]></description>
			<content:encoded><![CDATA[<p>We are happy to announce that an updated version of WAVE web accessibility evaluation tool (<a href="http://wave.webaim.org">wave.webaim.org</a>) launched yesterday. This version includes several updates and bug fixes, and a couple of new rules. Most importantly, it is also <a href="http://wave.webaim.org/?lang=es">available in Spanish</a>.</p>
<p>WebAIM has been interested in translation of WAVE for years. We are very happy that this has finally become a reality and hope that this translation is the first of many. Thank you to those who have offered translation into other languages, including Portuguese, German, Japanese, Thai, Turkish, and Russian. We are currently seeking volunteers to help with these and other languages. We are also pursuing funding to support these internationalization efforts. If you would like to help, please <a href="http://wave.webaim.org/feedback">contact us</a>.</p>
<p>For more information about the new launch and the translation, visit the <a href="http://wave.webaim.org/blog">WAVE blog</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/wave-now-available-in-spanish/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Twitter Accessibility Roundup</title>
		<link>http://webaim.org/blog/twitter-accessibility-roundup/</link>
		<comments>http://webaim.org/blog/twitter-accessibility-roundup/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 21:14:50 +0000</pubDate>
		<dc:creator>Jared Smith</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=230</guid>
		<description><![CDATA[I&#8217;m a bit of a newcomer to Twitter. In the few months I&#8217;ve been online (follow me at @jared_w_smith), Twitter has become an indispensable tool for networking, communicating, and information gathering and sharing. There is a strong accessibility community on Twitter. In the spirit of The Accessibility Blog Roundup, below are 30 of the tweeple [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m a bit of a newcomer to <a href="http://twitter.com/">Twitter</a>. In the few months I&#8217;ve been online (follow me at <a href="http://twitter.com/jared_w_smith">@jared_w_smith</a>), Twitter has become an indispensable tool for networking, communicating, and information gathering and sharing. There is a strong accessibility community on Twitter. In the spirit of <a href="http://webaim.org/blog/accessibility-blog-roundup/">The Accessibility Blog Roundup</a>, below are 30 of the <strike>tweeple</strike> <strike>twits</strike> <strike>twitterers</strike> <strike>tweeters</strike> Twitter users I follow and know of that post frequent and insightful messages on web accessibility (in no particular order).</p>
<ul>
<li><a href="http://twitter.com/peterkz_swe">peterkz_swe</a></li>
<li><a href="http://twitter.com/v">v</a></li>
<li><a href="http://twitter.com/csunwebmaster">csunwebmaster</a></li>
<li><a href="http://twitter.com/shawn_slh">shawn_slh</a></li>
<li><a href="http://twitter.com/hanshillen">hanshillen</a></li>
<li><a href="http://twitter.com/suzrobitaille">suzrobitaille</a></li>
<li><a href="http://twitter.com/cynthiawaddell">cynthiawaddell</a></li>
<li><a href="http://twitter.com/steveofmaine">steveofmaine</a></li>
<li><a href="http://twitter.com/kliehm">kliehm</a></li>
<li><a href="http://twitter.com/wendyabc">wendyabc</a></li>
<li><a href="http://twitter.com/MarcoZehe">MarcoZehe</a></li>
<li><a href="http://twitter.com/ppatel">ppatel</a></li>
<li><a href="http://twitter.com/jfc3">jfc3</a></li>
<li><a href="http://twitter.com/kelsmith">kelsmith</a></li>
<li><a href="http://twitter.com/stcaccess">stcaccess</a></li>
<li><a href="http://twitter.com/dotjay">dotjay</a></li>
<li><a href="http://twitter.com/sarahebourne">sarahebourne</a></li>
<li><a href="http://twitter.com/dennisl">dennisl</a> / <a href="http://twitter.com/webaxe">webaxe</a> / <a href="http://twitter.com/AccessibleTwitr">AccessibleTwitr</a></li>
<li><a href="http://twitter.com/awkawk">awkawk</a></li>
<li><a href="http://twitter.com/joedolson">joedolson</a></li>
<li><a href="http://twitter.com/j9t">j9t</a></li>
<li><a href="http://twitter.com/AccessForAll">AccessForAll</a></li>
<li><a href="http://twitter.com/lloydi">lloydi</a> / <a href="http://twitter.com/accessify">accessify</a></li>
<li><a href="http://twitter.com/mpaciello">mpaciello</a></li>
<li><a href="http://twitter.com/brucel">brucel</a></li>
<li><a href="http://twitter.com/patrick_h_lauke">patrick_h_lauke</a></li>
<li><a href="http://twitter.com/codepo8">codepo8</a></li>
<li><a href="http://twitter.com/gezlemon">gezlemon</a></li>
<li><a href="http://twitter.com/feather">feather</a></li>
<li><a href="http://twitter.com/stevefaulkner">stevefaulkner</a></li>
<li><a href="http://twitter.com/glendawh">GlendaWH</a></li>
</ul>
<p>Limiting this list to just 30 was very difficult. There are many wonderful people on Twitter, but if you&#8217;re looking to expand your Twitter network to include the best of accessibility, following the folks listed above is a great place to start.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/twitter-accessibility-roundup/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Accessibility Blog Roundup II</title>
		<link>http://webaim.org/blog/accessibility-blog-roundup/</link>
		<comments>http://webaim.org/blog/accessibility-blog-roundup/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 21:12:43 +0000</pubDate>
		<dc:creator>Jared Smith</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=218</guid>
		<description><![CDATA[Two years ago I published The Great Accessibility Blog Roundup. At the time, I was relatively new to following blogs and thought it would be helpful to post the most useful and informative blogs I had found. Now, it&#8217;s time to update the list. Below are many of the accessibility blogs I currently follow. While [...]]]></description>
			<content:encoded><![CDATA[<p>Two years ago I published <a href="http://webaim.org/blog/blog-roundup/">The Great Accessibility Blog Roundup</a>. At the time, I was relatively new to following blogs and thought it would be helpful to post the most useful and informative blogs I had found. Now, it&#8217;s time to update the list. Below are many of the accessibility blogs I currently follow. While you&#8217;re here, be sure to check out <a href="http://webaim.org/blog/twitter-accessibility-roundup/">The Accessibility Twitter Roundup</a>.</p>
<dl>
<dt><a href="http://www.456bereastreet.com/">456 Berea Street</a> <a href="http://www.456bereastreet.com/feed.xml"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for 456 Berea Street" /></a></dt>
<dd>Roger Johansson gives informative, useful accessibility tips in short, easy-to-understand blog postings.</dd>
<dt><a href="http://www.alistapart.com/">A List Apart</a> <a href="http://www.alistapart.com/rss.xml"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for A List Apart" /></a></dt>
<dd>Their RSS feed is still broken 2 years later (you often get duplicate and repeated entries), but ALA is a must read for any web developer.</dd>
<dt><a href="http://accessibilitytips.com/">Accessibility Tips</a> <a href="http://accessibilitytips.com/feed"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Accessibility Tips" /></a></dt>
<dd>Mike Davies has posted this excellent collection of tips, guidance, and practical suggestions for developing accessible websites.</dd>
<dt><a href="http://accessify.com/news">Accessify</a> <a href="http://accessify.com/rss/accessify_rss.xml"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Accessify" /></a></dt>
<dd>Ian Lloyd and the folks at Accessify post many accessibility items, particularly ones relevant to the UK crowd.</dd>
<dt><a href="http://accessites.org/">Accessites.org</a> <a href="http://accessites.org/site/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Accessites.org" /></a></dt>
<dd>The goal of Mike Cherim and his &#8220;Team Access&#8221; is to prove that accessible web sites can function well and look beautiful. The feed features highlights of accessible web sites and insightful articles on accessible web design.</dd>
<dt><a href="http://blogs.adobe.com/accessibility/">Adobe Accessibility</a> <a href="http://blogs.adobe.com/accessibility/index.xml"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Adobe Accessibility" /></a></dt>
<dd>The Adobe Accessibility team&#8217;s blog on accessibility in Adobe products.</dd>
<dt><a href="http://www.allaccessblogging.com/">All Access Blogging</a> <a href="http://feeds.feedburner.com/AllAccessBlogging"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for All Access Blogging" /></a></dt>
<dd>Skye Kilaen provides valuable tips for making your blog more accessible.</dd>
<dt><a href="http://anikto.com/wordpress/">AniktoBlog</a> <a href="feed://http://anikto.com/wordpress/?feed=rss2"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for AniktoBlog" /></a></dt>
<dd>Kel Smith&#8217;s User-Centered Design and Web Accessibility Blog.</dd>
<dt><a href="http://boxofchocolates.ca/">box of chocolates</a> <a href="http://www.boxofchocolates.ca/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for box of chocolates" /></a></dt>
<dd>&#8220;You never know what you&#8217;re going to get&#8221; is the tagline, but with Derek Featherstone you get a true Accessibility <strike>Ninja</strike> Jedi Knight.</dd>
<dt><a href="http://www.brucelawson.co.uk/">Bruce Lawson</a> <a href="http://www.brucelawson.co.uk/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Bruce Lawson's blog" /></a></dt>
<dd>Bruce Lawson&#8217;s blog offers a mix of very interesting humor (you&#8217;ve been warned), personal experiences, and in-depth accessibility and standards info.</dd>
<dt><a href="http://www.afhill.com/blog/">Digital Likeness</a> <a href="http://feeds2.feedburner.com/afhill"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Digital Likeness" /></a></dt>
<dd>Andrea Hill, an accessibility and social media Wonder Woman, writes on a variety of topics.</dd>
<dt><a href="http://www.doitmyselfblog.com/">Do It Myself Blog</a> <a href="http://www.doitmyselfblog.com/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Do It Myself Blog" /></a></dt>
<dd>Glenda Watson Hyatt provides vast, first-hand insight into accessibility, assistive technology, and living with a disability.</dd>
<dt><a href="http://www.iheni.com/">iheni :: making the web worldwide</a> <a href="http://www.iheni.com/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for iheni Blog" /></a></dt>
<dd>Henny Swan, a web evangelist from Opera, blogs about efforts to make the web worldwide.</dd>
<dt><a href="http://www.joedolson.com/articles">Joe Dolson Accessible Web Design</a> <a href="http://feeds.feedburner.com/AccessibleDesign"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Joe Dolson Accessible Web Design" /></a></dt>
<dd>Joe is a freelance accessible site designer that shares his immense knowledge though his blog and many articles.</dd>
<dt><a href="http://juicystudio.com/">Juicy Studio</a> <a href="http://juicystudio.com/syndicate/juicyatom.xml"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Juicy Studio" /></a></dt>
<dd>Gez Lemon provides some of the most influential research and writing in the accessibility field, particularly on the technical aspects of accessibility and assistive technologies. He writes infrequently, but when he does, it&#8217;s best to read carefully.</dd>
<dt><a href="http://learningtheworld.eu/">Learning the World</a> <a href="http://learningtheworld.eu/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Learning the World" /></a></dt>
<dd>Martin Kliehm&#8217;s blog about web standards and accessibility.</dd>
<dt><a href="http://www.marcozehe.de/">Marco’s accessibility blog</a> <a href="http://www.marcozehe.de/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Marco’s accessibility blog" /></a></dt>
<dd>Marco Zehe, Mozilla&#8217;s accessibility QA and assistive technology wunderkind, blogs on all aspects of accessibility, disability, and assistive technology, with a focus on open source and Mozilla products.</dd>
<dt><a href="http://www.maxdesign.com.au/">Max Design</a> <a href="http://learningtheworld.eu/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Max Design" /></a></dt>
<dd>Russ Weakley&#8217;s blog on web design and web development focusing on Cascading Style Sheets, usability, accessibility and web standards. His weekly &#8220;Links for light reading&#8221; are awesome!</dd>
<dt><a href="http://www.splintered.co.uk/">splintered</a> <a href="http://www.splintered.co.uk/feeds/news.xml"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for splintered" /></a></dt>
<dd>Patrick H. Lauke is a very vocal accessibility expert. He&#8217;s active on about every accessibility project and mailing list there is, is a prolific author and blogger, and is now Opera&#8217;s newest web evangelist.</dd>
<dt><a href="http://www.standards-schmandards.com/">Standards Schmanders</a> <a href="http://www.standards-schmandards.com/feed"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Standards Schmanders" /></a></dt>
<dd>As the blog subtitle suggests, Peter Krantz&#8217;s writings provide a pragmatic approach to web accessibility.</dd>
<dt><a href="http://www.paciellogroup.com/blog/">The Paciello Group Blog</a> <a href="http://www.paciellogroup.com/blog/?feed=rss2"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for The Paciello Group Blog" /></a></dt>
<dd>The Paciello Group is comprised of some of the smartest, most influential accessibility experts on the planet. TPG&#8217;s Steve Faulkner posts a vast wealth of information to their blog.</dd>
<dt><a href="http://www.webstandards.org/">The Web Standards Project</a> <a href="http://www.webstandards.org/feed/"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for The Web Standards Project" /></a></dt>
<dd>WaSP is a grassroots coalition fighting for standards. The <a href="http://www.webstandards.org/action/atf/">Accessibility Task Force</a> membership, of which I&#8217;m proud to be a member, include many of the brightest minds in web accessibility. The news feed represents just a small portion of the work that goes on behind the scenes at WaSP.</dd>
<dt><a href="http://www.wait-till-i.com/">Wait till I come!</a> <a href="http://www.wait-till-i.com/feed"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Wait till I come!" /></a></dt>
<dd>Chris Heilmann of Yahoo! has turned out some of the best writing and presentations on web standards and programming in recent years. He has a unique ability to push the very edges of innovation while focusing on standards and accessibility in everything he does.</dd>
<dt><a href="http://webaxe.blogspot.com/">Web Axe - Accessibility Tips</a> <a href="http://feeds.feedburner.com/webaxe"><img src="http://webaim.org/media/template/icon_rss.png" alt="RSS for Web Axe - Accessibility Tips" /></a></dt>
<dd>Web Axe is a podcast and blog featuring practical web design accessibility tips. There are currently 70 podcasts available for download and every one of them provides useful accessibility information. Dennis Lembree&#8217;s site provides loads of useful information and interviews with the who&#8217;s who of web accessibility. Dennis is also the creator of <a href="http://accessibletwitter.com/">Accessible Twitter</a>.</dd>
</dl>
<h2>What have I missed?</h2>
<p>Several blogs that I follow were not listed here because posts are made infrequently or they don&#8217;t have a strong web accessibility focus. I&#8217;m sure there are many excellent accessibility blogs that I&#8217;m unaware of or overlooked. If you write or are familiar with an <strong><em>accessibility-focused</em></strong> blog that&#8217;s not listed above, please post the URL in a comment below.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/accessibility-blog-roundup/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Updated WAVE Toolbar</title>
		<link>http://webaim.org/blog/updated-wave-toolbar/</link>
		<comments>http://webaim.org/blog/updated-wave-toolbar/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 16:51:58 +0000</pubDate>
		<dc:creator>Jared Smith</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=216</guid>
		<description><![CDATA[A few weeks ago we announced the release of the new WAVE web site. Today, we&#8217;re happy to announce the release of a new, much improved version of the WAVE Firefox Toolbar. The WAVE Firefox Toolbar allows you to check the accessibility of any web page directly within the Firefox web browser. This version of [...]]]></description>
			<content:encoded><![CDATA[<p>A few weeks ago we announced the release of the new <a href="http://wave.webaim.org/">WAVE web site</a>. Today, we&#8217;re happy to announce the release of a new, much improved version of the WAVE Firefox Toolbar. The WAVE Firefox Toolbar allows you to check the accessibility of any web page directly within the Firefox web browser. This version of the add-on includes numerous updates, bug fixes, and new features, including:</p>
<ul>
<li>Support for several new tests and icons.</li>
<li>Increased accuracy of tests and reporting.</li>
<li>Better support for complex pages, including processing of pages with frames and iframes.</li>
<li>Customizable shortcut key functionality to quickly and easily process WAVE reports.</li>
<li>WAVE icons now feature a tooltip window that provides additional detail about the icon. Simply place your mouse over an icon to see these additional details.</li>
<li>A new context menu. Right click&#8230;, WAVE Toolbar&#8230;, then select a report option.This context menu can be turned on or off in the Options.</li>
<li>An improved mini-toolbar. You can drag the WAVE toolbar icon onto any other Firefox toolbar for quick access to WAVE Toolbar functionality while using only a small amount of screen real estate.</li>
</ul>
<p>Download the new toolbar at <a href="http://wave.webaim.org/toolbar">http://wave.webaim.org/toolbar</a></p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/updated-wave-toolbar/feed/</wfw:commentRss>
		</item>
		<item>
		<title>New WAVE Version Released</title>
		<link>http://webaim.org/blog/new-wave-version-released/</link>
		<comments>http://webaim.org/blog/new-wave-version-released/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 23:10:27 +0000</pubDate>
		<dc:creator>Jared Smith</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=211</guid>
		<description><![CDATA[WebAIM is pleased to announce that a new version of the WAVE web accessibility evaluation tool was released today. This significant update reflects many months of work on WebAIM&#8217;s part to make WAVE more stable, powerful, and useful. Since the version 4 beta was launched just over a year ago, WAVE has been used to [...]]]></description>
			<content:encoded><![CDATA[<p>WebAIM is pleased to announce that a new version of the <a href="http://wave.webaim.org/">WAVE web accessibility evaluation tool</a> was released today. This significant update reflects many months of work on WebAIM&#8217;s part to make WAVE more stable, powerful, and useful. Since the version 4 beta was launched just over a year ago, WAVE has been used to analyze nearly <strong>a million web pages</strong> for accessibility. Today&#8217;s launch signifies a significant step forward in making WAVE the most powerful and useful (and ALWAYS free) web accessibility tool available.</p>
<p>Notable new and improved features:</p>
<ul>
<li>Simplified and streamlined user interface</li>
<li>Significantly re-engineered back-end framework
<ul>
<li>Better stability and significantly faster processing of pages</li>
<li>Single sourced code for server version of WAVE and the Firefox toolbar</li>
<li>More powerful and flexible logic for WAVE evaluation rules</li>
</ul>
</li>
<li>Support for internationalization. Initial translations will be provided in coming months.</li>
<li>Several new WAVE rules
<ul>
<li>Missing fieldset - alert when a group of check boxes or radio buttons is not enclosed in a fieldset</li>
<li>ARIA - indicator for all ARIA roles, properties, and attributes</li>
<li>Unlabeled form element with title - alerts users to form elements that do not have an associated label, but do have the necessary title attribute</li>
<li>Blink</li>
<li>Many other rules have been further polished and improved for accuracy</li>
</ul>
</li>
</ul>
<p>All of these new features and many more are currently being implemented into an updated <a href="http://wave.webaim.org/toolbar">Firefox toolbar</a> which will be available in the near future.</p>
<p>We are always open to <a href="http://wave.webaim.org/feedback">feedback</a> and hope that you will take some time to review the <a href="http://wave.webaim.org/">new WAVE features</a> and let us know how we can make it even better.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/new-wave-version-released/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Screen Reader Survey Updates</title>
		<link>http://webaim.org/blog/screen-reader-survey-updates/</link>
		<comments>http://webaim.org/blog/screen-reader-survey-updates/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 22:42:41 +0000</pubDate>
		<dc:creator>Stefanie Walker</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=206</guid>
		<description><![CDATA[We are continuing to go over the screen reader survey results and have begun analyzing responses to the open-ended questions. The first two questions that we have worked on asked users to list their favorite web sites and sites which they avoid.
Google was hands down the winner with almost 60% of respondents, 671 of 1121, [...]]]></description>
			<content:encoded><![CDATA[<p>We are continuing to go over the <a href="http://webaim.org/projects/screenreadersurvey/">screen reader survey results</a> and have begun analyzing responses to the open-ended questions. The first two questions that we have worked on asked users to list their favorite web sites and sites which they avoid.</p>
<p>Google was hands down the winner with almost 60% of respondents, 671 of 1121, listing it as one of their favorite sites. Flash-based sites were listed most often as the type of site users avoid. It was also interesting to note that several sites prevalently as ones used and as ones avoided. We have updated the screen reader survey results to include information on <a href="http://webaim.org/projects/screenreadersurvey/#websites">favorite web sites and sites respondents avoid</a>. We&#8217;ve also added a section of <a href="http://webaim.org/projects/screenreadersurvey/#quotables">quotable comments from survey respondents</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/screen-reader-survey-updates/feed/</wfw:commentRss>
		</item>
		<item>
		<title>WebAIM/TPG Partnership</title>
		<link>http://webaim.org/blog/webaim-tpg-partnership/</link>
		<comments>http://webaim.org/blog/webaim-tpg-partnership/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 14:46:17 +0000</pubDate>
		<dc:creator>Jared Smith</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=199</guid>
		<description><![CDATA[WebAIM and The Paciello Group (TPG) are pleased to announce today a partnership that delivers independent web site certification for accessibility.
In today’s diverse environment, the Internet is becoming the pre-eminent location for people with disabilities to find information and to transact business.  It is vitally important for web site creators and operators to take [...]]]></description>
			<content:encoded><![CDATA[<p><strong>WebAIM and <a href="http://www.paciellogroup.com/">The Paciello Group</a> (TPG) are pleased to announce today a partnership that delivers independent web site certification for accessibility.</strong></p>
<p>In today’s diverse environment, the Internet is becoming the pre-eminent location for people with disabilities to find information and to transact business.  It is vitally important for web site creators and operators to take all appropriate steps to ensure their web properties are universally accessible.   However, many people with disabilities are finding an unacceptable level of accessibility for many popular web sites, creating a frustrating experience.</p>
<p>Now, with the partnership between TPG and WebAIM, web site owners can retain The Paciello Group to perform full accessibility testing and professional services while additionally receiving the WebAIM Accessible Site Certification. This certificate can be posted on their web site attesting to an independent guarantee. WebAIM clients can also secure 3rd party TPG certification of thier sites.</p>
<p>While both TPG and WebAIM independently provide high quality, industry leading accessibility consulting and certification services, this exclusive partnership provides great value to our clients by allowing a 3rd party entity to both verify and certify accessibility of our client&#8217;s web sites and applications.</p>
<p>While certification systems and structures have been around for sometime, the WebAIM / TPG is unique in that two independent accessibility groups have joined to add the strength of their expertise to provide an external certification of accessibility after expert consultation. TPG and WebAIM are forming this partnership to ensure the highest level of accessibility services and to also insure full independence between the testing and certification agencies.<br />
<strong>Mike Paciello, founder and president of The Paciello Group addresses the value of independent certification:</strong></p>
<blockquote><p>&quot;There are a number of companies delivering quality professional services to help vendors make their sites more accessible, but we wanted to offer our clients the assurance that the work we are performing is of the highest quality and attested to by a completely independent authority.  WebAIM’s position in the accessibility market as a recognized leader in practice and passion for accessibility makes them the logical choice to deliver this independent certification.  We are thrilled to partner with them.&quot;</p>
</blockquote>
<p><a href="http://www.paciellogroup.com/">The Paciello Group</a> is passionately dedicated to helping government agencies, technology vendors, e-commerce corporations, and educational institutions make their technology equally accessible to all people, including those with disabilities. The company, based in Nashua, NH, offers professional consulting, technology solutions, and monthly monitoring services to ensure that clients reach all audiences effectively and efficiently while meeting governmental and international standards.</p>
<p><a href="http://webaim.org/">WebAIM</a>, Web Accessibility in Mind, provides comprehensive web accessibility solutions. Ten years of experience makes WebAIM one of the leading providers of web accessibility expertise internationally. WebAIM is a non-profit organization within the Center for Persons with Disabilities at Utah State University.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/webaim-tpg-partnership/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Hiding content for screen readers</title>
		<link>http://webaim.org/blog/hiding-content-for-screen-readers/</link>
		<comments>http://webaim.org/blog/hiding-content-for-screen-readers/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 17:23:20 +0000</pubDate>
		<dc:creator>Jared Smith</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://webaim.org/blog/?p=191</guid>
		<description><![CDATA[For years WebAIM has recommended a specific technique for hiding content visually while allowing it to be read by screen readers. This involved using CSS to position the content above the top of the page. It has now been brought to our attention that if the off-screen content contains a focusable element (a link or [...]]]></description>
			<content:encoded><![CDATA[<p>For years WebAIM has recommended a specific technique for hiding content visually while allowing it to be read by screen readers. This involved using CSS to position the content above the top of the page. It has now been <a href="http://www.accessibilitytips.com/2008/03/04/positioning-content-offscreen/">brought to our attention</a> that if the off-screen content contains a focusable element (a link or form element), that the web browser will attempt to scroll to this element when it receives focus - thus scrolling to the top of the page. This could be confusing for sighted keyboard users.</p>
<p>To resolve this potential issue, we now recommend the following styles for hiding content off-screen:</p>
<p><span class="markup">position:absolute;<br />
left:-10000px;<br />
top:auto;<br />
width:1px;<br />
height:1px;<br />
overflow:hidden;</span></p>
<p>This will move the element straight to the left a considerable distance. Because the hidden element is moved directly to the left, if a link or form element within it receives focus, the browser will not scroll to the top of the page.</p>
<p>The width, height, and overflow styles are likely a bit overkill, but account for rare instances where positioning is disabled, but other styles enabled. Or perhaps for viewports that have VERY large external margins. These styles can probably be omitted in most instances.</p>
<p>It is important to note that it is not generally practice to place links or form elements, which provide functionality, in a hidden element just for screen reader users. Functionality should typically be made available to all users. Additionally, discretion should be used in providing content, cues, or information only for screen reader users. Remember that sighted keyboard users may also benefit from this information. In general, content should only be hidden from sighted users and made available to screen reader users when content is apparent visually, but not apparent to screen reader users.</p>
<p>An article outlining proper and improper implementations and techniques for hiding content is available at <a href="http://webaim.org/techniques/css/invisiblecontent/">http://webaim.org/techniques/css/invisiblecontent/</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://webaim.org/blog/hiding-content-for-screen-readers/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
