Digital Web just released the first part of a new two part article of mine entitled Seven Accessibility Mistakes .
In it I am listing mistakes I have encountered in the past (and done some of them) and give tips how to avoid them in the future.
Some of these tips might be utopic for you to achieve, but I for one am up for the challenge.
I’ll be moving to a newer, faster and better connected server soon, so there might be some downtime and hickups. I apologise profusely in advance.
I got asked to set this up as a proof of concept for an upcoming project, and it might be helpful to you guys, too:
Previewing collated form data with DOMscripting
The code is a bit wooly at the moment and I will clean it up and explain a bit more if I get the time.
In the meantime, just give it a swirl.
Google have released some statistics on web pages they have analysed:
In December 2005 we did an analysis of a sample of slightly over a billion documents, extracting information about popular class names, elements, attributes, and related metadata. The results we found are available below. We hope this is of use!
I would very much say so, so have a read about Google code webstats
Another Firefox extension I hadn’t known of earlier is Firebug which put together the best of JS console and the DOM inspector and even shows you your XMLhttpRequest data!
Following a thread on the evolt list about reading the next sibling element of a current element and making sure it really is an element and not a text node (line break), I decided to add a small helper object to my upcoming JavaScript book that takes care of some of these issues.
Give it a try: DOMhelp
My questions now are:
I promise to add a greeting, should you come up with something I
forgot or find out I did wrong. I don’t get many free copies though…
:-)
I am aware that there are a lot of libraries already out there, but
most of them are just too massive to use in a beginner book.