» tagged pages
» logout

sorted by: recent | see : popular
Content Tagged with accessibility + usability

WAI-ARIA Overview

WAI-ARIA (Accessible Rich Internet Applications) defines a way to make Web content and Web applications more accessible to people with disabilities: dynamic content + advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies

W3C: Del.icio.us W3C Tags

Web Content Accessibility Guidelines 1.0

Web Content Accessibility Guidelines 1.0

W3C: Del.icio.us W3C Tags

W3C On The Relationship Between Usability And Accessibility

The W3C posted an update to the Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG), something which I (for some reason) don't remember seeing go by in January when they posted the initial draft.

W3C: Del.icio.us W3C Tags

That Checkbox Needs a Label

As a user of many web applications, I often find myself noticing little things that slow me down. One such thing is the use of checkboxes in web forms. It’s not the problem of checkboxes itself, it’s the face that checkboxes require the user to really focus their attention to a fairly small box on the page and perform a click inside. If you’re filling out a form really quickly, it’s almost guaranteed that you’ll take advantage of you your tab key to get through each field quickly. Sometimes there are select boxes, which require the user to make selections with their mouse. Checkboxes drive me crazy because it requires more time to position the cursor and move on.

So, when I see a form like this, I don’t see it being very quick to interact with.

While I’m not in love with the date selection interface here, my bigger pain has been the checkbox in the form. Why? Because they forgot to use the <label for=""> HTML tag.

What’s the problem? Well, I don’t have the convenience of clicking on the label text, which would toggle the corresponding checkbox.

I know, many of you know all about this… but I run into this problem everywhere. This is an accessibility issue for people and really just increases the chances for a frustrating user experience. When you use the label tag properly… it will provide a larger amount of the screen for people to click, which reduces the chance of not clicking in the right spot. The label tag was designed with this in mind so that people could click close enough to trigger the desired action.

Here is an example of where it becomes really useful.

So, the lesson? Please remember to use the label for tag. :-)


<input type="checkbox" id="remember_me" name="remember_me" value="true" />
<label for="remember_me">Remember info?</label>  

This is an easy thing to forget when building web applications. We’ve forgot and I’m sure you have too. I just wanted to point it out though because I see this happen so much… even in new sites.

Perhaps you run into similar problems with web applications that can be fixed with just a little more HTML. Care to share your experiences?

For more information, read Labeling form elements from the Dive Into Accessibility site.

Rails: Robby on Rails

Web Accessibility Evaluation Tools: Overview

Web accessibility evaluation tools are software programs or online services that help determine if a Web site meets accessibility guidelines. While Web accessibility evaluation tools can significantly reduce the time and effort to evaluate Web sites, no t

W3C: Del.icio.us W3C Tags

Page 1 | Next >>