<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title>InfoDesign: Understanding by Design</title>
<link>http://www.informationdesign.org/</link>
<description>Dedicated to the growth and improvement of the information experience industries.</description>
<dc:language>en-us</dc:language>
<dc:creator>plato@xs4all.nl</dc:creator>
<dc:date>2012-11-17T11:41:45+01:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.21-en" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>


<item>
<title>Accessibility is part of UX (it isn’t a swear word)</title>
<description><![CDATA[Having access should be a hygiene factor, not a motivator.
"People often go a bit wobbly when accessibility is mentioned. Visions of text only websites, monochrome designs and static content swirl in their heads. Teeth are gritted, excuses are prepared, and battle conditions ensue. The reality is that accessibility is simply a key part of UX. A truly outstanding digital experience is a fusion of accessibility, usability, creativity and technology. The trick is to weave those things together, and to do that successfully there needs to be a cross pollination of skills and expertise. The good news is that accessibility is usability under a magnifying glass. If you’re thinking about great usability, the chances are that you’re already thinking about great accessibility too."
(L&eacute;onie Watson ~ humanising technology blog) ~ courtesy of ericscheid]]></description>

<!-- 
<link>http://www.informationdesign.org/archives/2012/11/#006639</link>
<guid isPermaLink="false">6639@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2012-11-17T11:41:45+01:00</dc:date>
</item>

<item>
<title>Accessibility First for a Better User Experience for All</title>
<description>&quot;All of these problems affect their general usability for people without disabilities, though not as severely. The more crowded or complex a screen, the harder it is to understand it and learn to use it effectively. Just as making hard decisions about priorities for a mobile user interface can pay off in a better Web version of an application, designing for better accessibility can make a product more usable for everyone.&quot; (Whitney Quesenbery ~ UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/12/#005840</link>
<guid isPermaLink="false">5840@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2010-12-20T10:44:26+01:00</dc:date>
</item>

<item>
<title>Access Ability: A practical handbook on accessible graphic design </title>
<description>&quot;All design by definition promotes accessibility. Graphic designers try to make printed messages clearer, websites more navigable, physical environments easier to negotiate. As a profession, we’re committed to providing easier access – to information, to ideas, to public spaces – through smarter, more effective communications engaging the widest possible audience. Or at least everyone we’re hoping to reach. (...) Our goal is not to prescribe a set of rules for accessible design. Practical guides that try to be categorical end up being, at best, targets for rebuttal – or simply doorstops. So our aim is not to tell professional designers what to do, but rather to remind all of us how we could be doing better.&quot; (Accessible Graphic Design)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/11/#005811</link>
<guid isPermaLink="false">5811@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2010-11-30T15:40:03+01:00</dc:date>
</item>

<item>
<title>Why You Should Adopt An &apos;Accessible Content Strategy&apos;</title>
<description>&quot;With the burgeoning number of computing devices and software solutions, it is easier than ever before to deliver single-sourced content such that it is accessible, consumable and actionable by as many users as possible.&quot; (The Content Wrangler)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2010/05/#005597</link>
<guid isPermaLink="false">5597@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2010-05-25T16:28:14+01:00</dc:date>
</item>

<item>
<title>Usable Accessibility: Making Web Sites Work Well for People with Disabilities</title>
<description>&quot;When people talk about both usability and accessibility, it is often to point out how they differ. Accessibility often gets pigeon-holed as simply making sure there are no barriers to access for screen readers or other assistive technology, without regard to usability, while usability usually targets everyone who uses a site or product, without considering people who have disabilities. In fact, the concept of usability often seems to exclude people with disabilities, as though just access is all they are entitled to. What about creating a good user experience for people with disabilities—going beyond making a Web site merely accessible to make it truly usable for them?&quot; - (Whitney Quesenbery - UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2009/02/#004915</link>
<guid isPermaLink="false">4915@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Usability</dc:subject>

<dc:date>2009-02-24T11:04:44+01:00</dc:date>
</item>

<item>
<title>This is How the Web Gets Regulated</title>
<description>&quot;If a deaf person has a legal right to watch TV or movies with captions, that person has a legal right to watch online video with captions. The voluntary approach has done practically nothing to make that possible. Laws or human-rights regulations are necessary and inevitable. You should get behind them.&quot; (Joe Clark - A List Apart)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2008/11/#004774</link>
<guid isPermaLink="false">4774@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2008-11-20T15:32:58+01:00</dc:date>
</item>

<item>
<title>WCAG Samurai</title>
<description>&quot;The WCAG Samurai was a group of developers, led by Joe Clark, that publishes corrections for, and extensions to, the Web Content Accessibility Guidelines 1.0.&quot;</description>

<!-- 
<link>http://www.informationdesign.org/archives/2007/07/#004242</link>
<guid isPermaLink="false">4242@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2007-07-06T16:11:02+01:00</dc:date>
</item>

<item>
<title>Improving Accessibility through Typography</title>
<description>&quot;Typography has many facets which go beyond font faces, sizes, or the color of text. Taking typography into consideration at every step of the way can enable you to prepare a much more readable, accessible document.&quot; (Joe Dolson - Accessites) - courtesy of usernomics</description>

<!-- 
<link>http://www.informationdesign.org/archives/2007/06/#004224</link>
<guid isPermaLink="false">4224@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2007-06-11T09:37:26+01:00</dc:date>
</item>

<item>
<title>Accessible Web 2.0 Applications with WAI-ARIA</title>
<description>&quot;Web 2.0 applications often have accessibility and usability problems because of the limitations of (X)HTML. The W3C’s standards draft for Accessible Rich Internet Applications (ARIA) addresses those limitations. It provides new ways of communicating meaning, importance, and relationships, and it fills gaps in the (X)HTML specifications and increases usability for all users by enabling navigation models familiar from desktop applications. Best of all, you can start using ARIA right away to enhance the accessibility of your websites.&quot; (Martin Kliehm - A List Apart)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2007/04/#004160</link>
<guid isPermaLink="false">4160@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2007-04-10T13:02:54+01:00</dc:date>
</item>

<item>
<title>Ensuring Accessibility for People With Color-Deficient Vision</title>
<description>&quot;This article is Part IV of my series &apos;Color Theory for Digital Displays&apos;. It describes how you can use color in applications and on Web pages to ensure that they are accessible to people who have color-deficient vision. If you do not consider the needs of people with color-deficient vision when choosing color schemes for applications and Web pages, those you create may be difficult to use or even indecipherable for about one in twelve users.&quot; (Pabini Gabriel-Petit - UXmatters)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2007/02/#004091</link>
<guid isPermaLink="false">4091@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2007-02-08T20:26:54+01:00</dc:date>
</item>

<item>
<title>Roadmap for Accessible Rich Internet Applications</title>
<description>&quot;The Roadmap for Accessible Rich Internet Applications addresses the accessibility of dynamic Web content for people with disabilities. The roadmap outlines the technologies to map controls, AJAX live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. The roadmap also outlines new navigation techniques to mark common Web structures as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources.&quot; (W3C WAI-ARIA)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2006/09/#003950</link>
<guid isPermaLink="false">3950@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2006-09-26T16:57:12+01:00</dc:date>
</item>

<item>
<title>The Web Standards Project: Education Task Force</title>
<description>&quot;The WaSP Education Task Force was created in 2005 to work directly with institutions of higher education to help raise awareness of Web standards and accessibility among instructors, administrators, and Web development teams.&quot; (WaSP) - courtesy of 456breastreet</description>

<!-- 
<link>http://www.informationdesign.org/archives/2006/05/#003743</link>
<guid isPermaLink="false">3743@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2006-05-22T09:38:13+01:00</dc:date>
</item>

<item>
<title>Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web</title>
<description>&quot;A common method of limiting access to services made available over the Web is visual verification of a bitmapped image. This presents a major problem to users who are blind, have low vision, or have a learning disability such as dyslexia. This document examines a number of potential solutions that allow systems to test for human users while preserving access by users with disabilities.&quot; (W3C) - courtesy of accessify</description>

<!-- 
<link>http://www.informationdesign.org/archives/2005/11/#003452</link>
<guid isPermaLink="false">3452@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2005-11-24T09:29:39+01:00</dc:date>
</item>

<item>
<title>Web accessibility: The basics and benefits</title>
<description>&quot;Web accessibility is about making your website accessible to all Internet users (both disabled and non-disabled), regardless of what browsing technology they’re using. In addition to complying with the law, an accessible website can reap huge benefits on to your website and your business.&quot; (Trenton Moss - uiGarden.net)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2005/11/#003448</link>
<guid isPermaLink="false">3448@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2005-11-22T10:46:35+01:00</dc:date>
</item>

<item>
<title>Accessibility Is Not Enough</title>
<description>&quot;A strict focus on accessibility as a scorecard item doesn&apos;t help users with disabilities. To help these users accomplish critical tasks, you must adopt a usability perspective.&quot; (Jakob Nielsen - Alertbox)</description>

<!-- 
<link>http://www.informationdesign.org/archives/2005/11/#003442</link>
<guid isPermaLink="false">3442@http://www.informationdesign.org/</guid>
 -->

<dc:subject>Accessibility</dc:subject>

<dc:date>2005-11-20T22:05:22+01:00</dc:date>
</item>


</channel>
</rss>