The long-awaited updated to this popular Firefox add-on has just been released, after almost a year in development, while the new Opera extension was released a few weeks ago, to exclusively-positive reviews.

The Firefox version has a huge number of bug-fixes and improvements, most notably a fix for the spider's tendency to hang while scanning some sites, and a ten-fold increase in scanning speed -- so on average, it can now scan five pages per second, where before it would take up to two seconds per page.

The Opera version is forked from the same core codebase, for parsing stylesheets and scanning pages, but its interface had to be completely re-designed to suit the capabilities of Opera's API. It's just as fast and just as solid as the new Firefox version, and brings this useful tool to all who have Opera as their browser of choice.

I'll be publishing my slides, and most of the demos I presented, once the audio is available -- I have an idea to use HTML5 <audio> to embed it into the slideshow (which was written in HTML and CSS and presented with Opera in full-screen mode), then add a bunch of synchronisation events so it automatically steps-through the slides at the appropriate points in the audio. :-) (It will of course work in browsers other than Opera, as it's relatively simple to script and extend basic pagination display and control; so simple in fact, I wonder why more browsers don't do this?).

I'll be speaking on the subject of Accesibility in Modern Interfaces:

Though the web has evolved a great deal in the last decade, the most basic aspects of accessible development have hardly changed at all. So to kick-off my talk, I'll be looking at accessible techniques which have stood the test of time, being just as important today as they were a decade ago.

But the web is continually changing, and web-accessibility has had to change with it. To continue my talk, I'll examine in-depth the most-recent developments in this area, focusing mainly on WAI ARIA — the standard for Accessible Rich Internet Applications, which makes it possible to build custom widgets, like sliders, or drag and drop interfaces, that are accesible to screenreaders and other access technologies.

Then to finish, I'll be asking: how do we pass-on our understanding of the needs and purpose of accessibility to the rest of our development team, to make sure it's treated as a core-requirement and not just bolted-on afterwards? And how do we make sure we remember ourselves, and not get distracted by the coolness of the latest shiny stuff!

But I'm just one among many!

Covering a fascinating and diverse range of subjects, I'll be joined at the podium by some of the web's brightest lights — none other than Steve Marshall, Mike Rundle, Remy Sharp, Rachel Andrew, Jack Osborne, and the irrepressible Christian Heilmann.