For a little over two hours, now, Yahoo! Mail has been unavailable to its users (yes, all 8 of us). I saw reports this morning that Flickr (another Yahoo! property) was down intermittently, as well.
Has anyone seen any official reports as to what might be causing the issues? Is Yahoo! under some sort of attack? Are the throngs of people transferring their bookmarks from Delicious bogging down Yahoo!’s servers? Are you experiencing any problems trying to access any of Yahoo!’s other properties?
There’s been a lot of talk about HTML5 and all of the new elements it introduces. Forms will be built and used completely differently, the structure of documents will be much more semantic, and new features will be available to website and application developers.
But, what are these semantic elements? Are they really anything new? Will they change the structure of your document at all? The simple answer is “no”. The new elements, for the most part, just make your documents easier to parse and understand (for machines and for people using assistive technology). Very few of the new elements are really all that new; they’re just the same old elements with new names for new purposes.
As more and more browsers begin to support HTML5 and its elements, one of the nice things we can all begin using is the <figcaption> tag. When coupled together with the new <figure> tag, the <figcaption> tag semantically connects a caption with an illustration (not necessarily an image illustration; it can be a text illustration).
For the past few weeks, I have been using ChromeDeck (the native Tweetdeck application for the Google Chrome browser) fairly exclusively as my desktop Twitter client. I am very pleased with the application, and am extremely impressed at how similar the appearance is to the desktop app. There are a lot of neat features that you won’t find in the full-fledged desktop version; but there are also a few features I used regularly in the AIR application that I sorely miss in the Chrome version.
In an age where user feedback and interaction has become so popular, accessible forms have become that much more important. Many sites have already embraced making their forms accessible, and done a pretty good job of it, but inevitably some will still lack that little extra something – as small as an inappropriately named label through to no accessible features at all.
1. Using label tags
Labels should always be used and include the for attribute (e.g. <label for="name">). The value used should match the id of the input field that the label is being used for: