<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blog Standard Stuff &#187; Web Standards</title>
	<atom:link href="http://lloydi.com/blog/category/web-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://lloydi.com/blog</link>
	<description>Nothing to do with standards, even less to do with wombats, only vaguely a blog</description>
	<lastBuildDate>Thu, 05 Feb 2009 00:23:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Interview for SitePoint Newsletter</title>
		<link>http://lloydi.com/blog/2006/05/23/learn-web-design-beginners-interview/</link>
		<comments>http://lloydi.com/blog/2006/05/23/learn-web-design-beginners-interview/#comments</comments>
		<pubDate>Tue, 23 May 2006 11:24:44 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Sitepoint Book]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/2006/05/23/learn-web-design-beginners-interview/</guid>
		<description><![CDATA[This is an email interview that I did for Matt Mickiewicz over at SitePoint &#8211; it&#8217;s to go into a newsletter that goes out to SitePoint&#8217;s various sales reps and distributors. I&#8217;m not sure it it&#8217;s going to be used anywhere else online, but I thought it would be useful to publish here anyway &#8211; [...]]]></description>
			<content:encoded><![CDATA[<p>This is an email interview that I did for Matt Mickiewicz over at SitePoint &#8211; it&#8217;s to go into a newsletter that goes out to SitePoint&#8217;s various sales reps and distributors. I&#8217;m not sure it it&#8217;s going to be used anywhere else online, but I thought it would be useful to publish here anyway &#8211; tell you a little more about the book I wrote.</p>
<h3>What do you think makes your book different from all the other &#8220;beginning web design&#8221; books on the market? Why?</h3>
<p>I can do better than just <em>think</em> that it&#8217;s different &#8211; when I was at the beginning of the book-writing process, I did my homework and researched the other beginners books. Without exception, when I flicked through those books I kept <a xhref="http://accessify.com/2005/10/piss-poor-publishing-or-teaching-new.php">discovering advice that was outdated or just plain wrong</a>, despite some of them having undergone rewrites (in second and third editions). It was actually quite shocking and made me realise that the SitePoint book was very much needed &#8211; a <a xhref="http://beginningwebdesign.com/">beginners book</a> that taught the right skills from the start, rather than cutting corners for quick results, thereby teaching bad habits that later need to be unlearnt.</p>
<h3>Why should beginners worry about tables, CSS or accessibility?</h3>
<p>Firstly, because it&#8217;s the right thing to do. Although I would argue that they don&#8217;t <em>need</em> to worry at all. The worry comes from learning the wrong way at the beginning (see response to previous question!) and then thinking that accommodating these ideas is going to be difficult &#8211; and it can be if you are trying retrospectively fix issues. To answer the question point-by-point, though, tables are not needed for layout these days, and by not teaching that method, it will allow beginners to redesign their sites far more easily and reap benefits of having their sites work on a much wider range of devices. CSS, well, it really is the way to add presentation to a website, and I&#8217;d be doing a misjustice if I suggested otherwise. Finally, accessibility: in all honesty, I&#8217;ve not covered that a huge amount in the book, but have ensured that all the techniques and approaches are accessible, and have provided the reader with more information about the topic so that they can learn at their own pace. It is a big topic in its own right, after all.</p>
<h3>Who do you think is the ideal reader for this title?</h3>
<p>My mum. Or my sister. Or maybe even yours? Seriously, I had my sister in my mind when I wrote the table of contents. She is a 40-year-old mother of two tearaways, uses the computer for email, browsing the web, a bit of shopping, but is not a techy by any stretch. She&#8217;s now a Mac user because she got fed up with virus problems and wants things to just work. When she has difficulty with anything, she asks questions in non-technical ways, and she learns by the same methods. With that in mind, I set out to write a book that would enable her to build a web site without any prior knowledge, without requiring her to go out and buy any new software but to make use of what&#8217;s already there (or free to download) and I didn&#8217;t try to force too much information in one go. So that was my model reader &#8211; and I&#8217;m <em>sure</em>there are many others out there like her. Now we&#8217;ve just got to stop these people buying the other beginners&#8217; books and read the good stuff!</p>
<h3>How much will readers learn from the book? What will they be able to do once they finish reading it? What&#8217;s going to be their next step?</h3>
<p>From a complete novice, the reader will learn how to use the tools at their disposal to create a small web site that is standards- compliant, accessible, easy to update (via a blog), can be searched by visitors, looks good (particularly if they have some nice images to use) and that others can contribute to (via the blog, also). By the end of the book, the reader will understand the basics, will have put them all to use and will be in an excellent position to further their skills, having already got CSS-layouts, semantic markup and web standards awareness under their belt. In short, they&#8217;ll be better set up for all the other excellent intermediate/advanced books out their than they could ever achieve with the other beginners books. I truly believe this!</p>
<h3>In this day and age, why would someone want to build a website as opposed to putting up a page on MySpace or starting a blogger.com account, both of which require a lot less knowledge and work?</h3>
<p>I will give you an analogy. It&#8217;s a car one (something I&#8217;ve used before, but hey ho, it works for me!).I have a <a xhref="http://vwkombi.com">30 year old VW van</a>. I bought it in Aus, drove it all around Australia, then kept it, <a xhref="http://www.vwkombi.com/shipping-kombi-to-uk.html">shipped it to UK</a> and am continually making changes to it &#8211; a little tweak here, a little fix there. Now, money permitting, I could go out and buy a spangly, <a xhref="http://www.vwkombi.com/photos/beachbuggin-2005/Pages/16.html">jaw-droppingly good split screen camper van</a>, a <a xhref="http://www.vwkombi.com/photos/beachbuggin-2005/Pages/5.html">real show-stopper</a>. But I would not feel any sense of achievement as it would be someone else&#8217;s restoration work.</p>
<p>I feel the same about hand-crafting a site vs getting something off the shelf. The off-the-shelf approach is fine for a quick hit &#8211; and I won&#8217;t deny that for many people that will do just fine &#8211; but if you do it yourself you&#8217;ll get the result you&#8217;re after, have much more control, get a greater sense of achievement and will truly learn a skill that you can put to good use later. Who knows, it could be the way that you earn a crust one day? I don&#8217;t know anyone who makes a lot of money by setting up Blogger accounts for friends, but I know a lot of people who make a good earning &#8211; more than I do, I am unhappy to report! &#8211; by creating web sites for clients that could not possibly be created using a tool such as those you&#8217;ve mentioned. They have their place, but sometimes it&#8217;s just not enough, know what I mean?</p>
<h3>End of the &#8216;interview&#8217; &#8230;</h3>
<p>So, if having read that you feel this is the book for you (or mum/sister/brother/whatever), please head on over to SitePoint and order your copy today. Ah go on, I&#8217;ll be your best friend! </p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/05/23/learn-web-design-beginners-interview/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Book news &#8211; First Podcast mention (that I know of!)</title>
		<link>http://lloydi.com/blog/2006/05/19/book-news-first-podcast-mention-the-i-know-of/</link>
		<comments>http://lloydi.com/blog/2006/05/19/book-news-first-podcast-mention-the-i-know-of/#comments</comments>
		<pubDate>Fri, 19 May 2006 08:57:25 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Sitepoint Book]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/2006/05/19/book-news-first-podcast-mention-the-i-know-of/</guid>
		<description><![CDATA[My book got a mention on Boagworld&#8217;s podcast, and I thought I&#8217;d transcribe and respond to some of the comments Paul made here: 

&#34;It&#8217;s called Build Your Own Web Site the Right Way using HTML and CSS. What a nice snappy title! He needs to work on his title a bit.&#34; 

Yeah, not my choice [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://beginningwebdesign.com/">My book</a> got a <a href="http://www.boagworld.com/archives/2006/05/podcast_34_the_roles_of_the_client_and_the_web_des.html">mention on Boagworld&#8217;s podcast</a>, and I thought I&#8217;d transcribe and respond to some of the comments Paul made here: </p>
<blockquote>
<p>&quot;It&#8217;s called <cite>Build Your Own Web Site the Right Way using HTML and CSS</cite>. What a nice snappy title! He needs to work on his title a bit.&quot; </p>
</blockquote>
<p>Yeah, not my choice of title. It is a bit long-winded, but then if it were called &quot;Beginners Guide to Building a Web Site (with Web Standards)&quot; – or some variation on that theme – the very audience that it&#8217;s aimed for probably wouldn&#8217;t get it. Would the absolute beginner know what web standards are or why they matter? So while I would love to have had a shorter title (e.g. <cite>CSS Mastery</cite>, <cite>DOM Scripting</cite>), those titles only really work for those who know a bit about the topic. Or at least that&#8217;s my theory as to why SitePoint went for that title. Anyway, Paul continues: </p>
<blockquote>
<p>&quot;The book came about because one day he was hanging around in PC World or whatever, as you do if you&#8217;re a geek, and he picked up the books about HTML that were on the shelves, dummies guide on how to build web sites and that kind of stuff, and was horrified at the fact that they all taught horrendous ways to build web sites, very old-fashioned, very out-of-date, not very accessible etc [Marcus – ' In schools they do as well'] … Yeah, I know, they still teach table-based design … So basically he decided to write a web design book that taught you from absolute basics, from knowing nothing about HTML, CSS or anything else of how to build a web site but doing it the right way, as his snappy title says&quot; </p>
</blockquote>
<p>Well, that&#8217;s <em>almost</em> right, but I can&#8217;t claim to have had the idea for writing the book, to be honest. What happened was that when I had made a start on the early chapters I wanted to check that I was on the right track, so on a weekend shopping trip I did a bit of ad-hoc research … and that&#8217;s when I discovered <a href="http://accessify.com/2005/10/piss-poor-publishing-or-teaching-new.php">just how badly a book like mine was needed</a>. It basically gave me a lot of encouragement because in the early days of writing the book, despite feeling proud to have been approached about the book deal, I did have a slight feeling of &quot;does the world need another book about HTML?&quot;. That very unscientific bit of research in Borders and Waterstones really made me appreciate the importance of getting this book right!</p>
<blockquote>
<p>&quot;<strong>Apparently it&#8217;s an excellent book</strong>, [I'm not going to argue with that! - Ian] I haven&#8217;t got a copy of it, I haven&#8217;t seen it. But <strong>I&#8217;m always getting asked, y&#8217;know, &#8216;how do I get into web design, how do I learn it?&#8217; It seems like this book is a good place to start</strong>.&quot; </p>
</blockquote>
<p>Paul, you&#8217;ve hit the nail on the head there. I realise that it&#8217;s difficult for me to get my peers to buy a copy as they won&#8217;t learn anything from it, but it <em><strong>is</strong></em> the book that they can reccommend to their friends/colleagues/loved ones safe in the knowledge that they will learn the right way and, at the end of the book, be at a level where they can pick up some of the <a href="http://beginningwebdesign.com/other-books/">other excellent web design books</a> out there without feeling that they have to re-educate themselve on the importance of standards, semantics and such like. </p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/05/19/book-news-first-podcast-mention-the-i-know-of/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What&#8217;s wrong with Flickr?</title>
		<link>http://lloydi.com/blog/2006/05/17/whats-wrong-with-flickr/</link>
		<comments>http://lloydi.com/blog/2006/05/17/whats-wrong-with-flickr/#comments</comments>
		<pubDate>Wed, 17 May 2006 08:59:35 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/2006/05/17/whats-wrong-with-flickr/</guid>
		<description><![CDATA[From the moment I was first introduced to photo-sharing site Flickr, I was smitten. I loved it &#8211; loved the interaction it offered, loved the ease with which I was able to upload and share photos, loved the fact that storage and bandwidth allowance was so high (beyond what I&#8217;d be able to upload on [...]]]></description>
			<content:encoded><![CDATA[<p>From the moment I was first introduced to photo-sharing site <a href="http://flickr.com/">Flickr</a>, I was smitten. I loved it &#8211; loved the interaction it offered, loved the ease with which I was able to upload and share photos, loved the fact that storage and bandwidth allowance was so high (beyond what I&#8217;d be able to upload on any given month, at least on the paid-for service). In short, I became a total Flickr advocate. But something still bothered me &#8230;</p>
<h3>The old navigation &#8211; confusing!</h3>
<p>Some of the navigation was, prior to yesterday&#8217;s updates, confusing to say the least. For example, let&#8217;s say I wanted to find the recent activity (stuff that people have commented on/added notes on) or check out other people&#8217;s photos that I&#8217;ve commented on (to see if any other comments/conversation has ensued). For the former, I could find the link in the footer. For <em>me</em>, this was not &#8216;footer material&#8217; &#8211; it&#8217;s one of the most important pages on Flickr. What&#8217;s it doing there at the bottom? Anyway, that&#8217;s a side issue. The confusion for me is that this page and the &#8216;photos you&#8217;ve commented on&#8217; page are, essentially, two sides of the same coin. Yet I could only easily find the first of those pages. To get to the other page I needed to first pick a photo, one of my own actually (which, depending on where I am in Flickr at the time, might involve 2 or 3 clicks to get there), then scroll down underneath the photo where I&#8217;d find a link to both those pages. This is just one example where I&#8217;ve found the placement of navigation confusing and inconsistent, and that required me to be familiar with the site and remember the route to these pages. There were other issues, but I&#8217;ll not harp on about that. I have other things to harp on about &#8230;</p>
<h3>The all-new Gamma version</h3>
<p>Flickr have gone from &#8216;Beta&#8217; to &#8216;Gamma&#8217; stage in the last 24 hours. I think it&#8217;s the first time I&#8217;ve seen that badge applied to any web site! The changes are mostly navigational ones (thankfully), although there are general UI tidy-ups and a re-working of the Organizr (which really needed it &#8211; I cannot count the number of times I got script time-out errors when using it). I&#8217;ve yet to really get to grips with the changes, so there may be a follow-on to this post, but my initial thought is:</p>
<p>How are Flickr getting away with it?</p>
<p>And by that I mean, how is it that a site that is loved so much by the tech-savvy, blogging and web standards community (read nerds, pedants etc &#8211; I can say this, &#8216;cos I&#8217;m in that group!) seems to escape criticism of its make-up/build? At least, it seems to me that it does. We&#8217;ll criticize the smallest validation error in sites that otherwise do an excellent job of sticking to standards, but Flickr, well &#8230; it looks so nice and all that, who wants to say bad things? Well, I do, for one.</p>
<h3>Little mistakes that should not be there</h3>
<p>Where are the <code>alt</code> attributes for these images below, folks?</p>
<p><img src="/blog/flickrmissingalts.gif" alt="Flickr's missing alt attributes" width="447" height="157" /> </p>
<p>And these fancy drop-down navigation items? They are not keyboard-navigable.</p>
<p><img src="/blog/flickrtopnav.gif" alt="Flickr's top navigation - not keyboard accessible" width="425" height="64" /></p>
<p> Oops. And, as an aside, they do not even work with a mouse when I try to use the site at work &#8211; the company firewall actively blocks JavaScript that appears that it might be doing something nasty, which it has done in this case. I tried to disable scripting (using the Firefox Web Developer Toolbar), but there is not a <code>noscript</code> alternative for this navigation. To get to any of these sub items, I now have to disable style sheets to reveal the links and then re-enable CSS when I get where I want to be:</p>
<p><img src="/blog/flickrdisablecssnav.gif" alt="Disabled CSS to reveal links" width="416" height="81" /></p>
<p>Do people still do this? Apparently so. Spacers, yeah!</p>
<p><img src="/blog/flickrspacer.gif" alt="Using spacer as alt text - not good" width="71" height="83" /> </p>
<p>View profile? How about &#8216;view luxuryluke&#8217;s profile&#8217; as an <code>alt</code> attribute? Simple enough to do &#8211; not sure why this kind of thing gets missed off:</p>
<p><img src="/blog/flickrviewprofile.gif" alt="Alt text for view profile is lacking a little" width="504" height="140" /> </p>
<p>And again, some more prudent <code>alt</code> work wouldn&#8217;t go amiss. How about simply using &#8216;See all public photos tagged with SitePoint&#8217;? The &#8216;Click this icon to &#8230;&#8217; part is somewhat superfluous.</p>
<p><img src="/blog/flickrclickthis.gif" alt="More alt problems" width="236" height="109" /> </p>
<h3>Don&#8217;t mind me, I&#8217;m just a pedant</h3>
<p>This may seem like another example of pedantry, but I believe simple things like those I&#8217;ve noted above are easily avoided. There are bigger issues that I could address (such as the keyboard accessibility of the site as a whole, the overuse of tables for layout that could be solved with relatively simple CSS), but I&#8217;ve said enough for one day. I&#8217;m off to throw stones at some kittens now, grumpy old git that I am. </p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/05/17/whats-wrong-with-flickr/feed/</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
		<item>
		<title>Out now &#8211; my beginners&#8217; book on Web Standards</title>
		<link>http://lloydi.com/blog/2006/05/11/out-now-my-beginners-book-on-web-standards/</link>
		<comments>http://lloydi.com/blog/2006/05/11/out-now-my-beginners-book-on-web-standards/#comments</comments>
		<pubDate>Thu, 11 May 2006 22:54:32 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Sitepoint Book]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/2006/05/11/out-now-my-beginners-book-on-web-standards/</guid>
		<description><![CDATA[I&#8217;m thrilled to announce that my book, Build Your Own Website the Right Way Using HTML and CSS, is now out on SitePoint. I received my personal copies today and am really pleased with the end result (it&#8217;s surprising how much fun it is to re-read your own work in this format &#8230; but it&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m thrilled to announce that my book, Build Your Own Website the Right Way Using HTML and CSS, is now out on <a href="http://www.sitepoint.com/books/html1/">SitePoint</a>. I <a href="http://www.flickr.com/photos/ianlloyd/144558914/">received my personal copies today</a> and am really pleased with the end result (it&#8217;s surprising how much fun it is to re-read your own work in this format &#8230; but it&#8217;s a real bummer when you find a typo!).</p>
<p><a href="http://www.flickr.com/photos/ianlloyd/144558914/" title="Photo Sharing"><img src="http://static.flickr.com/53/144558914_cd89a07c7f.jpg" width="384" height="500" alt="My personal copies" /></a></p>
<p>I&#8217;d really appreciate any mention you folks can provide for me &#8211; that&#8217;s assuming that anyone other than family members reads this blog :-D.  If you feel like promoting a book about web standards that you could happily give to your mum and know that she&#8217;ll learn the right way, please do link to this page (and if you <strong>really</strong> want to help promote standards such that Google points people in the right direction, it&#8217;d be great if you used words such as <a href="http://beginningwebdesign.com/">beginners&#8217; guide to web standards</a> or similar).</p>
<p>Anyway, that&#8217;s my shameless marketing plea over &#8211; I really hope you can help in some small way :-)</p>
<p><!-- </p>
<p>PS &#8211; I accept no responsibility/ownership for the cheesy schoolboy humour on page 86. As I read through my thoughts went from &#8220;hang on, I don&#8217;t remember writing this part&#8221; to &#8220;my God, this is just embarassing&#8221;. Trust me, I&#8217;ll be requesting that bit gets scrubbed for any future revision!</p>
<p><a href="http://www.flickr.com/photos/ianlloyd/145004094/" title="Photo Sharing"><img src="http://static.flickr.com/51/145004094_4470c3f04a_m.jpg" width="240" height="126" alt="page-86" /></a><br />I didn&#8217;t write that!</p>
<p><a href="http://www.flickr.com/photos/ianlloyd/145004093/" title="Photo Sharing"><img src="http://static.flickr.com/51/145004093_57a670fe7f_m.jpg" width="240" height="122" alt="no-69" /></a><br />See, it wasn&#8217;t in the second draft I submitted.</p>
<p>&#8211;></p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/05/11/out-now-my-beginners-book-on-web-standards/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Simply BBC</title>
		<link>http://lloydi.com/blog/2006/04/27/simply-bbc/</link>
		<comments>http://lloydi.com/blog/2006/04/27/simply-bbc/#comments</comments>
		<pubDate>Thu, 27 Apr 2006 09:11:27 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/2006/04/27/simply-bbc/</guid>
		<description><![CDATA[Following on from the Simply Google idea that he came up with a little while ago (which I re-coded for him in nice standards-based markup with unobtrusive scripts) Chris McEvoy has done the same thing with the BBC. Predictably entitled Simply BBC, it&#8217;s another one-stop entrance to all things BBC. And once again, it&#8217;s based [...]]]></description>
			<content:encoded><![CDATA[<p>Following on from the <a href="http://www.goo-home.com/">Simply Google</a> idea that he came up with a little while ago (which I <a href="http://lloydi.com/blog/2006/04/13/simply-google-made-simpler/">re-coded for him in nice standards-based markup</a> with unobtrusive scripts) <a href="http://www.usabilityviews.com/">Chris McEvoy</a> has done the same thing with the BBC. Predictably entitled <a href="http://www.usabilityviews.com/simply_bbc.htm">Simply BBC</a>, it&#8217;s another one-stop entrance to all things BBC. And once again, it&#8217;s based on the CSS-based version that I provided for the precursor. As with the Google idea, what it&#8217;s done for me is reveal sections of the BBC&#8217;s site that I never knew existed (or at least wasn&#8217;t that bothered about going out to find). In other words, it&#8217;s all about improving the discoverability factor. Try it out, see what you think.</p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/04/27/simply-bbc/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>A simpler Simply Google</title>
		<link>http://lloydi.com/blog/2006/04/13/simply-google-made-simpler/</link>
		<comments>http://lloydi.com/blog/2006/04/13/simply-google-made-simpler/#comments</comments>
		<pubDate>Thu, 13 Apr 2006 08:59:17 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/?p=167</guid>
		<description><![CDATA[My esteemed colleague Chris McEvoy apparently had &#8216;one of his moments&#8217; (he has these, you know) last Sunday evening and decided he was fed up with having to search Google for some of Google&#8217;s more hidden features (oh the irony!), such as Answers, Suggest and so on. So he created Simply Google.
 
Is it simpler?
Mmm, [...]]]></description>
			<content:encoded><![CDATA[<p>My esteemed colleague <a href="http://www.usabilityviews.com/">Chris McEvoy</a> apparently had &#8216;one of his moments&#8217; (he <a href="http://usability.typepad.com/confusability/2005/11/kate_bush_sings.html">has</a> <a href="http://usability.typepad.com/confusability/2006/03/what_if_jakob_n.html">these</a>, you know) last Sunday evening and decided he was fed up with having to search Google for some of Google&#8217;s more hidden features (oh the irony!), such as <a href="http://answers.google.com/answers/">Answers</a>, <a href="http://www.google.com/search?complete=1">Suggest</a> and so on. So he created <a href="http://www.goo-home.com/">Simply Google</a>.</p>
<p><a href="http://www.goo-home.com/"><img src="/blog/simplygoogle.gif" alt="Simply Google" width="350" height="311" border="0"/></a> </p>
<h3>Is it simpler?</h3>
<p>Mmm, debateable. The very thing that people say makes Google work is its simple interface. Wanna search? Here&#8217;s the search box, people! What Chris did was put all the various different Google search options on one page, making it far easier to learn what options are available, but it&#8217;s not for everybody. Whether you like it or not, you cannot deny that he&#8217;s ticked off that &#8216;findability&#8217; box on the checklist.</p>
<h3>The CSS makeover</h3>
<p>Just as the Simply Google page was getting noticed by various people, Chris approached me to ask for some help in kicking it into standards mode (<a href="http://lloydi.com/blog/simplygoogleoriginal.htm">it was a table-based layout with non-breaking spaces and various examples of markup abuse to achieve presentational effects</a>). Ironically, I had thought of doing just that and was going to <em>approach him</em> with the idea of creating a &#8216;Simpler Simply Google&#8217;! So, that&#8217;s what I did. There are a few points I just wanted to make about the CSS make-over:</p>
<ul>
<li>I didn&#8217;t redesign the look and feel in any way. I kept to the blueprint (with just one exception &#8211; changing the location/style of the footer text) </li>
<li>My aim was to rebuild without tables and make it 100% valid XHTML, strict (achieved)</li>
<li>The biggest issue I had was with the search forms not having <code>label</code> elements. In the original version, there was a direct link to the site that the search facility related to. I could have replaced the link with a <code>label</code>. Instead, I decided to use both. For screen reader users, the <code>label</code> element provides a little more contextual information than before, but for sighted users the link will take them to the web site. The problem would be for users who try to click on the <code>label</code> and expect it to give focus to the search <code>input</code> element. It does this, for a second, but then the link behaviour takes over and loads the page requested. My feeling is that if it looks like a link, people will only click on it to use it as a link. Is this wrong? As I said, I did this with the intention of keeping to the original design.</li>
<li>The labels for the search are <em>after</em> the input. This is another thing that I would normally not do, hence I wanted to explain:
<ul>
<li>The intention was that when this page is viewed on a handheld device that does not apply the CSS (or any other browser that does not get CSS for whatever reason), the search boxes should line up nicely. If the <code>label</code> elements were in front of the <code>input</code> boxes, with no CSS they would create an unsightly ragged effect :<br />
       <img src="/blog/labelsrightaligned.gif" alt="labels appear after the input with CSS disabled" width="150" height="155"/>       </li>
<li>A downside of this is that the tab order is a bit strange on a fully CSS-capable browser (try it out for yourself). Should I have placed higher importance on the tab order or on the appearance of the page with no CSS? </li>
</ul>
</li>
</ul>
<p>So, that was my CSS make-over of <a href="http://goo-home.com/">Simply Google</a>. I&#8217;m interested in your thoughts/feedback. </p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/04/13/simply-google-made-simpler/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Going Naked!</title>
		<link>http://lloydi.com/blog/2006/04/03/naked-as-a-jaybird/</link>
		<comments>http://lloydi.com/blog/2006/04/03/naked-as-a-jaybird/#comments</comments>
		<pubDate>Mon, 03 Apr 2006 11:26:05 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/?p=165</guid>
		<description><![CDATA[I posted this over at webstandards.org earlier, but thought I&#8217;d cross-post it here for my approximate 2.3 average daily readers (hi sis! Hello, erm , me!): April 5th is CSS Naked Day, and this site will be bearing all. To be honest, all I&#8217;ll be showing is the markup that *someone else* created for this [...]]]></description>
			<content:encoded><![CDATA[<p>I posted this over at <a href="http://www.webstandards.org/2006/04/03/get-naked/">webstandards.org</a> earlier, but thought I&#8217;d cross-post it here for my approximate 2.3 average daily readers (hi sis! Hello, erm , me!): April 5th is <a href="http://naked.dustindiaz.com/">CSS Naked Day</a>, and this site will be bearing all. To be honest, all I&#8217;ll be showing is the markup that *someone else* created for this page (it&#8217;s an off-the-shelf CSS design that I&#8217;ve used here). All the same, I feel like I should join in here as well as at <a href="http://accessify.com/">Accessify</a>. Who knows, maybe seeing my nudey bits here will encourage me to get some new threads. And by that convoluted phrase what I&#8217;m really saying is this &#8211; Ian, redesign this frickin&#8217; site already. There, that told me.</p>
<p>I wonder if Dustin ever considered hosting CSS Naked Day on the <a href="http://en.wikipedia.org/wiki/Steak_and_Blowjob_Day">14th of March</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/04/03/naked-as-a-jaybird/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Going to the Printing Press</title>
		<link>http://lloydi.com/blog/2006/03/23/going-to-the-printing-press/</link>
		<comments>http://lloydi.com/blog/2006/03/23/going-to-the-printing-press/#comments</comments>
		<pubDate>Thu, 23 Mar 2006 23:46:17 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Sitepoint Book]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://lloydi.com/blog/2006/03/23/going-to-the-printing-press/</guid>
		<description><![CDATA[The book heads for the printing press the end of next week. Yeehaw!
Update: the book is now available for pre-order on Amazon UK and Amazon.com (thanks for pointing that out, Craig).
In the meantime, here&#8217;s what the book might look like if you just happened to have the world&#8217;s shiniest table to stand it up on:

]]></description>
			<content:encoded><![CDATA[<p><a href="http://lloydi.com/blog/2006/03/02/one-of-the-many-reasons-i-have-been-quiet-part-3/">The book</a> heads for the printing press the end of next week. Yeehaw!</p>
<p><strong>Update:</strong> the book is now available for pre-order on <a href="http://www.amazon.co.uk/exec/obidos/ASIN/0975240293/">Amazon UK</a> and <a href="http://www.amazon.com/gp/product/0975240293/">Amazon.com</a> (thanks for pointing that out, <a href="http://www.focalcurve.com/">Craig</a>).</p>
<p>In the meantime, here&#8217;s what the book might look like if you just happened to have the world&#8217;s shiniest table to stand it up on:</p>
<p><a href="http://www.flickr.com/photos/ianlloyd/116953887/"><img src='/blog/sitepointbookrefelected.jpg' alt='The cover design for my book, due out on Sitepoint real soon' /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/03/23/going-to-the-printing-press/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How to Print Selective Sections of a Web Page using CSS and DOM Scripting</title>
		<link>http://lloydi.com/blog/2006/03/21/how-to-print-selective-sections-of-a-web-page-using-css-and-dom-scripting-2/</link>
		<comments>http://lloydi.com/blog/2006/03/21/how-to-print-selective-sections-of-a-web-page-using-css-and-dom-scripting-2/#comments</comments>
		<pubDate>Tue, 21 Mar 2006 09:02:25 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[Scripting]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://www.lloydi.com/blog/2006/03/21/how-to-print-selective-sections-of-a-web-page-using-css-and-dom-scripting-2/</guid>
		<description><![CDATA[This is an experiment to see if it&#8217;s possible to selectively print sections of a large document usings CSS print styles after the page has loaded without affecting the on-screen display.
Why might you use this? Well, the inspiration came from a page of interest rates from banking and savings products. Customers have often complained that [...]]]></description>
			<content:encoded><![CDATA[<p>This is an experiment to see if it&#8217;s possible to selectively print sections of a large document usings CSS print styles after the page has loaded without affecting the on-screen display.</p>
<p>Why might you use this? Well, the inspiration came from a page of interest rates from banking and savings products. Customers have often complained that the interest rates were split up on different sections &#8211; they wanted everything in one page. But what about those people who only want to print out the section that relates to them? One solution is to build the page using include files with separate printer-friendly pages that are linked to. This solution uses DOM scripting to dynamically apply print CSS styles depending on the link that has been clicked on &#8211; if the user clicks on &#8216;print this section&#8217;, all other sections are set to display none for print. </p>
<p>This technique could be use in </p>
<ul>
<li>FAQs</li>
<li>Product information pages</li>
<li>&#8230; well, wherever you feel it has value </li>
</ul>
<p>This has been tested and works in </p>
<ul>
<li>Windows
<ul>
<li>Firefox 1.5</li>
<li>Netscape 6.2</li>
<li>Netscape 8</li>
<li>Opera 7.0 </li>
<li>Opera 8.5</li>
<li>IE 6</li>
</ul>
</li>
<li>Mac
<ul>
<li>Firefox 1.5</li>
<li>Camino 1.0</li>
<li>Opera 7.54   </li>
</ul>
</li>
</ul>
<h3>Notes:</h3>
<p>The &#8216;print this section&#8217; links are <strong>dynamically</strong> inserted for any section that is marked with the <code>class</code> name of <code>section</code> and are hidden using print CSS. No JavaScript, no see the links!</p>
<p>I have had to double up on the attribute setters in the script so that IE didn&#8217;t get upset. It&#8217;s not perfect, but it works and isn&#8217;t really nasty. No, honestly, it isn&#8217;t ;-)
  </p>
<pre>
<code>el[i].setAttribute(&quot;<strong>className</strong>&quot;,&quot;section print&quot;);
el[i].setAttribute(&quot;<strong>class</strong>&quot;,&quot;section print&quot;);
</code></pre>
<h3><a href="http://lloydi.com/experiments/selective-printing/print_selective_sections.html">View the Example Here &raquo; </a></h3>
<p>And if you like what you see, why not <a href="http://digg.com/submit?phase=2&#038;url=http://www.lloydi.com/blog/2006/03/21/how-to-print-selective-sections-of-a-web-page-using-css-and-dom-scripting-2/">digg it for me</a>? Thanks</p>
<h3>Copy the Code Here</h3>
<p>Get the <a href="http://lloydi.com/experiments/selective-printing/print_sections.js">JavaScript here</a> and the <a href="http://lloydi.com/experiments/selective-printing/print_selective_sections.html">HTML here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/03/21/how-to-print-selective-sections-of-a-web-page-using-css-and-dom-scripting-2/feed/</wfw:commentRss>
		<slash:comments>67</slash:comments>
		</item>
		<item>
		<title>One of the (Many) Reasons I Have Been Quiet, part 3</title>
		<link>http://lloydi.com/blog/2006/03/02/one-of-the-many-reasons-i-have-been-quiet-part-3/</link>
		<comments>http://lloydi.com/blog/2006/03/02/one-of-the-many-reasons-i-have-been-quiet-part-3/#comments</comments>
		<pubDate>Thu, 02 Mar 2006 10:59:47 +0000</pubDate>
		<dc:creator>Lloydi</dc:creator>
				<category><![CDATA[Sitepoint Book]]></category>
		<category><![CDATA[Web Standards]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://www.lloydi.com/blog/2006/03/02/one-of-the-many-reasons-i-have-been-quiet-part-3/</guid>
		<description><![CDATA[Ever the apologist, here I am again justifying lack of activity on this site (and some others) over the last year or two (the list of other time-suckers can be found here). What&#8217;s the justification this time? Well, it&#8217;s a good one.
While travelling around the globe a couple of years ago, I started doing some [...]]]></description>
			<content:encoded><![CDATA[<p>Ever the apologist, here I am again justifying lack of activity on this site (and some others) over the last year or two (the <a href="http://www.lloydi.com/blog/2006/02/08/back-from-the-dead/">list of other time-suckers can be found here</a>). What&#8217;s the justification this time? Well, it&#8217;s a good one.</p>
<p>While travelling around the globe a couple of years ago, I started doing some <a href="http://www.sitepoint.com/books/checklists1/?SID=a4e852c8d5af0e3de435d9ce8f63e75c">technical editing for Sitepoint</a>. It was a great way to earn a bit of money to pay my way while not getting in the way of moving from place to place &#8211; no bar work or fruit-picking for me! Much of this editing work was carried out in the <a href="http://vwkombi.com/photos/around-australia/Pages/16.html">back of my van</a> in the late hours while my wife-to-be snoozed. When I returned to UK after travelling, I was approached about some more potential writing work. Despite the fact that I knew I had an extremely busy year ahead of me, somehow I felt brave enough to take it on. Over seven months, while dealing with two house sales, buying a new house and making tentative <a href="http://ianandmanda.com/photos/">wedding</a> plans, I spent many evenings working on this project. Today, for the first time, I saw the  evidence that it was finally coming to fruition &#8211; Sitepoint have added the book to their &#8216;coming soon&#8217; section.</p>
<h4>So, what&#8217;s the book about?</h4>
<p>At this point, it might be worth re-reading <a href="http://accessify.com/2005/10/piss-poor-publishing-or-teaching-new.php">this post about the poor state of many beginner web design books on the market</a>. The reason for my trip to the book shops was to really get a feel for what&#8217;s out there and to make sure that I was on track with what I was writing. I couldn&#8217;t have been happier at how bad it was &#8211; it made me realise that what I had started writing for Sitepoint was much needed and much overdue.</p>
<h4>Who is this book aimed at?</h4>
<p>Well, chances are it&#8217;s <em>not</em> aimed at you. As much as I&#8217;d like to say it&#8217;s a cutting edge book about CSS tricks that you and I love to peruse, or an accessibility book with a slightly different angle than those currently out there, it&#8217;s neither. This is what it is:</p>
<ul>
<li>It&#8217;s a book that you can give to your web newbie mother/sister/auntie</li>
<li>It doesn&#8217;t presume any foreknowledge of HTML or ownership of any expensive/fancy web authoring software (nor does it suggest going out and buying any)</li>
<li>While it&#8217;s for beginners, it&#8217;s not going to call anyone a dummy ;-) </li>
<li>It&#8217;s a web design book that refuses to teach bad, outdated practices as a way of getting  eye-catching results more quickly than the &#8216;proper&#8217; method. For example, the first time you will see page layout covered is with CSS in chapter 4. Tables are covered &#8211; but in a chapter about managing data in tables, just where they should be . </li>
</ul>
<p>In short, it&#8217;s a book that aims to teach complete beginners how to build web sites that conform to web standards such that they won&#8217;t need to unlearn bad practices at a later date, or even know that those bad practices exist.</p>
<p>Well, I&#8217;ve talked it up so much, about time I provided a link:</p>
<p><a href="http://www.sitepoint.com/books/html1/?SID=a4e852c8d5af0e3de435d9ce8f63e75c">Build Your First Website The Right Way Using HTML &amp; CSS</a></p>
<p>Publication date is March/April (I believe the latter ismore likely). If you think you know someone that this could be of benefit to, please do add your name to the notification list (by joining the <a href="http://www.sitepoint.com/books/bookclub.php?gotobookclub=Join+the+Club">Sitepoint Book Buyers&#8217; Club</a>). I am looking forward to seeing the finished result &#8230; and I really <em>do</em> wonder what bizarre and completely off-topic picture this book will have on the cover! </p>
]]></content:encoded>
			<wfw:commentRss>http://lloydi.com/blog/2006/03/02/one-of-the-many-reasons-i-have-been-quiet-part-3/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
