<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Accessibility Blog&#8217;s New Design</title>
	<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/</link>
	<description>Raising the awareness of Web Site Accessibility and Marketing.</description>
	<pubDate>Sun, 20 Jul 2008 14:23:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Fahed Bizzari</title>
		<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-65457</link>
		<dc:creator>Fahed Bizzari</dc:creator>
		<pubDate>Sat, 30 Jun 2007 15:57:57 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-65457</guid>
		<description>&lt;blockquote cite="Joe Dolson"&gt;I may use that metaphor one of these days!&lt;/blockquote&gt;
Lol! Don't forget to cite us!</description>
		<content:encoded><![CDATA[<blockquote cite="Joe Dolson"><p>I may use that metaphor one of these days!</p></blockquote>
<p>Lol! Don&#8217;t forget to cite us!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-65438</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Sat, 30 Jun 2007 15:11:24 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-65438</guid>
		<description>&lt;blockquote&gt;
Thanks again for your advice. It seems that, in many cases, accessibility has a lot of common sense - it just needs to be taken into consideration.
&lt;/blockquote&gt;

Glad to help! You've pretty much hit it on the head, there: it's mostly common sense. It's just common sense which requires you to anticipate a lot of problems you personally may never encounter!

&lt;blockquote&gt;
Buildings allow wheel-chairs to enter using a ramp and that ramp should also be at the front of the building with the main stairs. To cater for wheel-chairs, it doesn't mean we need to get rid of the stairs, we just need to make sure that people with wheel-chairs can enter the building as easily (so to say) as people without.
&lt;/blockquote&gt;

Nice way of putting it. I may use that metaphor one of these days!</description>
		<content:encoded><![CDATA[<blockquote><p>
Thanks again for your advice. It seems that, in many cases, accessibility has a lot of common sense - it just needs to be taken into consideration.
</p></blockquote>
<p>Glad to help! You&#8217;ve pretty much hit it on the head, there: it&#8217;s mostly common sense. It&#8217;s just common sense which requires you to anticipate a lot of problems you personally may never encounter!</p>
<blockquote><p>
Buildings allow wheel-chairs to enter using a ramp and that ramp should also be at the front of the building with the main stairs. To cater for wheel-chairs, it doesn&#8217;t mean we need to get rid of the stairs, we just need to make sure that people with wheel-chairs can enter the building as easily (so to say) as people without.
</p></blockquote>
<p>Nice way of putting it. I may use that metaphor one of these days!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fahed Bizzari</title>
		<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-65432</link>
		<dc:creator>Fahed Bizzari</dc:creator>
		<pubDate>Sat, 30 Jun 2007 14:55:05 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-65432</guid>
		<description>Thanks for the link. I did manage to read that article in the last few days. 

We also came to unanimous agreement with what you've said. The base font has been set in em's with 1em = 12px. The width of the site is also measured in em's, whilst page structure is measured in percentages to give a zoom/scalable layout.

On a 1024 resolution screen, the font can be resized to up to 15.5px without the bottom scroll bar kicking in and will grow/zoom as much as needed for larger resolution sizes.

Whilst we were very concerned about the issue of mixing accessibility with design, the concept we took hold of was...

Buildings allow wheel-chairs to enter using a ramp and that ramp should also be at the front of the building with the main stairs. To cater for wheel-chairs, it doesn't mean we need to get rid of the stairs, we just need to make sure that people with wheel-chairs can enter the building as easily (so to say) as people without.

Thanks again for your advice. It seems that, in many cases, accessibility has a lot of common sense - it just needs to be taken into consideration.</description>
		<content:encoded><![CDATA[<p>Thanks for the link. I did manage to read that article in the last few days. </p>
<p>We also came to unanimous agreement with what you&#8217;ve said. The base font has been set in em&#8217;s with 1em = 12px. The width of the site is also measured in em&#8217;s, whilst page structure is measured in percentages to give a zoom/scalable layout.</p>
<p>On a 1024 resolution screen, the font can be resized to up to 15.5px without the bottom scroll bar kicking in and will grow/zoom as much as needed for larger resolution sizes.</p>
<p>Whilst we were very concerned about the issue of mixing accessibility with design, the concept we took hold of was&#8230;</p>
<p>Buildings allow wheel-chairs to enter using a ramp and that ramp should also be at the front of the building with the main stairs. To cater for wheel-chairs, it doesn&#8217;t mean we need to get rid of the stairs, we just need to make sure that people with wheel-chairs can enter the building as easily (so to say) as people without.</p>
<p>Thanks again for your advice. It seems that, in many cases, accessibility has a lot of common sense - it just needs to be taken into consideration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-64820</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Fri, 29 Jun 2007 15:22:15 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-64820</guid>
		<description>Large fonts are easier to read in most cases --- that's true. However, it's far more important that you make the font rescalable according to user preferences than that you make it larger. 

Most users who have a routine need for larger fonts no how to make that change in their browsers. This ability is built into the browser, and you should allow the user to maintain control over their experience. 

What you particularly need to avoid is using pixels or points to size text. Although pixels &lt;em&gt;should&lt;/em&gt; be resizeable universally, they are not. IE6 doesn't allow the user to change the size of text if it's sized in pixels. Use &lt;code&gt;em&lt;/code&gt;s or percentages, instead. 

Large fonts are not, in fact, absolutely more accessible than large fonts.  For a bit more advice, I recommend reading &lt;a href="http://accessites.org/site/2007/06/improving-accessibility-through-typography/"&gt;Improving Accessibility Through Typography&lt;/a&gt;, an article I published recently at Accessites.org.</description>
		<content:encoded><![CDATA[<p>Large fonts are easier to read in most cases &#8212; that&#8217;s true. However, it&#8217;s far more important that you make the font rescalable according to user preferences than that you make it larger. </p>
<p>Most users who have a routine need for larger fonts no how to make that change in their browsers. This ability is built into the browser, and you should allow the user to maintain control over their experience. </p>
<p>What you particularly need to avoid is using pixels or points to size text. Although pixels <em>should</em> be resizeable universally, they are not. IE6 doesn&#8217;t allow the user to change the size of text if it&#8217;s sized in pixels. Use <code>em</code>s or percentages, instead. </p>
<p>Large fonts are not, in fact, absolutely more accessible than large fonts.  For a bit more advice, I recommend reading <a href="http://accessites.org/site/2007/06/improving-accessibility-through-typography/">Improving Accessibility Through Typography</a>, an article I published recently at Accessites.org.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fahed Bizzari</title>
		<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-64684</link>
		<dc:creator>Fahed Bizzari</dc:creator>
		<pubDate>Fri, 29 Jun 2007 07:40:40 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-64684</guid>
		<description>Overseeing the development of our new site, myself and our development team have been going deeper and deeper into accessibility as part of basic social responsibility. One issue, which i believe relates to the concept of design vs accessibility, which is affecting us relates to font size.

Obviously, large fonts are more accessible than small fonts. But does that mean our design should use a font which is acceptable for good vision users (e.g. 12px) and allow scaling so that let low vision users can increase the size in their browsers. Or should we keep the site in 14px and automatically scale down for low resolution monitors that don't have enough space for 14px text. (Note 4% of our users have an 800x600 resolution).

The complication is that the immediate look of 14px is considered by most, including our entire development team, to be unprofessional. At the same time, however, there is issue of accessibility.

Do you know of any corporate sites that have adopted large fonts? What can you recommend?

Thanks</description>
		<content:encoded><![CDATA[<p>Overseeing the development of our new site, myself and our development team have been going deeper and deeper into accessibility as part of basic social responsibility. One issue, which i believe relates to the concept of design vs accessibility, which is affecting us relates to font size.</p>
<p>Obviously, large fonts are more accessible than small fonts. But does that mean our design should use a font which is acceptable for good vision users (e.g. 12px) and allow scaling so that let low vision users can increase the size in their browsers. Or should we keep the site in 14px and automatically scale down for low resolution monitors that don&#8217;t have enough space for 14px text. (Note 4% of our users have an 800&#215;600 resolution).</p>
<p>The complication is that the immediate look of 14px is considered by most, including our entire development team, to be unprofessional. At the same time, however, there is issue of accessibility.</p>
<p>Do you know of any corporate sites that have adopted large fonts? What can you recommend?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Dolson</title>
		<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-13591</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Tue, 19 Sep 2006 19:52:26 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-13591</guid>
		<description>Thanks! I'm thrilled to be doing this with Matt, and I'm certainly glad to hear that other people like the idea too ;) !

I've made a note of the sensitivity to bright colors issue - we were aiming for high contrast, but perhaps we overshot into "too high" contrast, instead...

Thanks for the comments!</description>
		<content:encoded><![CDATA[<p>Thanks! I&#8217;m thrilled to be doing this with Matt, and I&#8217;m certainly glad to hear that other people like the idea too <img src='http://www.accessibilityblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> !</p>
<p>I&#8217;ve made a note of the sensitivity to bright colors issue - we were aiming for high contrast, but perhaps we overshot into &#8220;too high&#8221; contrast, instead&#8230;</p>
<p>Thanks for the comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Krause Berg (cre8pc)</title>
		<link>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-13590</link>
		<dc:creator>Kim Krause Berg (cre8pc)</dc:creator>
		<pubDate>Tue, 19 Sep 2006 19:47:23 +0000</pubDate>
		<guid>http://www.accessibilityblog.com/2006/09/19/accessibility-blogs-new-design/#comment-13590</guid>
		<description>Joe, this is fantastic news!  My two favorite accessibility teachers working together. Perfect, and a brilliant idea.  Viewing the changes from Firefox - no problems. Viewing it with my eyesight probs (various), good. Some colors tend to be "too bright" but I have two different contact lenses in my eyes, one being a bi-focal one and one that lets me drive a car. My brain works harder to intrepret the messages my eyes send. For some reason, I've become sensitive to bright colors, I noticed. (Just a little user feedback for ya.)  Congratulations both of you!</description>
		<content:encoded><![CDATA[<p>Joe, this is fantastic news!  My two favorite accessibility teachers working together. Perfect, and a brilliant idea.  Viewing the changes from Firefox - no problems. Viewing it with my eyesight probs (various), good. Some colors tend to be &#8220;too bright&#8221; but I have two different contact lenses in my eyes, one being a bi-focal one and one that lets me drive a car. My brain works harder to intrepret the messages my eyes send. For some reason, I&#8217;ve become sensitive to bright colors, I noticed. (Just a little user feedback for ya.)  Congratulations both of you!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.605 seconds -->
