<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:thr="http://purl.org/syndication/thread/1.0" xml:lang="en" xml:base="http://intangiblestyle.com/wp-atom.php">
	<title type="text">intangiblestyle</title>
	<subtitle type="text">Creating 'Websites that Work'</subtitle>

	<updated>2012-02-26T02:36:35Z</updated>

	<link rel="alternate" type="text/html" href="http://intangiblestyle.com" />
	<id>http://intangiblestyle.com/feed/atom/</id>
	

	<generator uri="http://wordpress.org/" version="3.3.1">WordPress</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/Intangiblestyle" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="intangiblestyle" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">Intangiblestyle</feedburner:emailServiceId><feedburner:feedburnerHostname xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://feedburner.google.com</feedburner:feedburnerHostname><entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Web Strategy Basics: choosing a web designer]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2012/01/28/web-strategy-basics-choosing-web-designer/" />
		<id>http://intangiblestyle.com/?p=430</id>
		<updated>2012-01-28T14:53:21Z</updated>
		<published>2012-01-28T14:49:27Z</published>
		<category scheme="http://intangiblestyle.com" term="Articles" /><category scheme="http://intangiblestyle.com" term="Web Strategy Basics" /><category scheme="http://intangiblestyle.com" term="Website Owners" />		<summary type="html"><![CDATA[As a small business owner, you have enormous choice when looking for a web designer. The best approach is to forget fixed rules about what you ought to need. Instead,  during your initial discussions, follow some simple guidelines to help understand what’s on offer.  The result will be a better ‘fit’ with your chosen designer and a much better idea of where your project is going.]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2012/01/28/web-strategy-basics-choosing-web-designer/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2012%2F01%2F28%2Fweb-strategy-basics-choosing-web-designer%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2012%2F01%2F28%2Fweb-strategy-basics-choosing-web-designer%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>As a business owner looking for a website designer, you have an enormous amount of choice for who to work with—particularly at the level for a smaller business. Almost everyone knows someone who ‘does websites’ and any advertising brochure will show you more&#8230;not to mention the horde of results from a quick Google search! So how do you find out if someone you picked from all these options is going to be the right designer (or design team) for you?</p>
<p>Let&#8217;s take a step back for a moment. Essentially, a website project is a series of decisions &#8211; starting with “Should I hire you?” You&#8217;re looking for the best design, a design that will help you meet your goals while working with a compatible team <em>and</em> staying within your budget. With so much choice, the key to making the right decision is <em>communication</em>. Remember designers are also asking “Should I work with you?”—looking for clients who are ready to accomplish something meaningful, with an appropriate budget, and who will be good partners during the project.</p>
<p>In effect, the process of choosing a designer is the first part of the project’s ‘Discovery phase’. It can take just a few days, or more than a year if you&#8217;re in the early stages of considering a project. (That&#8217;s fine—as a designer, it&#8217;s always best to speak to people as early in their planning as possible.)</p>
<p>I&#8217;ve found that while everyone has different needs for choosing a designer and planning a project, there are some approaches to your early discussions and communication with a designer that will make it easier to decide if you want to work together. They also make it easier to walk away on good terms if you and a designer aren’t going to be a good fit—and often, I find, give enough insight to recommend a design team who may be a better choice. Looking further forward, it better prepares both you and the designer for each other&#8217;s communication and decision-making styles—which helps the whole project go more smoothly.</p>
<p>These approaches may seem obvious, but as with many obvious things they&#8217;re often not so obvious in the ‘heat of the moment.’ So, when you&#8217;re talking with a potential design team, remember to:</p>
<ul>
<li>
<h3>Be clear about all your needs, goals, concerns &amp; priorities</h3>
<p>When you work with a designer, you&#8217;re placing the future of your business, products and services in their hands. For the sake of your business, you need to be absolutely clear with them! It&#8217;s always a good idea to ask what the particular people you are talking to need to know to understand and scope the project. The answers are often revealing and may be surprising.</p>
<p>Putting it from the designer&#8217;s point of view, good design is user-centric: and when designing a project approach, you, the client, are the user. Your needs, goals, concerns and priorities are not just important, they&#8217;re the core essentials the project is designed around. The more you can share about your needs and context, the the better ‘fit’ the proposed project structure will be. It&#8217;s similar to the way that, in a focus group, responses uttered to impress participants can mislead a design team: not sharing project realities (and contexts) will make it hard to create the right proposal.</li>
<li>
<h3>Share all relevant constraints</h3>
<p>These are things like money, time-scale, business context, and must-have ideas or tactics. You can probably think of others, specific to your business, as well.</p>
<p>Money is usually the thorniest constraint. It&#8217;s hard to say “This is my budget,” to someone you haven&#8217;t decided to trust or hire yet. But if you&#8217;re upfront about your budget as far as possible (some people honestly don’t have a number until they hear a ‘ballpark figure’ and that’s fine), the whole process is a lot more efficient. This saves time <em>and</em> money.</p>
<p>Design is about finding a new way to solve a problem within constraints. Constraints themselves are not a difficulty: they are essential. To your designer, constraints give structure to problems and solutions, spur creativity, and help judge the success of a solution. It helps if you can separate actual constraints from personal preferences and must-have ideas. But do mention those too.</p>
<p>Bottom line – even if you think some of your constraints may be deal-breakers, give your designer a chance. The results will be better for it (and your designer will be happier).</li>
<li>
<h3>Ask every single question you have. Think of some more. Ask those too.</h3>
<p>Of all projects, the best start with people who ask a lot of questions! Good designers don’t mind being challenged on <em>any</em> aspect of their work. It&#8217;s something that should continue through the whole project. Go on, ask.</p>
<p>If you&#8217;re talking to me, ask how I work, why I’ve make certain choices, or how I’d respond in hypothetical situations. Ask why a proposal is structured that particular way. If anything is unclear, ask about that, too. Proposals, just like every other part of a project, are better with client feedback. Don’t hope someone will ‘get around’ to answering your question and don’t feel awkward about “not speaking design language.” Designers don&#8217;t expect you to know their business, but we do rely on you to know yours and to question everything we do from that basis!</p>
<p>When you&#8217;re in talks with a designer, you&#8217;re shopping for someone to solve problems for you. Asking lots of questions will help you evaluate what&#8217;s on offer, and get a sense for what people will be like to work with.</li>
<li>
<h3>Be open about your process</h3>
<p>For you, as for me (and every other design team), the selection process is an overhead. It’s the work we have to do to get to the &#8216;real&#8217; work.</p>
<p>Particularly at this stage, everyone wants to use their time efficiently. The more a prospective designer knows about your decision-making process, the better they&#8217;ll be equipped to give you what you need to reach a decision—even if that decision is that you won&#8217;t be a good fit.</p>
<p>If circumstances change—the project is off, you’ve selected someone else, or an internal team is taking on the work—just pick up the phone, or send a quick e-mail to anyone you’ve been talking to. Yes, it&#8217;s a little bit awkward, but it lets everyone feel good about the discussions we had and move on. Stuff happens. But please—if your non-disclosure rules allow!—include a one-sentence summary of what happened, as accurately as you can. No-one will have to wonder if they offended you (and they may be able to make things better for next time).</p>
<p>And remember, “No news” is also news—especially if the whole process is taking a while! A one-sentence update is both helpful and humane.</li>
</ul>
<p>The selection process is often the worst part of a website project and an uncomfortable period for all concerned. Trite as it sounds, no two businesses are the same: your people, processes and goals are all individual. What you need from a designer is every bit as individual, so there are no real short-cuts. Follow these ideas, though, and you&#8217;ll have an efficient, open and productive exchange of ideas—and very often, end up with a much better idea of what you&#8217;re looking for than you had in the beginning. Once you know both the designer and the proposal inside out, it can be surprisingly easy to decide if they&#8217;re right for you.
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2012%2F01%2F28%2Fweb-strategy-basics-choosing-web-designer%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2012%2F01%2F28%2Fweb-strategy-basics-choosing-web-designer%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2012/01/28/web-strategy-basics-choosing-web-designer/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2012/01/28/web-strategy-basics-choosing-web-designer/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Mobile First: solving IE vs. Symbian]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2010/09/22/mobile-first-solving-ie-vs-symbian/" />
		<id>http://intangiblestyle.com/?p=404</id>
		<updated>2011-09-03T01:49:02Z</updated>
		<published>2010-09-22T08:44:55Z</published>
		<category scheme="http://intangiblestyle.com" term="Articles" /><category scheme="http://intangiblestyle.com" term="CSS" /><category scheme="http://intangiblestyle.com" term="Mobile" />		<summary type="html"><![CDATA[As we all know, media queries are by far the best way to distinguish between desktop and mobile browsers, or, more generically, between the dozens of different screen sizes our users can have. Media queries are the future of the web.Nonetheless, the fact that they are the future doesn’t mean that there are no problems. [...]]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2010/09/22/mobile-first-solving-ie-vs-symbian/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2010%2F09%2F22%2Fmobile-first-solving-ie-vs-symbian%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2010%2F09%2F22%2Fmobile-first-solving-ie-vs-symbian%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<blockquote><p>As we all know, media queries are by far the best way to distinguish between desktop and mobile browsers, or, more generically, between the dozens of different screen sizes our users can have. Media queries are the future of the web.<br />Nonetheless, the fact that they are the future doesn’t mean that there are no problems. One is particularly tricky: what do we do for browsers that don’t support them?</p>
<p>- Peter-Paul Koch, <a href="http://www.quirksmode.org/blog/archives/2010/09/more_about_medi.html">More about media queries</a></p></blockquote>
<p>Those browsers are IE and Symbian, the two biggest browsers on desktop and mobile respectively. Clearly we need a solution that doesn&#8217;t leave one of them rendering CSS for the wrong platform.</p>
<p>(And since the aim is to fulfill the promise of <a href="http://www.quirksmode.org/blog/archives/2010/09/combining_meta.html">PPK&#8217;s original idea</a>, that solution needs to work client-side and without depending on JS.)</p>
<h3>The problem</h3>
<p>Usually, an IE problem would just bring out that dependable IE-wrangler, <a href="http://dev.opera.com/articles/view/supporting-ie-with-conditional-comments/">conditional comments</a>. Unfortunately, as people on the <a href="http://tech.groups.yahoo.com/group/mobile-web/message/3">mobile-web list</a> quickly spotted, that approach falls foul of IE6 Mobile.</p>
<p>You see, when faced with a conditional comment, <a href="http://www.brucelawson.co.uk/2008/ie-6-mobile-standards-compliance-tests/">IE6 Mobile acts as if it&#8217;s plain old IE6 on the desktop</a>. (Which it pretty much is, just squashed awkwardly into a mobile OS.)</p>
<p>It&#8217;s not the first time IE6 Mobile has caused annoying problems. It&#8217;s one of the many mobile browsers that read both &#8216;screen&#8217; and &#8216;handheld&#8217; CSS media types, and need a reset served to them so they don&#8217;t render the desktop styles. (Until PPK came up with this approach, anyway.)</p>
<h3>The solution</h3>
<p>Oddly enough, this once-annoying quirk ends up providing the solution. Using conditional comments, we can force IEs older than IE9 to read their own stylesheet, with the desktop styles and whatever fixes may be needed. On the end of this, we add an @media handheld block. This resets the desktop styles IE6 Mobile has just read, and replaces them with the mobile styles we want it to actually render.</p>
<p>Everyone gets the right styles, without any extra http requests. Phew.</p>
<p>Here&#8217;s how it all looks:</p>
<p><script src="http://gist.github.com/581794.js?file=gistfile2.html"></script><br />
<script src="http://gist.github.com/581794.js?file=old-ies.css"></script><br />
<script src="http://gist.github.com/581794.js?file=everything-else.css"></script></p>
<p>A couple of notes on future-proofing. IE9 understands media queries, so it gets the main stylesheet along with other modern browsers. Windows Phone 7 doesn&#8217;t read media queries, but it can be selected with its&#8217; own conditional comment. It gets the main stylesheet too so as to leave room for future versions that may understand media queries.
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2010%2F09%2F22%2Fmobile-first-solving-ie-vs-symbian%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2010%2F09%2F22%2Fmobile-first-solving-ie-vs-symbian%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2010/09/22/mobile-first-solving-ie-vs-symbian/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2010/09/22/mobile-first-solving-ie-vs-symbian/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Interface Watch: Google.com]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2009/12/19/interface-watch-google-com/" />
		<id>http://intangiblestyle.com/?p=375</id>
		<updated>2009-12-19T11:02:37Z</updated>
		<published>2009-12-19T10:53:04Z</published>
		<category scheme="http://intangiblestyle.com" term="Notes" /><category scheme="http://intangiblestyle.com" term="Interface Watch" /><category scheme="http://intangiblestyle.com" term="Usability" />		<summary type="html"><![CDATA[Google's updated search page sets a new of how to maximise usability by keeping things simple and focused on the task at hand. When first loaded, the page shows the logo and search box. <em>That's all</em>. Everything else is hidden.]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2009/12/19/interface-watch-google-com/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F19%2Finterface-watch-google-com%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F19%2Finterface-watch-google-com%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://intangiblestyle.com/wp-content/uploads/2009/12/google-search-clean.jpg"><img src="http://intangiblestyle.com/wp-content/uploads/2009/12/google-search-clean-450x227.jpg" alt="Screenshot of Google&#039;s new search page, with all extraneous elements hidden" title="Google&#039;s new, even more focused search interface" width="450" height="227" class="alignleft" /></a>
<p>For a long time, Google&#8217;s search page has been a leading example of how to maximise usability by keeping things simple and focused on the task at hand. The interface consists simply of Google&#8217;s logo and a search box&mdash;everything else is kept small and out of the way. The distractions are minimal so users can focus easily.</p>
<p>There&#8217;ve been a few tweaks made over the years, but never anything really noticeable to casual users.</p>
<p>Not any more. When you load <a href="http://google.com/">Google&#8217;s new homepage</a>, you see the logo and search box. <em>That&#8217;s all</em>. Everything else is hidden. You can type your search, press enter, and that&#8217;s all you&#8217;ll ever see.</p>
<p>For the vast majority of searchers, apparently, that&#8217;s enough. But move your mouse&mdash;indicating, Google says, that you might want to do something more&mdash;and the rest of the page fades smoothly in, allowing access to the rest of Google&#8217;s services.</p>
<p>Nice!</p>
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F19%2Finterface-watch-google-com%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F19%2Finterface-watch-google-com%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2009/12/19/interface-watch-google-com/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2009/12/19/interface-watch-google-com/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[What makes a website successful?]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2009/12/05/what-makes-a-website-successful/" />
		<id>http://intangiblestyle.com/?p=369</id>
		<updated>2010-07-15T17:56:22Z</updated>
		<published>2009-12-05T21:58:43Z</published>
		<category scheme="http://intangiblestyle.com" term="Articles" /><category scheme="http://intangiblestyle.com" term="Usability" />		<summary type="html"><![CDATA[Over at 24ways, Paul Boag suggests that a website's success is actually determined by whether its content supports the owners' business objectives, is targeted at the right audience, and provides appropriate calls to action. True, but there's more to it than that.]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2009/12/05/what-makes-a-website-successful/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F05%2Fwhat-makes-a-website-successful%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F05%2Fwhat-makes-a-website-successful%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://24ways.org/">24ways</a>, the advent calendar for web geeks, is back again. <a href="http://24ways.org/2009/what-makes-a-website-successful">Entry #4</a> is from Paul Boag, and he&#8217;s suggesting that a website&#8217;s success really isn&#8217;t, after all, determined by valid code, accessibility, usability, or attractive design &#8211; but by whether its content supports the owners&#8217; business objectives, is targeted at the right audience, and provides appropriate calls to action. </p>
<p>Paul cites eBay and Amazon as examples: they achieved huge success by uniting the right content with the right audience, regardless of design, poor code quality and major (and minor) usability issues.</p>
<p>True, as far as it goes. But I think there&#8217;s more to it than that &#8211; and that web developers&#8217; other skills shouldn&#8217;t be rejected as useless.</p>
<p>Why? Because there are actually 3 facets to a successful website:</p>
<ul>
<li>content that serves the right audience ad business goals</li>
<li>&#8216;findability&#8217; to ensure that the audience gets to the site</li>
<li>usability to ensure they can achieve the goals when they get there</li>
</ul>
<p>eBay and Amazon are exceptions, but they&#8217;re exceptions that prove the rule. What they got absolutely right was matching great content to the needs of their audience.</p>
<p>They were able to &#8216;short-circuit&#8217; findability by making sure everyone knew about them. Search engine performance really didn&#8217;t mean much when everyone searched for &#8216;ebay&#8217; and &#8216;amazon&#8217; not &#8216;online auctions&#8217; and &#8216;online bookshop&#8217;. (Most people, of course, won&#8217;t have this advantage, so skills like writing valid code, accessibility and SEO come back into play.)</p>
<p>Likewise, being the &#8216;first and only&#8217; (at least that everyone <em>knew</em> about) helped deal with minor, or even major, usability issues. They were &#8216;usable enough&#8217; in the beginning, when competitors were unknown and the general trend on the web was of task failure. (Jakob Nielsen estimates nearly 60% of the time.) As they&#8217;ve lost that advantage over time, usability (and its relations like <abbr title="User Experience">UX</abbr>, <abbr title="Information Architecture">IA</abbr> and so on) have renewed importance. For everyone else, they&#8217;ve always been there.
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F05%2Fwhat-makes-a-website-successful%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F12%2F05%2Fwhat-makes-a-website-successful%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2009/12/05/what-makes-a-website-successful/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2009/12/05/what-makes-a-website-successful/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Coding like it&#039;s 2009]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2009/06/21/coding-like-2009/" />
		<id>http://intangiblestyle.com/?p=360</id>
		<updated>2009-06-21T11:57:35Z</updated>
		<published>2009-06-21T11:57:35Z</published>
		<category scheme="http://intangiblestyle.com" term="Articles" /><category scheme="http://intangiblestyle.com" term="Accessibility" />		<summary type="html"><![CDATA[Cameron Moll suggests we can safely go back to sizing text in pixels - because new browsers allow anyone who wants to resize it. Sorry Cameron, but for people who care about accessibility, that's just plain wrong.]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2009/06/21/coding-like-2009/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F06%2F21%2Fcoding-like-2009%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F06%2F21%2Fcoding-like-2009%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Back in 1999, when <abbr title="Internet Explorer">IE</abbr> ruled the world and most people still used tables for layout, pixel-sized text was one of the web&#8217;s great evils. <abbr title="Internet Explorer">IE</abbr>, you see, couldn&#8217;t resize text sized in pixels &#8211; which meant huge numbers of sites were inaccessible to almost anyone with less-than-perfect vision. Web developers who cared about accessibility (or usability) learned instead to size text in ems&mdash;a unit relative to the browser&#8217;s default text size.</p>
<p>A decade on, we have <a href="http://getfirefox.com/" title="Firefox 3">lots</a> <a href="http://opera.com/" title="Opera 9.5">of</a> <a href="http://apple.com/safari/" title="Safari 4">new</a> <a href="http://microsoft.com/ie8/" title="Internet Explorer 8">browsers</a>, all of them capable of using page zoom, resizing not only pixel-sized text, but images too. So, Cameron Moll suggests in <a href="http://www.cameronmoll.com/archives/2009/06/coding_like_its_1999/">Coding like it&#8217;s 1999</a>, we can safely go back to sizing text in pixels &#8211; because now anyone who wants can resize it.</p>
<blockquote><p>What does all this mean? It means px can again be considered a viable value for font-size.<br />
- Cameron Moll</p></blockquote>
<p>Sorry Cameron, but for people who care about accessibility, that&#8217;s just plain wrong.</p>
<p>Approximately ~17% worldwide still use <abbr title="Internet Explorer">IE</abbr>6 (<a href="NetApplications, May 2009|http://marketshare.hitslink.com/browser-market-share.aspx?qprid=2">NetApplications, May 2009</a>). Much as we might want <abbr title="Internet Explorer">IE</abbr>6 to die, that&#8217;s hardly an insignificant market share. Even allowing for the drop in <abbr title="Internet Explorer">IE</abbr>6 usage at weekends, quite a lot of people would be potentially disadvantaged. (As an aside, <a href="http://www.456bereastreet.com/archive/200902/ie_8_still_does_not_resize_text_sized_in_pixels/"><abbr title="Internet Explorer">IE</abbr>7  and 8 still don&#8217;t scale pixel-sized text</a>. We don&#8217;t know how many <abbr title="Internet Explorer">IE</abbr>7 or 8 users prefer text scaling to page zoom, but we <em>do</em> know that if they&#8217;re on a pixel-sized site their preferred type of scaling won&#8217;t work.)</p>
<p>Looking deeper, em-sized text isn&#8217;t just scaleable &#8211; it does a better job of respecting users preferences.</p>
<ul>
<li>It&#8217;s based on the browsers default text settings, which are set to ensure basic readability.</li>
<li>If your em values are reasonable, most readers won&#8217;t be obliged to adjust text scale.</li>
<li>It makes a better solution available to users who need larger text&mdash;they can increase the browser&#8217;s default text size.</li>
<li>For users who aren&#8217;t tech-savvy enough to do that, it ensures text is <em>always</em> resizeable.</li>
</ul>
<p>The bottom line, though, is that as professionals, we shouldn&#8217;t force users to adopt a technical solution to a problem that we can easily solve for them. Yes, working with ems is <a href="http://www.sitepoint.com/blogs/2007/04/30/typography-baseline-rhythm-deciphered/" title="Matthew Magain explains how to make text-in-ems easy">a little more difficult</a>, but as <a href="http://ericmiraglia.com/blog/?p=181">Nate Koechley put it recently</a>, &#8220;It’s OK for us to suffer a little bit to give the user a better experience; that’s what we’re here for.&#8221; The fact that a technical solution exists doesn&#8217;t relieve us of responsibility to <em>get things right</em> in the first place and stop the problem ever happening.</p>
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F06%2F21%2Fcoding-like-2009%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F06%2F21%2Fcoding-like-2009%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2009/06/21/coding-like-2009/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2009/06/21/coding-like-2009/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Interface Watch: Twitter pagination]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2009/05/28/interface-watch-twitter-pagination/" />
		<id>http://intangiblestyle.com/?p=331</id>
		<updated>2009-05-28T11:46:29Z</updated>
		<published>2009-05-28T11:46:29Z</published>
		<category scheme="http://intangiblestyle.com" term="Notes" /><category scheme="http://intangiblestyle.com" term="Interface Watch" /><category scheme="http://intangiblestyle.com" term="Usability" />		<summary type="html"><![CDATA[<p>Twitter's pagination controls have always been simple, but recently they got a whole lot simpler. The classic 'next' and 'prev' links have been replaced by a single 'more' button that loads more tweets on the same page.</p>]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2009/05/28/interface-watch-twitter-pagination/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F05%2F28%2Finterface-watch-twitter-pagination%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F05%2F28%2Finterface-watch-twitter-pagination%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><a href="http://www.intangiblestyle.dreamhosters.com/wp-content/uploads/2009/05/more-twitter.jpg"><img src="http://intangiblestyle.com/wp-content/uploads/2009/05/more-twitter-450x132.jpg" alt="Screenshot of Twitter&#039;s new pagination control: a simple 'more' button." title="Twitter&#039;s &lsquo;more&rsquo; button" width="450" height="132" class="alignleft" /></a></p>
<p>Twitter&#8217;s pagination controls have always been simple, but recently they got a whole lot simpler. The <a href="http://www.flickr.com/photos/kurafire/558255022/">classic &#8216;next&#8217; and &#8216;prev&#8217; links</a> have been replaced by a single &#8216;more&#8217; button that loads more tweets on the same page.</p>
<p>Simplified pagination controls like this can greatly improve usability, and they&#8217;ve been around for a while as bookmarklets, browser add-ons and in the occasional web-app. (<a href="http://www.dopplr.com/">Dopplr</a> uses a similar control for lists of contacts.) But it seems to be the first time an interface like this has appeared quite so prominently in a high-profile application.</p>
<p>Unfortunately, Twitter&#8217;s version doesn&#8217;t degrade gracefully, so usability actually gets <em>worse</em> when JavaScript is unavailable. Clicking &#8216;more&#8217; reloads the page with the next group of tweets&hellip;but doesn&#8217;t provide a link to return to the page you were on before. Forcing users to resort to their browser&#8217;s back button isn&#8217;t ideal&mdash;it would have been better to use progressive enhancement and to show the AJAX-dependent &#8216;more&#8217; button only if AJAX is actually available.</p>
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F05%2F28%2Finterface-watch-twitter-pagination%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F05%2F28%2Finterface-watch-twitter-pagination%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2009/05/28/interface-watch-twitter-pagination/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2009/05/28/interface-watch-twitter-pagination/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Where to find CSS Web Fonts]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2009/04/13/where-to-find-css-web-fonts/" />
		<id>http://intangiblestyle.com/?p=266</id>
		<updated>2009-10-19T11:19:11Z</updated>
		<published>2009-04-13T09:15:58Z</published>
		<category scheme="http://intangiblestyle.com" term="Articles" /><category scheme="http://intangiblestyle.com" term="CSS" /><category scheme="http://intangiblestyle.com" term="Typography" />		<summary type="html"><![CDATA[<p>Thanks to support in Safari, Firefox and Opera, and Jon Tan's efforts to make them co-exist with <abbr title="Internet Explorer">IE</abbr>'s proprietary EOT format, CSS web fonts are becoming a reality. But the major font foundries are still resisting the idea of licensing fonts for distribution via CSS. So here are a few places where you <em>can</em> find high-quality fonts that can legally be redistributed.]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2009/04/13/where-to-find-css-web-fonts/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F04%2F13%2Fwhere-to-find-css-web-fonts%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F04%2F13%2Fwhere-to-find-css-web-fonts%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Thanks to the upcoming releases of Firefox and Opera with webfonts support, existing support in Safari, and <a href="http://jontangerine.com/log/2008/10/font-face-in-ie-making-web-fonts-work">Jon Tan&#8217;s efforts</a> to make them co-exist with <abbr title="Internet Explorer">IE</abbr>&#8216;s proprietary EOT format, CSS web fonts are becoming a reality. But the major font foundries are <a href="http://www.clagnut.com/blog/2166/">still resisting</a> the idea of licensing fonts for distribution via CSS. So where can we find quality fonts that can legally be redistributed?</p>
<p>There are, of course, many font repositories out there. Some, like <a href="http://fontsquirrel.com/">Font Squirrel</a>, even focus on high-quality fonts that are free for commercial use. But the vast majority even of these fonts can&#8217;t be redistributed&mdash;and finding the few that can takes more time than most designers have to spend.</p>
<p>Fortunately, there are a few places out that showcase <em>entirely</em> redistributable fonts. <del>It&#8217;s a short list, for now, but one that&#8217;s hopefully going to grow.</del> Six months on, it&#8217;s a sizeable list&mdash;with great-quality fonts for just about any purpose.</p>
<ul>
<li><a href="http://opentype.info/demo/webfontdemo.html">10 Great Free Fonts for @font-face embedding</a>&mdash;Ralf Herrmann’s original list</li>
<li><a href="http://www.webfonts.info/wiki/index.php?title=Commercial_foundries_which_allow_%40font-face_embedding">Commercial foundries which allow @font-face embedding</a> and <a href="http://www.webfonts.info/wiki/index.php?title=Fonts_available_for_%40font-face_embedding">free fonts available for @font-face embedding</a>at the WebFonts.info wiki</a></li>
<li><a href="http://www.dafont.com/top.php?nb_ppp_old=10&#038;page=1&#038;top=1&#038;text=Type+your+text+here&#038;nb_ppp=10&#038;psize=m&#038;classt=alpha&#038;l[]=10">DaFont.com</a> now lets you search for GPL-licensed fonts (which are, of course, all redistributable)</li>
<li><a href="http://www.josbuivenga.demon.nl/">Exljbris Font Foundry</a></li>
<li><a href="http://www.fontsquirrel.com/fontface">Font Squirrel&#8217;s @font-face list</a> is long and comprehensive&mdash;and they include EOT versions and sample stylesheets too!</li>
<li><a href="http://www.theleagueofmoveabletype.com/">League of Moveable Type</a></li>
<li><a href="http://home.comcast.net/~crudfactory/cf3/index.xhtml">The Crud Factory</a></li>
<li><a href="http://openfontlibrary.fontly.org/">Open Font Library</a></li>
</ul>
<p>If you know of anywhere else that hosts exclusively (or mostly) high-quality redistributable fonts, let everyone else know in the comments!</p>
<p class="tip">4/7/09 &#8211; I&#8217;ve updated the list to add the Crud Factory and Open Font Library.</p>
<p class="tip">19/10/09 &#8211; Added FontSquirrel and DaFont.com &#8211; via <a href="http://blog.themeforest.net/tutorials/css-font-face-and-15-free-fonts-you-can-use-today/">Jarel Remick</a>. Thanks Jarel!</p>
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F04%2F13%2Fwhere-to-find-css-web-fonts%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F04%2F13%2Fwhere-to-find-css-web-fonts%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2009/04/13/where-to-find-css-web-fonts/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2009/04/13/where-to-find-css-web-fonts/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Safari 4 beta released]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2009/02/27/safari-4-beta-released/" />
		<id>http://intangiblestyle.com/?p=257</id>
		<updated>2009-02-27T09:26:10Z</updated>
		<published>2009-02-27T09:26:10Z</published>
		<category scheme="http://intangiblestyle.com" term="Notes" />		<summary type="html"><![CDATA[Apple has released a beta version of its Safari 4 browser. It brings with it plenty of UI innovations and a few usability issues, as well as some solid improvements to web standards support.]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2009/02/27/safari-4-beta-released/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F02%2F27%2Fsafari-4-beta-released%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F02%2F27%2Fsafari-4-beta-released%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Apple has released a beta version of its Safari 4 browser, which brings with it <a href="http://apple.com/safari">plenty of UI innovations</a> and <a href="http://arstechnica.com/apple/news/2009/02/hands-on-safari-4-beta-fast-mixes-polish-rough-ui-edges.ars">a few usability issues</a>. There&#8217;s a great deal of cool stuff included: &#8216;tabs on top&#8217; (borrowed from Chrome), &#8216;Top Sites&#8217; (borrowed from Opera), and new location bar searching based on Firefox 3&#8242;s &#8216;Awesomebar&#8217;. There&#8217;s also a substantial JavaScript speedup&mdash;even if Apple&#8217;s claimed &#8220;7x faster than Firefox&#8221; is based on a <a href="http://twitter.com/jeresig/status/1245129943">slightly dodgy testsuite</a>, it&#8217;s still a respectable 1.6x faster according to the well-respected Sunspider test.</p>
<p>Developers aren&#8217;t neglected, either. HTML5 support now includes offline storage and the <code>&lt;video&gt;</code> and <code>&lt;audio&gt;</code> tags. Combined with improved CSS3 support, CSS Transformations and Animations, better SVG and SMIL, basic WAI-ARIA support, and a revamped Web Inspector, it looks like Safari 4 is gong to be an excellent release and a solid advance for web standards.</p>
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F02%2F27%2Fsafari-4-beta-released%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F02%2F27%2Fsafari-4-beta-released%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2009/02/27/safari-4-beta-released/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2009/02/27/safari-4-beta-released/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Setting up screen reader testing]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2009/01/05/screen-reader-test-setup/" />
		<id>http://intangiblestyle.com/?p=200</id>
		<updated>2009-01-05T09:05:20Z</updated>
		<published>2009-01-05T09:05:20Z</published>
		<category scheme="http://intangiblestyle.com" term="Notes" /><category scheme="http://intangiblestyle.com" term="Accessibility" />		<summary type="html"><![CDATA[<p>Ever wondered how to set up your machine for testing with screen readers? Todd Kloots at YUIBlog has an article on setting up Jaws, Window-Eyes and NVDA for testing in a virtual machine.</p>]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2009/01/05/screen-reader-test-setup/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F01%2F05%2Fscreen-reader-test-setup%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F01%2F05%2Fscreen-reader-test-setup%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>Ever wondered how to set up your machine for testing with screen readers? It&#8217;s one of those things that can take a long time and a fair bit of trial and error to work out&mdash;until now. Todd Kloots at YUIBlog has posted an article on <a href="http://yuiblog.com/blog/2008/12/30/configuring-screen-readers/">setting up Jaws, Window-Eyes and NVDA for testing</a> in a virtual machine. He talks through finding demo versions to test with, getting set up and tweaking settings for easier testing as a sighted person.</p>
<p>While it would have been nice to see some reference to testing with other ARIA-capable readers, such as <a href="http://projects.gnome.org/orca/">Orca</a> or <a href="http://www.firevox.clcworld.net/features.html">FireVox</a>, it&#8217;s an excellent guide to getting set up for testing on Windows. Using <abbr title="Virtual Machines">VMs</abbr> means the approach is even useful cross-platform.</p>
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F01%2F05%2Fscreen-reader-test-setup%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2009%2F01%2F05%2Fscreen-reader-test-setup%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2009/01/05/screen-reader-test-setup/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2009/01/05/screen-reader-test-setup/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
		<entry>
		<author>
			<name>Matthew</name>
						<uri>http://intangiblestyle.com/</uri>
					</author>
		<title type="html"><![CDATA[Merry Christmas (and a few links)]]></title>
		<link rel="alternate" type="text/html" href="http://intangiblestyle.com/2008/12/25/merry-christmas-links/" />
		<id>http://intangiblestyle.com/?p=171</id>
		<updated>2008-12-25T08:26:21Z</updated>
		<published>2008-12-25T08:26:21Z</published>
		<category scheme="http://intangiblestyle.com" term="Notes" /><category scheme="http://intangiblestyle.com" term="Miscellaneous" />		<summary type="html"><![CDATA[<p>It's been a busy time of year. I've missed a few things worth writing about, so here's a Christmas present in the form of a few links.</p>]]></summary>
		<content type="html" xml:base="http://intangiblestyle.com/2008/12/25/merry-christmas-links/"><![CDATA[<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2008%2F12%2F25%2Fmerry-christmas-links%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2008%2F12%2F25%2Fmerry-christmas-links%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>It&#8217;s been a busy time of year. Apart from preparing for Christmas and wrapping up the odd project, I&#8217;ve <a href="http://twitter.com/intangible/status/1064713660">been away</a> for a while, attending my Grandfather&#8217;s funeral. In the meantime I missed a few things worth writing about, so here&#8217;s a Christmas present in the form of a few links:</p>
<ul>
<li><a href="http://www.webstandards.org/2008/12/11/wcag-20-is-a-w3c-rec/">WCAG 2.0 becomes a W3C Recommendation</a>. At last web accessibility takes a big step forward from version 1.0.</li>
<li>Roger Johansson has a round up of how to create more <a href="http://www.456bereastreet.com/archive/200812/making_google_maps_more_accessible/">accessible Google Maps</a>.</li>
<li>TechCrunch came out with a new <a href="http://www.techcrunch.com/2008/11/26/techcrunchs-new-search-engine-powered-by-yahoo-boss/">search engine based on Yahoo!&#8217;s BOSS &#8216;Vertical Lens&#8217;</a> custom search technology. Sadly only available to Yahoo! partners at the moment&#8230;</li>
<li>Robert Nyman released a new version of his <a href="http://www.robertnyman.com/inline-code-finder/">Inline Code Finder</a> Firefox extension&mdash;which now handles inline CSS as well as JavaScript.</li>
<li>Peter Nederlof&#8217;s <a href="http://www.xs4all.nl/~peterned/csshover.html">Whatever:hover</a> reached version 3. It now works with AJAX, and supports :focus and :active as well as :hover.</li>
<li>Cameron Moll has a discussion about resources for a <a href="http://cameronmoll.com/archives/2008/12/four_resources_when_starting_a_project/">starting a new project</a>.</li>
<li>Andy Clarke has two posts on beautiful web typography at For a Beautiful Web: <a href="http://forabeautifulweb.com/blog/about/typesetting_the_waste_land/">Typesetting the Waste Land</a> and <a href="http://forabeautifulweb.com/blog/about/typography_is_poetry_more_on_typesetting_the_waste_land/">Typography is Poetry</a>.</li>
<li>Benjamin Smedberg takes a look at a crop of cross-browser issues with <a href="http://benjamin.smedbergs.us/blog/2008-12-22/using-svg-on-the-web/">using SVG on the web</a>.</li>
<li>Aza Raskin writes about <a href="http://www.azarask.in/blog/post/the-interface-of-resturant-reciepts/">real-world usability</a> &#8211; with paper receipts, no less.</li>
<li>No Christmas links roundup would be complete without mention of <a href="http://24ways.org/2008">24ways</a>. From the <a href="http://24ways.org/2008/easing-the-path-from-design-to-development">design to development transition</a> to tips on <a href="http://24ways.org/2008/recession-tips-for-web-designers">surviving the recession</a>, the advent calendar for web geeks is as brilliant as ever.</li>
</ul>
<p>And a bonus link: Merlin Mann&#8217;s <a href="http://www.merlinmann.com/rightnow/">&#8216;Is this really what you want to be doing right now?&#8217;</a> The answer, of course, is no, I have Christmas to celebrate. ;)</p>
<p>Merry Christmas!</p>
<div class="tweetmeme_button" style="float: right; margin: .3em 0 0 1em;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fintangiblestyle.com%2F2008%2F12%2F25%2Fmerry-christmas-links%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fintangiblestyle.com%2F2008%2F12%2F25%2Fmerry-christmas-links%2F&amp;source=intangible&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content>
		<link rel="replies" type="text/html" href="http://intangiblestyle.com/2008/12/25/merry-christmas-links/#comments" thr:count="0" />
		<link rel="replies" type="application/atom+xml" href="http://intangiblestyle.com/2008/12/25/merry-christmas-links/feed/atom/" thr:count="0" />
		<thr:total>0</thr:total>
	</entry>
	</feed><!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 1399/1501 objects using disk: basic

Served from: intangiblestyle.com @ 2012-05-16 00:11:07 -->

