With (standards-compliant) browser innovation firmly back on the agenda, there’s a lot of exciting new technology to get to grips with. This week, Google have thrown their weight firmly behind HTML5, while a new start-up aims to bring web fonts to all.
I’m at home with the flu at the moment, so taking the opportunity to un-star some items in Google Reader; this post is a link-dump with a little added comment.
A few of them have been in my favourites for a couple of months, so apologies if you’ve seen them already.
WAI-ARIA is a relatively new standard from the W3C, which provides semantic information to assisted screen reading technology. It’s fairly rapidly being adopted by browser makers and should become a part of your mark-up toolkit.
As well as being good for accessibility, it’s also useful to provide hooks for CSS and Javascript. Here are a just a couple of quick ways to get started using it.
Mozilla recently launched a very early version of Bespin, their online IDE (Sitepoint have a nice overview). It’s hard to make too much of it at this early stage, although it is impressively fast and responsive; time will tell if that continues to be the case as new features are added.
This responsiveness seems to come from the front end being created using JavaScript (only 62kb compressed, apparently) and the HTML5 canvas element (update: more on that implementation). Seeing other examples of what its capable of, I really need to start learning more about canvas.
To great fanfare, The Queen, in the company of Sir Tim Berners-Lee, unveiled the new British Monarchy website today. Unfortunately, what they unveiled was a real dog’s dinner.
Royal.gov.uk highlights the worst elements of the practice of web development; on only the second page I visited it became obvious that the site hasn’t been tested on any browser other than Internet Explorer, and a peek at the source code left me shocked.
A mistake which seems to be fairly common when taking the first steps in learning about Microformats (and one which I have made) is to presume that the markup which is generated by the generation tools – for example, the hCard Creator – is the markup that must be used in the page.
That’s not the case, of course; with a few notable exceptions, the markup is completely customisable, and it is the order of the class names (and other attributes) which matters.