<?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: Simple steps towards building an accessible site (part 2)</title>
	<atom:link href="http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/</link>
	<description>The Web Magazine for Young Designers and Developers</description>
	<lastBuildDate>Mon, 19 Jul 2010 03:45:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Russell Bishop</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-186</link>
		<dc:creator>Russell Bishop</dc:creator>
		<pubDate>Fri, 26 Feb 2010 03:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-186</guid>
		<description>Some excellent points raised here, which is great, as accessiblity is crucial in this industry.

I find that improving your website&#039;s accessibility is really just abiding to a set of rules. Grea thing is this eveentually because part of your natural worklflow and - hey presto! We&#039;ve accessible websites with ease!

Cheers for the article Ms. Swan!</description>
		<content:encoded><![CDATA[<p>Some excellent points raised here, which is great, as accessiblity is crucial in this industry.</p>
<p>I find that improving your website&#8217;s accessibility is really just abiding to a set of rules. Grea thing is this eveentually because part of your natural worklflow and &#8211; hey presto! We&#8217;ve accessible websites with ease!</p>
<p>Cheers for the article Ms. Swan!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ihenix</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-177</link>
		<dc:creator>ihenix</dc:creator>
		<pubDate>Thu, 11 Feb 2010 07:00:05 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-177</guid>
		<description>Hi Stelt - you are right in that kids also fall into (or overlap into) this category. I say overlap as I always think kinds have an easier time learning and difficulties are soon overcome. 

Typo&#039;s fixed! Thank you.</description>
		<content:encoded><![CDATA[<p>Hi Stelt &#8211; you are right in that kids also fall into (or overlap into) this category. I say overlap as I always think kinds have an easier time learning and difficulties are soon overcome. </p>
<p>Typo&#8217;s fixed! Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stelt</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-176</link>
		<dc:creator>stelt</dc:creator>
		<pubDate>Tue, 09 Feb 2010 13:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-176</guid>
		<description>What about young kids? Many use the web well before their school years.
They have some of the limitations mentioned, even though most quickly grow (though often for a very, very long time, but usually temporarily) out of them.

typos:
&quot;In may countries&quot;
; instead of &#039;</description>
		<content:encoded><![CDATA[<p>What about young kids? Many use the web well before their school years.<br />
They have some of the limitations mentioned, even though most quickly grow (though often for a very, very long time, but usually temporarily) out of them.</p>
<p>typos:<br />
&#8220;In may countries&#8221;<br />
; instead of &#8216;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Faulds</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-164</link>
		<dc:creator>John Faulds</dc:creator>
		<pubDate>Wed, 03 Feb 2010 12:12:30 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-164</guid>
		<description>Just to point out that it&#039;s not just IE6 that won&#039;t resize text sized in pixels if you use the View / Text size option; IE7 &amp; 8 do the same thing - &lt;a href=&quot;http://www.456bereastreet.com/archive/200902/ie_8_still_does_not_resize_text_sized_in_pixels/&quot; rel=&quot;nofollow&quot;&gt;http://www.456bereastreet.com/archive/200902/ie_8_still_does_not_resize_text_sized_in_pixels/&lt;/a&gt;.

Granted that 7 &amp; 8 also include page zoom, but you can&#039;t assume that everyone will use page zoom over the other text sizing option, particularly if the user is already familiar with how it worked in IE6.</description>
		<content:encoded><![CDATA[<p>Just to point out that it&#8217;s not just IE6 that won&#8217;t resize text sized in pixels if you use the View / Text size option; IE7 &amp; 8 do the same thing &#8211; <a href="http://www.456bereastreet.com/archive/200902/ie_8_still_does_not_resize_text_sized_in_pixels/" rel="nofollow">http://www.456bereastreet.com/archive/200902/ie_8_still_does_not_resize_text_sized_in_pixels/</a>.</p>
<p>Granted that 7 &amp; 8 also include page zoom, but you can&#8217;t assume that everyone will use page zoom over the other text sizing option, particularly if the user is already familiar with how it worked in IE6.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henny</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-163</link>
		<dc:creator>Henny</dc:creator>
		<pubDate>Wed, 03 Feb 2010 10:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-163</guid>
		<description>Thanks for the comments everyone, some really good points raised about the px issue on fonts for IE. 

Ian mentioning that in a two year development cycle for a website is very valid and raises an important point which is that when making sites accessible you want to consider how best to implement an accessible site depending on your business. So, for example, if you&#039;re a large UK organisation with users based just in the UK then leaving behind flexible fonts makes sense. If your site has more of a global outreach you may want to think again (Korea is locked into IE, China uses it heavily for example).

WCAG are guidelines and not as prescriptive as we all think and should be thought about within the context of the site you work on.

Jamie - I am with you on autoplay completely. Both a usability and accessibility fail :(</description>
		<content:encoded><![CDATA[<p>Thanks for the comments everyone, some really good points raised about the px issue on fonts for IE. </p>
<p>Ian mentioning that in a two year development cycle for a website is very valid and raises an important point which is that when making sites accessible you want to consider how best to implement an accessible site depending on your business. So, for example, if you&#8217;re a large UK organisation with users based just in the UK then leaving behind flexible fonts makes sense. If your site has more of a global outreach you may want to think again (Korea is locked into IE, China uses it heavily for example).</p>
<p>WCAG are guidelines and not as prescriptive as we all think and should be thought about within the context of the site you work on.</p>
<p>Jamie &#8211; I am with you on autoplay completely. Both a usability and accessibility fail :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Lance Shabazz Show # 119 part 2 &#124; Cult Following</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-162</link>
		<dc:creator>The Lance Shabazz Show # 119 part 2 &#124; Cult Following</dc:creator>
		<pubDate>Tue, 02 Feb 2010 15:32:33 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-162</guid>
		<description>[...] Simple steps towards building an accessible site (part 2) [...]</description>
		<content:encoded><![CDATA[<p>[...] Simple steps towards building an accessible site (part 2) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Horror/Cult/Exploitation DVD Update Part 6 (7/5/09) &#124; Cult Following</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-158</link>
		<dc:creator>Horror/Cult/Exploitation DVD Update Part 6 (7/5/09) &#124; Cult Following</dc:creator>
		<pubDate>Tue, 02 Feb 2010 04:35:12 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-158</guid>
		<description>[...] Simple steps towards building an accessible site (part 2) [...]</description>
		<content:encoded><![CDATA[<p>[...] Simple steps towards building an accessible site (part 2) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie Knight</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-154</link>
		<dc:creator>Jamie Knight</dc:creator>
		<pubDate>Mon, 01 Feb 2010 15:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-154</guid>
		<description>Hiya,

Great article, as discussed above i think EM and PX sizing is less of an issue than it once was. I think the WCAG has it right, its a good thing to have, though not anywhere near as important as it use to be. In recent projects i have returned to using PX sizing, i can&#039;t say i ever completely got my head around em sizing and i do find it faster (and easier to code up design accurately!). A good example of this is recently with a large site, i was provided the CSS and HTML for the header and footer and was not allowed to change it on pain of death!

 Along the lines of the same topic, much can also be said about the prevalence of full page zooming. Although a flexible layout which does not break when using text resizing is important, i feel that as more and more browsers default to full page zooming this will become less important.

Just to add what Henny  has said about video, one of my frustrations with video relates to autoplay. If someone is reliant on audio output or is greatly disturbed or distracted by it, then auto playing video can be a very very painful experience!

Overall a great article and series, nice one to henny and thanks to anna for publishing it!

Cheers, 

Jamie &amp; Lion</description>
		<content:encoded><![CDATA[<p>Hiya,</p>
<p>Great article, as discussed above i think EM and PX sizing is less of an issue than it once was. I think the WCAG has it right, its a good thing to have, though not anywhere near as important as it use to be. In recent projects i have returned to using PX sizing, i can&#8217;t say i ever completely got my head around em sizing and i do find it faster (and easier to code up design accurately!). A good example of this is recently with a large site, i was provided the CSS and HTML for the header and footer and was not allowed to change it on pain of death!</p>
<p> Along the lines of the same topic, much can also be said about the prevalence of full page zooming. Although a flexible layout which does not break when using text resizing is important, i feel that as more and more browsers default to full page zooming this will become less important.</p>
<p>Just to add what Henny  has said about video, one of my frustrations with video relates to autoplay. If someone is reliant on audio output or is greatly disturbed or distracted by it, then auto playing video can be a very very painful experience!</p>
<p>Overall a great article and series, nice one to henny and thanks to anna for publishing it!</p>
<p>Cheers, </p>
<p>Jamie &amp; Lion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simple plan vacation &#124; Luggage Porn</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-152</link>
		<dc:creator>Simple plan vacation &#124; Luggage Porn</dc:creator>
		<pubDate>Mon, 01 Feb 2010 15:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-152</guid>
		<description>[...] Simple steps towards building an accessible site (part 2) [...]</description>
		<content:encoded><![CDATA[<p>[...] Simple steps towards building an accessible site (part 2) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Lloyd</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-149</link>
		<dc:creator>Ian Lloyd</dc:creator>
		<pubDate>Mon, 01 Feb 2010 11:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-149</guid>
		<description>Hi Henny,

Couple of points I wanted to add. Like Doug S, I&#039;ve become less concerned about the px issue on fonts for IE. Defining standards for a project at work that will be up to two years in the making, I&#039;ve dropped that requirement on the basis that IE6 in 2 years time will account for so many fewer users and you have to draw the line somewhere ... that said, it comes with a warning. I&#039;m reasonably comfortable specifying px sizes for fonts, but start to get nervous if those are anything under 20px.

The other thing was regarding the alt attribute. The images shows the street with the alt attribute, but that&#039;s IE doing what no other browser does - displaying the *alternative* when the original is still there. It *might* suggest to less experienced readers that alt attribute may be used for hover text, which of course it isn&#039;t so, perhaps an example showing a missing image with the alternative text might be slightly safer? 

Anyway, minor niggles - always good to have an article that encapsulates the main points well (and I&#039;ll also add that I really like the design of scrunchup -lots of nice CSS text treatments)</description>
		<content:encoded><![CDATA[<p>Hi Henny,</p>
<p>Couple of points I wanted to add. Like Doug S, I&#8217;ve become less concerned about the px issue on fonts for IE. Defining standards for a project at work that will be up to two years in the making, I&#8217;ve dropped that requirement on the basis that IE6 in 2 years time will account for so many fewer users and you have to draw the line somewhere &#8230; that said, it comes with a warning. I&#8217;m reasonably comfortable specifying px sizes for fonts, but start to get nervous if those are anything under 20px.</p>
<p>The other thing was regarding the alt attribute. The images shows the street with the alt attribute, but that&#8217;s IE doing what no other browser does &#8211; displaying the *alternative* when the original is still there. It *might* suggest to less experienced readers that alt attribute may be used for hover text, which of course it isn&#8217;t so, perhaps an example showing a missing image with the alternative text might be slightly safer? </p>
<p>Anyway, minor niggles &#8211; always good to have an article that encapsulates the main points well (and I&#8217;ll also add that I really like the design of scrunchup -lots of nice CSS text treatments)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henny</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-145</link>
		<dc:creator>Henny</dc:creator>
		<pubDate>Mon, 01 Feb 2010 08:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-145</guid>
		<description>Hi Doug, you have a point in that most modern browsers today handles scaling of text (as well as images and the rest of the page). In fact under the Web Content Accessibility Guidelines 2.0 using relative font sizing is no longer a Success Criteria as it was in WCAG 1.0 and is instead a recommended technique (if memory hasn&#039;t let me down).

That said however there are still a huge amount of IE6 users out there. Many don&#039;t have the opportunity to upgrade or switch their browsers as they ar locked into using IE6 in work situations and so on. I tend to still use relative font sizes so as to ensure these users don&#039;t get left behind but agree that the landscape will have to eventually change. Bring it on I say!</description>
		<content:encoded><![CDATA[<p>Hi Doug, you have a point in that most modern browsers today handles scaling of text (as well as images and the rest of the page). In fact under the Web Content Accessibility Guidelines 2.0 using relative font sizing is no longer a Success Criteria as it was in WCAG 1.0 and is instead a recommended technique (if memory hasn&#8217;t let me down).</p>
<p>That said however there are still a huge amount of IE6 users out there. Many don&#8217;t have the opportunity to upgrade or switch their browsers as they ar locked into using IE6 in work situations and so on. I tend to still use relative font sizes so as to ensure these users don&#8217;t get left behind but agree that the landscape will have to eventually change. Bring it on I say!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug S.</title>
		<link>http://scrunchup.com/issue-5/simple-steps-towards-building-an-accessible-site-part-2/comment-page-1/#comment-140</link>
		<dc:creator>Doug S.</dc:creator>
		<pubDate>Mon, 01 Feb 2010 01:10:15 +0000</pubDate>
		<guid isPermaLink="false">http://scrunchup.com/?p=680#comment-140</guid>
		<description>This is great and I agree with most of this except the bit about using % or EMs to define text size.

My reason for this is simple: The ONLY people who will even know the difference are IE6 users. Anyone with a remotely recent version of Opera, Firefox or Safari or IE7 and IE8 can scale text whether it&#039;s in %, EMs, pixels or points.

Since this measure only helps a fraction of a fraction of users your time would actually be better spent providing better accessibility to other users. What colors you choose, making sure everything is semantic and with the proper alt or title tags is a better use of your time, in my opinion.</description>
		<content:encoded><![CDATA[<p>This is great and I agree with most of this except the bit about using % or EMs to define text size.</p>
<p>My reason for this is simple: The ONLY people who will even know the difference are IE6 users. Anyone with a remotely recent version of Opera, Firefox or Safari or IE7 and IE8 can scale text whether it&#8217;s in %, EMs, pixels or points.</p>
<p>Since this measure only helps a fraction of a fraction of users your time would actually be better spent providing better accessibility to other users. What colors you choose, making sure everything is semantic and with the proper alt or title tags is a better use of your time, in my opinion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
