Modernizr is an open-source JavaScript library that helps you build the next generation of HTML5 and CSS3-powered websites.

haha -- I know, I was straining my eyes to read the content!!

This article follows on from last month's Part I, where we discussed some of the principles of handling mobile users and switching their experiences. If you haven't read it yet please do so before we dive into some of the technical ideas and implementation details.

Determining a unit of measurement to size our text can be a topic of heated debate, even in this day and age. Unfortunately, there are still various pros and cons that make the various techniques less desirable. It's just a matter of which less-desirable is most desirable.

So there you are, minding your own business, using Webmaster Tools to check out how awesome your site is... but, wait! The Crawl errors page is full of 404 (Not found) errors! Is disaster imminent?? Fear not, my young padawan. Let's take a look at 404s and how they do (or do not) affect your site:

Mobile devices such as smartphones and tablets usually have a capacitive touch-sensitive screen to capture interactions made with the user's fingers. As the mobile web evolves to enable increasingly sophisticated applications, web developers need a way to handle these events. For example, nearly any fast-paced game requires the player to press multiple buttons at once, which, in the context of a touchscreen, implies multi-touch. Apple introduced their touch events API in iOS 2.0. Android has been catching up to this de-facto standard and closing the gap. Recently a W3C working group has come together to work on this touch events specification. In this article I'll dive into the touch events API provided by iOS and Android devices, explore what sorts of applications you can build, present some best practices, and cover useful techniques that make it easier to develop touch-enabled applications.

Ever seen a website where you just want to touch everything? Tim Van Damme explains the techniques he used in the Gowalla redesign What do drop shadows, gradients, rounded corners, transformations and animations have in common? Yes, they're a recipe for the disaster we once called Web 2.0, and have since been taken behind the shed, but they're also a group of new tricks we can do with CSS. Not all browsers support them yet, but enough do to let us have some fun.

Features listed in this section will trigger warnings in conformance checkers. Authors should not specify an http-equiv attribute in the Content Language state on a meta element. The lang attribute should be used instead. Authors should not specify a border attribute on an img element. If the attribute is present, its value must be the string "0". CSS should be used instead. Authors should not specify a language attribute on a script element. If the attribute is present, its value must be an ASCII case-insensitive match for the string "JavaScript" and either the type attribute must be omitted or its value must be an ASCII case-insensitive match for the string "text/javascript". The attribute should be entirely omitted instead (with the value "JavaScript", it has no effect), or replaced with use of the type attribute. Authors should not specify the name attribute on a elements. If the attribute is present, its value must not be the empty string and must neither be equal to the value of any of the IDs in the element's home subtree other than the element's own ID, if any, nor be equal to the value of any of the other name attributes on a elements in the element's home subtree. If this attribute is present and the element has an ID, then the attribute's value must be equal to the element's ID. In earlier versions of the language, this attribute was intended as a way to specify possible targets for fragment identifiers in URLs. The id attribute should be used instead.

Reader Jason Lucchesi send me in a neat demo of image captions sliding in overtop an image on rollover. The effect used a bunch of nested divs to get it done, so I thought I'd do my own version of it using the standard HTML5 structure for an image with a caption, and CSS3 it up.

Rich snippets (microdata, microformats, RDFa)

InfoWorld - One of the sly games that smart managers play is attaching their current project to a big, high-profile tar ball rolling down the hill, full of momentum. Now that HTML5 has become white hot after languishing for 10 years of relative disinterest, many ideas that began as cool enhancements for the Web are latching on to the bandwagon. They may be relatively independent projects, but because they involve JavaScript and HTML, they're now part of the HTML5 juggernaut.

Adding a hover state to an element

Click on an actual blog, then Settings >> Email & Mobile (Mobile Format of Blogs)