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:
While WordPress implements a really nice asynchronous upload function, it doesn’t really offer any simple way to manipulate the files before they’re actually stored in your uploads folder. There are multiple filters you can hook into after the file’s been uploaded and processed; but there aren’t any filters available to do anything with the file beforehand.
By now, chances are pretty good that you’ve received at least one e-mail message from some company informing you that your personal data (specifically your e-mail address) has been compromised in some way, as a result of a data breach at Epsilon.
So far, I have only received notification from Target, but I’ve heard reports that data from Amazon, Best Buy, Chase, Citi and many more major corporate entities was compromised.
Apparently, Epsilon is responsible for distributing most of the e-mail communications sent out by many, many different major corporations, so, if you’re signed up on anyone’s e-mail list, chances are pretty good that your e-mail address was harvested from Epsilon. Following is the communique I received from Target today.
When developing a new WordPress theme, sometimes you might need to create optional widget areas within the template; that is, areas that can include widgets if the user wants, but don’t appear at all if the user has not added any widgets to that particular area.
For instance, some users of your theme might want to include a tag cloud above the footer; or maybe they want to include Google AdSense ads above the content. Other users of your theme might not want anything to appear in those areas, though.