<?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"
	>
<channel>
	<title>Comments for Man with no Blog</title>
	<atom:link href="http://manwithnoblog.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://manwithnoblog.com</link>
	<description>Gary Barber rants on user experience, information architecture and the web industry.</description>
	<pubDate>Fri, 21 Nov 2008 14:07:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>Comment on 9 Skills to Supplement Design by wil</title>
		<link>http://manwithnoblog.com/2008/10/18/9-skills-to-supplement-design/#comment-8295</link>
		<dc:creator>wil</dc:creator>
		<pubDate>Tue, 21 Oct 2008 11:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=225#comment-8295</guid>
		<description>It's funny, I often think that people who design for web need to know more about the medium their designing for than they currently do. Yet Gary's list to me seemed to run against the grain of so many of the wonderful designers I know. Many of the best designers, whos work I love and respect, will never learn a coding language, they won't think about accessibility off the cuff and they don't care about information architecture ... at least not in the way I think is implied in the article.

I think a lot of this goes back to the fundamental skill set of a designer.

I once heard Mark Braddock say that when a client asks him to do something arbitrary like Add more blue he usually will ask them to describe what is wrong with the design. The problem for many people is that they don't know how to communicate with designers. Add more blue is a solution, it's the job of the designer to come up with that solution while It doesn't feel bright enough is a problem, that's what you need to communicate. I think he's pretty spot on here.

I don't think Designers need to know the Solutions for web development problems but they do need to understand how to communicate their needs, which is where having an understanding of those skills comes in handy.

I think probably I'd shorten Gary's list to the fundamentals of web development that don't rely on the Solutions but instead outline the field of play.

For example, I think Information Architecture, Javascript and Backend Coding could all come under one simple heading: Understand how a dynamic webpage is rendered

What you want out of that is a designer who knows that all the data in a CMS site is stored in a database, that they can use things like "date" and "title" as fields and make them repeat and all that sort of thing. A basic understanding of how a single "page" is actually made up of lots of little bits and how CSS works pretty much like Object Styles in InDesign, so they should always think in terms of those objects. And any images, movies, typefaces etc need to be accessible to everyone who views that page, again just like linking objects in InD.

Then there's the General User Experience, Interactive Interface Design, Accessibility and Usability. I think that fits under the simple heading: Understand how changes are made to the website in real time

With that in mind you're asking the designer to be familiar with how websites change on the fly. This includes an understanding of Triggers, so they know things happen based on Events like timers, mouse over and out, clicks, that sorta thing. Knowing that they're still doing the same Object-Style tricks as in pre-render (obeying the same linking rules too) but it's called up by special scripts now, so we can cause some changes in movement. A box that appears to scroll up is just having it's height value changed every couple of miliseconds but, apart from that, it's the same as a pre-rendered box.

Finally there's your Mobile Interface Design and the other side of General User Experience and Usability. In a way their outcomes of knowing the above two processes. If you understand how a website is displayed and how it changes then you know what you're able to do which is the empowering that i think most designers need. With that they're usually very capable of dealing with user feedback and pre-evaluating the user experience a lot more.

I guess I agree with Gary in intent but I don't think it's so much about the skills a designer picks up as opposed to spending time learning about the Process by which their work is going to be displayed. Much like they don't need to know how a particular type of paper is made but only what it looks like, feels like and how it responds to various colours.

