<?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: Flow project: Equality and Human Rights Commission - Accessible and inclusive</title>
	<atom:link href="http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/</link>
	<description>News and ideas on user experience.</description>
	<lastBuildDate>Wed, 23 Jun 2010 16:31:05 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Simon Johnson</title>
		<link>http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/comment-page-1/#comment-139</link>
		<dc:creator>Simon Johnson</dc:creator>
		<pubDate>Tue, 19 Feb 2008 21:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/#comment-139</guid>
		<description>When user testing sites that offer the text resizing in-page, users all ignored that function. I guess that those who need to know, already use their browser controls, but I can&#039;t see any harm by adding these additional controls, especially if the sites&#039; purpose to draw attention to these issues.</description>
		<content:encoded><![CDATA[<p>When user testing sites that offer the text resizing in-page, users all ignored that function. I guess that those who need to know, already use their browser controls, but I can't see any harm by adding these additional controls, especially if the sites' purpose to draw attention to these issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philbuk</title>
		<link>http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/comment-page-1/#comment-136</link>
		<dc:creator>philbuk</dc:creator>
		<pubDate>Thu, 14 Feb 2008 12:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/#comment-136</guid>
		<description>We&#039;re certainly well aware that many folk who would benefit from larger text on web pages don&#039;t know that their browsers can offer this, or don&#039;t know where the controls are.

The folk who REALLY need to know, usually do. But people with milder vision problems, like long- or short-sightedness tend not to know. Try asking any of your friends or relatives who wear glasses and see what they tell you.

The other reason for putting the font size controls at the top is to make a point. The Commission&#039;s site needs to be exemplary in its accessibility because of the subject matter and audience. So prominent placement of accessibility features makes perfect sense.

The text resize control says &quot;This site is coded to be highly accessible&quot; - in a more meaningful and practical way than just stating it in the abstract.</description>
		<content:encoded><![CDATA[<p>We're certainly well aware that many folk who would benefit from larger text on web pages don't know that their browsers can offer this, or don't know where the controls are.</p>
<p>The folk who REALLY need to know, usually do. But people with milder vision problems, like long- or short-sightedness tend not to know. Try asking any of your friends or relatives who wear glasses and see what they tell you.</p>
<p>The other reason for putting the font size controls at the top is to make a point. The Commission's site needs to be exemplary in its accessibility because of the subject matter and audience. So prominent placement of accessibility features makes perfect sense.</p>
<p>The text resize control says "This site is coded to be highly accessible" - in a more meaningful and practical way than just stating it in the abstract.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/comment-page-1/#comment-135</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 11 Feb 2008 10:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2008/02/07/flow-project-equality-and-human-rights-commission-accessible-and-inclusive/#comment-135</guid>
		<description>Hello,

Another interesting article.

What is your rational in offering text size changes to the user via the interface?

Do you think that text size options is of particular importance to the users of this site?

Browsers already offer this functionality. Did you find that users didn&#039;t know how to find this option via the browser?

Or maybe you required these options to be more obvious for the user regardless of their understanding of the browser?

Do you feel, and did user analysis find, that these options were beneficial to the UX?</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Another interesting article.</p>
<p>What is your rational in offering text size changes to the user via the interface?</p>
<p>Do you think that text size options is of particular importance to the users of this site?</p>
<p>Browsers already offer this functionality. Did you find that users didn't know how to find this option via the browser?</p>
<p>Or maybe you required these options to be more obvious for the user regardless of their understanding of the browser?</p>
<p>Do you feel, and did user analysis find, that these options were beneficial to the UX?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