A more focused approach perhaps :D</description>
		<content:encoded><![CDATA[<p>It&#8217;s funny, I often think that people who design for web need to know more about the medium their designing for than they currently do. Yet Gary&#8217;s list to me seemed to run against the grain of so many of the wonderful designers I know. Many of the best designers, whos work I love and respect, will never learn a coding language, they won&#8217;t think about accessibility off the cuff and they don&#8217;t care about information architecture &#8230; at least not in the way I think is implied in the article.</p>
<p>I think a lot of this goes back to the fundamental skill set of a designer.</p>
<p>I once heard Mark Braddock say that when a client asks him to do something arbitrary like Add more blue he usually will ask them to describe what is wrong with the design. The problem for many people is that they don&#8217;t know how to communicate with designers. Add more blue is a solution, it&#8217;s the job of the designer to come up with that solution while It doesn&#8217;t feel bright enough is a problem, that&#8217;s what you need to communicate. I think he&#8217;s pretty spot on here.</p>
<p>I don&#8217;t think Designers need to know the Solutions for web development problems but they do need to understand how to communicate their needs, which is where having an understanding of those skills comes in handy.</p>
<p>I think probably I&#8217;d shorten Gary&#8217;s list to the fundamentals of web development that don&#8217;t rely on the Solutions but instead outline the field of play.</p>
<p>For example, I think Information Architecture, Javascript and Backend Coding could all come under one simple heading: Understand how a dynamic webpage is rendered</p>
<p>What you want out of that is a designer who knows that all the data in a CMS site is stored in a database, that they can use things like &#8220;date&#8221; and &#8220;title&#8221; as fields and make them repeat and all that sort of thing. A basic understanding of how a single &#8220;page&#8221; is actually made up of lots of little bits and how CSS works pretty much like Object Styles in InDesign, so they should always think in terms of those objects. And any images, movies, typefaces etc need to be accessible to everyone who views that page, again just like linking objects in InD.</p>
<p>Then there&#8217;s the General User Experience, Interactive Interface Design, Accessibility and Usability. I think that fits under the simple heading: Understand how changes are made to the website in real time</p>
<p>With that in mind you&#8217;re asking the designer to be familiar with how websites change on the fly. This includes an understanding of Triggers, so they know things happen based on Events like timers, mouse over and out, clicks, that sorta thing. Knowing that they&#8217;re still doing the same Object-Style tricks as in pre-render (obeying the same linking rules too) but it&#8217;s called up by special scripts now, so we can cause some changes in movement. A box that appears to scroll up is just having it&#8217;s height value changed every couple of miliseconds but, apart from that, it&#8217;s the same as a pre-rendered box.</p>
<p>Finally there&#8217;s your Mobile Interface Design and the other side of General User Experience and Usability. In a way their outcomes of knowing the above two processes. If you understand how a website is displayed and how it changes then you know what you&#8217;re able to do which is the empowering that i think most designers need. With that they&#8217;re usually very capable of dealing with user feedback and pre-evaluating the user experience a lot more.</p>
<p>I guess I agree with Gary in intent but I don&#8217;t think it&#8217;s so much about the skills a designer picks up as opposed to spending time learning about the Process by which their work is going to be displayed. Much like they don&#8217;t need to know how a particular type of paper is made but only what it looks like, feels like and how it responds to various colours.</p>
<p>A more focused approach perhaps <img src='http://manwithnoblog.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Time to Drop Web Standards? by Ian Hickson</title>
		<link>http://manwithnoblog.com/2008/10/12/time-to-drop-web-standards/#comment-8280</link>
		<dc:creator>Ian Hickson</dc:creator>
		<pubDate>Sun, 12 Oct 2008 23:42:59 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=222#comment-8280</guid>
		<description>I am very concerned about the impression that people aren't welcome in the WHATWG -- let me be the first to reassure you that all feedback is very welcome, whoever it may come from. I guarantee that I will personally read and respond to every single piece of feedback sent to the whatwg@whatwg.org mailing list (see http://whatwg.org/ and http://whatwg.org/mailing-list#specs for details).

If you could let me know by private e-mail (ian@hixie.ch) why you felt turned away or not welcome, I would be very appreciative and will do everything I can to ensure that this doesn't happen again.</description>
		<content:encoded><![CDATA[<p>I am very concerned about the impression that people aren&#8217;t welcome in the WHATWG &#8212; let me be the first to reassure you that all feedback is very welcome, whoever it may come from. I guarantee that I will personally read and respond to every single piece of feedback sent to the <a href="mailto:whatwg@whatwg.org">whatwg@whatwg.org</a> mailing list (see <a href="http://whatwg.org/" rel="nofollow">http://whatwg.org/</a> and <a href="http://whatwg.org/mailing-list#specs" rel="nofollow">http://whatwg.org/mailing-list#specs</a> for details).</p>
<p>If you could let me know by private e-mail (ian@hixie.ch) why you felt turned away or not welcome, I would be very appreciative and will do everything I can to ensure that this doesn&#8217;t happen again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelancing in a Recession by James Bull</title>
		<link>http://manwithnoblog.com/2008/10/11/freelancing-in-a-recession/#comment-8273</link>
		<dc:creator>James Bull</dc:creator>
		<pubDate>Sun, 12 Oct 2008 16:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=220#comment-8273</guid>
		<description>Gary, that post was great advice for freelancers at any stage of an economic cycle, not just an impending recession.</description>
		<content:encoded><![CDATA[<p>Gary, that post was great advice for freelancers at any stage of an economic cycle, not just an impending recession.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelancing in a Recession by Gary Barber</title>
		<link>http://manwithnoblog.com/2008/10/11/freelancing-in-a-recession/#comment-8271</link>
		<dc:creator>Gary Barber</dc:creator>
		<pubDate>Sun, 12 Oct 2008 00:49:15 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=220#comment-8271</guid>
		<description>@Alain  Thanks for stopping by.   Interesting comments, I don't have a view point from the IT end of things as I have never worked with an IT section in the Web Industry.  It has always been with Marketing.  

Er... What freelance magazines? There are freelance magazines? Please enlighten me.</description>
		<content:encoded><![CDATA[<p>@Alain  Thanks for stopping by.   Interesting comments, I don&#8217;t have a view point from the IT end of things as I have never worked with an IT section in the Web Industry.  It has always been with Marketing.  </p>
<p>Er&#8230; What freelance magazines? There are freelance magazines? Please enlighten me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelancing in a Recession by Alain</title>
		<link>http://manwithnoblog.com/2008/10/11/freelancing-in-a-recession/#comment-8270</link>
		<dc:creator>Alain</dc:creator>
		<pubDate>Sat, 11 Oct 2008 21:39:13 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=220#comment-8270</guid>
		<description>i was freelancer in IT before. there are other issues

1) what is a big problem for a freelancer is when the market is dead, literally dead. Then someone as a very average employee may have a chance to stay even if there are layoffs, while almost all contractors are out of work. They will always as priority retrain employees even if they have absolutely no knowledge and layoff all contractors/consultants (i have seen it in some companies). It is the "temporary resource" side of contracting which i do not like.

2) another issue is overspecialisation and overexperienced.
When you are very specialised with lots of experience you have to normally to ask decent rates (at least more than junior people), the problem is that many clients prefer to hire JUNIOR people with no experience for various reasons. Sometimes its even. Simply there is only a very small market for senior experienced people. This is someway a marketing issue.   Furthermore if you have very specialised skills, you have to travel a lot or work very long time for the same client (then its better to be an employee). Also do not believe the bullshit in freelance magazines.</description>
		<content:encoded><![CDATA[<p>i was freelancer in IT before. there are other issues</p>
<p>1) what is a big problem for a freelancer is when the market is dead, literally dead. Then someone as a very average employee may have a chance to stay even if there are layoffs, while almost all contractors are out of work. They will always as priority retrain employees even if they have absolutely no knowledge and layoff all contractors/consultants (i have seen it in some companies). It is the &#8220;temporary resource&#8221; side of contracting which i do not like.</p>
<p>2) another issue is overspecialisation and overexperienced.<br />
When you are very specialised with lots of experience you have to normally to ask decent rates (at least more than junior people), the problem is that many clients prefer to hire JUNIOR people with no experience for various reasons. Sometimes its even. Simply there is only a very small market for senior experienced people. This is someway a marketing issue.   Furthermore if you have very specialised skills, you have to travel a lot or work very long time for the same client (then its better to be an employee). Also do not believe the bullshit in freelance magazines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelancing in a Recession by Rebecca Laffar-Smith</title>
		<link>http://manwithnoblog.com/2008/10/11/freelancing-in-a-recession/#comment-8269</link>
		<dc:creator>Rebecca Laffar-Smith</dc:creator>
		<pubDate>Sat, 11 Oct 2008 08:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=220#comment-8269</guid>
		<description>Great Tips, Gary! I really do think the most important one to remember is your first point, "DON'T PANIC!" It reminds me of The Hitchhiker's Guide To The Galaxy. The end of the world is coming, "Don't Panic". Because, ultimately, it's not an end at all.

As you said, economy rises and falls, it's a part of the cycle and the trick is to weather the storm. If you reflect on past history of 'depressions' you'll notice that over the long term we always come out ahead. That is the thing to remember.

In the now it's important to "Maintain Fundamentals" and "Go Back To Basics". These might sound similar but are two differing practices.

Maintaining your fundamentals is all about taking care of the little details. Keep up with your book keeping (even if it's a little bleak), be dogged about invoicing, keep sending out queries, and continue to do the day to day activities that make up your usual business practice. Just because times are tough does not mean you need to make dramatic changes to the things that work and will continue to work.

Getting back to basics however is about going simple. Did you upgrade to a 20 gig download plan on your internet? Cut back, you can live without the latest episode of Heroes and can save a chunk of cash on a lower plan. Did you get into the habit of having a rich slab of steak each week? Nothing wrong with Bangers and Mash! Honestly, we spend so much cash on luxury items because we learn to live in a higher income bracket. If you get back to basics for the time being you could save a great deal of money and find yourself financially well off when the fog of economic breakdown lifts.

I'm sure there are many other ideas that help get us through the tough times in a tighten your belt economy. Now is the perfect time to reflect and take action on them. :-)</description>
		<content:encoded><![CDATA[<p>Great Tips, Gary! I really do think the most important one to remember is your first point, &#8220;DON&#8217;T PANIC!&#8221; It reminds me of The Hitchhiker&#8217;s Guide To The Galaxy. The end of the world is coming, &#8220;Don&#8217;t Panic&#8221;. Because, ultimately, it&#8217;s not an end at all.</p>
<p>As you said, economy rises and falls, it&#8217;s a part of the cycle and the trick is to weather the storm. If you reflect on past history of &#8216;depressions&#8217; you&#8217;ll notice that over the long term we always come out ahead. That is the thing to remember.</p>
<p>In the now it&#8217;s important to &#8220;Maintain Fundamentals&#8221; and &#8220;Go Back To Basics&#8221;. These might sound similar but are two differing practices.</p>
<p>Maintaining your fundamentals is all about taking care of the little details. Keep up with your book keeping (even if it&#8217;s a little bleak), be dogged about invoicing, keep sending out queries, and continue to do the day to day activities that make up your usual business practice. Just because times are tough does not mean you need to make dramatic changes to the things that work and will continue to work.</p>
<p>Getting back to basics however is about going simple. Did you upgrade to a 20 gig download plan on your internet? Cut back, you can live without the latest episode of Heroes and can save a chunk of cash on a lower plan. Did you get into the habit of having a rich slab of steak each week? Nothing wrong with Bangers and Mash! Honestly, we spend so much cash on luxury items because we learn to live in a higher income bracket. If you get back to basics for the time being you could save a great deal of money and find yourself financially well off when the fog of economic breakdown lifts.</p>
<p>I&#8217;m sure there are many other ideas that help get us through the tough times in a tighten your belt economy. Now is the perfect time to reflect and take action on them. <img src='http://manwithnoblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Goodbye IE6 by Gary Barber</title>
		<link>http://manwithnoblog.com/2008/10/05/goodbye-ie6/#comment-8258</link>
		<dc:creator>Gary Barber</dc:creator>
		<pubDate>Sun, 05 Oct 2008 06:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=213#comment-8258</guid>
		<description>@Kay- yeah I saw that post. I'm not dropping support for IE6, more just moving it down a notch.  It's not getting the full attention to detail. But I agree it's going to be 2011-12 before we can forget about IE6, that's an entire career space for some people.</description>
		<content:encoded><![CDATA[<p>@Kay- yeah I saw that post. I&#8217;m not dropping support for IE6, more just moving it down a notch.  It&#8217;s not getting the full attention to detail. But I agree it&#8217;s going to be 2011-12 before we can forget about IE6, that&#8217;s an entire career space for some people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Goodbye IE6 by Kay Smoljak</title>
		<link>http://manwithnoblog.com/2008/10/05/goodbye-ie6/#comment-8257</link>
		<dc:creator>Kay Smoljak</dc:creator>
		<pubDate>Sun, 05 Oct 2008 05:43:18 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=213#comment-8257</guid>
		<description>I wrote just yesterday that I don't think I can drop support completely for IE6 until it gets to the 1-2% mark. Well, maybe 4-5% :)

Sadly, I think we have a long way to go yet. I'm actually grateful to Microsoft's security upgrade policies that pushed out IE5 far quicker than we would have seen otherwise. Hopefully IE6 will have the same fate by... oh I dunno, 2012?</description>
		<content:encoded><![CDATA[<p>I wrote just yesterday that I don&#8217;t think I can drop support completely for IE6 until it gets to the 1-2% mark. Well, maybe 4-5% <img src='http://manwithnoblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Sadly, I think we have a long way to go yet. I&#8217;m actually grateful to Microsoft&#8217;s security upgrade policies that pushed out IE5 far quicker than we would have seen otherwise. Hopefully IE6 will have the same fate by&#8230; oh I dunno, 2012?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Web Directions South 2008 by Gary Barber</title>
		<link>http://manwithnoblog.com/2008/09/29/web-directions-south-2008/#comment-8256</link>
		<dc:creator>Gary Barber</dc:creator>
		<pubDate>Sun, 05 Oct 2008 03:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=212#comment-8256</guid>
		<description>@Jeff Thanks for stopping by.  

The question on scalable font and accessibility is not really related to the age of the browser, but the usage rate in the wild.  Currently for IE6 it's around 35-40%.  This for me it just way to high a percentage to discount.   There is also the other factor people with disabilities downloading and installing new software.   Many find this a daunting task.  They are changing the configuration of their system, their lifeline in many cases.   This as you can appreciate is full of danger.   And hence they tend to err on the conservative side, as you would expect.   

So until the computer they are using dies they will usually continue to use the installed browser.   Which sadly is usually IE6 (even up to a few years ago). Hence I don't expect IE6 to slip below the magic 2% mark in the next few years. 

Jeff, I am over forty, I have vision problems, sometimes I have an issue with contrast, but more often  with font sizes. I have an extreme problem for instance reading your blog. So should I be discounted because I have vision problems.  Should parts of the web be inaccessible to me because of my age. 

All I'm asking is that you consider your fellow man. Maybe go observe how people with even minor disabilities have to struggle with parts of the web.  I can tell you personally it's a very humbling experience.</description>
		<content:encoded><![CDATA[<p>@Jeff Thanks for stopping by.  </p>
<p>The question on scalable font and accessibility is not really related to the age of the browser, but the usage rate in the wild.  Currently for IE6 it&#8217;s around 35-40%.  This for me it just way to high a percentage to discount.   There is also the other factor people with disabilities downloading and installing new software.   Many find this a daunting task.  They are changing the configuration of their system, their lifeline in many cases.   This as you can appreciate is full of danger.   And hence they tend to err on the conservative side, as you would expect.   </p>
<p>So until the computer they are using dies they will usually continue to use the installed browser.   Which sadly is usually IE6 (even up to a few years ago). Hence I don&#8217;t expect IE6 to slip below the magic 2% mark in the next few years. </p>
<p>Jeff, I am over forty, I have vision problems, sometimes I have an issue with contrast, but more often  with font sizes. I have an extreme problem for instance reading your blog. So should I be discounted because I have vision problems.  Should parts of the web be inaccessible to me because of my age. </p>
<p>All I&#8217;m asking is that you consider your fellow man. Maybe go observe how people with even minor disabilities have to struggle with parts of the web.  I can tell you personally it&#8217;s a very humbling experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Web Directions South 2008 by Jeff Croft</title>
		<link>http://manwithnoblog.com/2008/09/29/web-directions-south-2008/#comment-8254</link>
		<dc:creator>Jeff Croft</dc:creator>
		<pubDate>Mon, 29 Sep 2008 23:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=212#comment-8254</guid>
		<description>Thanks so much for coming to the type talk. Sorry it seemed to have disappointed you a bit. Just a couple comments:

1. I get mixed reviews about the fast-talking delivery. As many people seem to love it as hate it. Not sure what to do it about. Can really only be me, I guess.
2. As I said in the presentation, I don't at all think hanging bullets are "correct". What I say in the presentation is that they're "traditional." Traditional may or may not be what you're going for in a particular design. Suggesting that we should always use indented bullets and quotes is as ludicrous as suggesting we never should. "New rules" should not apply here -- and neither should old ones. Rather, these decisions should be made on a case-by-case basis. That's what design is all about. :)
3. I was a bit shocked by the response to the absolute vs. relative thing. I've given this talk a few times in the states and in the UK, and haven't ever had anyone take it as dismissive of accessibility. As I said in the talk, this, too, should be case-by-case. Everything is a tradeoff. Absolute sizing is easier -- no one can deny that. You can get things done faster using absolute sizes. Relative sizes are *arguably* more accessible, though I would contend that they are less and less so, as the browser which can't resize relative text slowly fades away. So, which is more important? Deadlines or accessibility? Well, that all depends on the project. As to: "We will see what Jeff has to say about absolute sized fonts when he is over 40 and his sight is starting to fade." When I'm 40 (that's 7.5 years, for those counting), IE6 will be long gone and all browsers will be able to resize absolutely sized text. In fact, all current browsers already can.</description>
		<content:encoded><![CDATA[<p>Thanks so much for coming to the type talk. Sorry it seemed to have disappointed you a bit. Just a couple comments:</p>
<p>1. I get mixed reviews about the fast-talking delivery. As many people seem to love it as hate it. Not sure what to do it about. Can really only be me, I guess.<br />
2. As I said in the presentation, I don&#8217;t at all think hanging bullets are &#8220;correct&#8221;. What I say in the presentation is that they&#8217;re &#8220;traditional.&#8221; Traditional may or may not be what you&#8217;re going for in a particular design. Suggesting that we should always use indented bullets and quotes is as ludicrous as suggesting we never should. &#8220;New rules&#8221; should not apply here &#8212; and neither should old ones. Rather, these decisions should be made on a case-by-case basis. That&#8217;s what design is all about. <img src='http://manwithnoblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
3. I was a bit shocked by the response to the absolute vs. relative thing. I&#8217;ve given this talk a few times in the states and in the UK, and haven&#8217;t ever had anyone take it as dismissive of accessibility. As I said in the talk, this, too, should be case-by-case. Everything is a tradeoff. Absolute sizing is easier &#8212; no one can deny that. You can get things done faster using absolute sizes. Relative sizes are *arguably* more accessible, though I would contend that they are less and less so, as the browser which can&#8217;t resize relative text slowly fades away. So, which is more important? Deadlines or accessibility? Well, that all depends on the project. As to: &#8220;We will see what Jeff has to say about absolute sized fonts when he is over 40 and his sight is starting to fade.&#8221; When I&#8217;m 40 (that&#8217;s 7.5 years, for those counting), IE6 will be long gone and all browsers will be able to resize absolutely sized text. In fact, all current browsers already can.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
