Out-Law Guide 3 min. read
09 Aug 2007, 9:35 am
The unique requirements for motor impaired web users can often be overlooked or poorly implemented. Motor impairments can be caused by a stroke, Parkinson's disease, Multiple Sclerosis (MS), a physical disability or even a broken arm. This group of users essentially have limited or no ability to use a mouse.
Wherever possible (and appropriate) expand the width and/or height of the clickable area. This will greatly aid motor impaired users that are able to use a mouse but with limited mobility. Ways of achieving this include:
display: blockto each link in a vertical list, the full width of the column becomes clickable (as opposed to just the text itself). You'll need to assign a width or height to the link for this to work properly in Internet Explorer.
Assigning a background colour to focused links is probably the most important thing you can do for keyboard-only users tabbing through web pages. When users tab on to any one link this background colour will display, clearly highlighting where the user is.
If your website doesn't provide this focus state then it can be difficult for keyboard-only users to orientate themselves on pages. A focus state for links can be easily achieved with basic CSS commands. For such a simple implementation it's amazing how few websites actually offer this.
'Skip to content' links have historically targeted screen reader users, yet are also useful for motor impaired users. A skip link is an invisible link that allows screen reader users to jump over the navigation on each page and get straight to the main content.
Skip links are very useful for keyboard-only users but only if they're made visible when focused on (otherwise how will they know the link exists?).
Some motor impaired web users utilise voice recognition software to navigate through web pages. If pages on your website start to play audio without users knowing about this in advance then this can severely conflict with the voice recognition software.
There's nothing wrong with using audio but do make sure that it doesn't start by default when users arrive at the page. Instead, provide a link/button that users can select to start the audio.
Keyboard-only users tab through links and form items in the order in which they're placed in the HTML source code. The default tabbing order is usually perfectly logical so doesn't need changing.
tabindex attribute can be used to change the on-page tabbing order but is rarely necessary. Items with the
tabindex attribute assigned to them get tabbed to first in order of hierarchy, regardless of their position in the HTML source code.
The only logical reason to change the tab order is if 95%+ of users go straight to one particular item on the page (e.g. a search form). Making this the first item users tab to would make perfect sense.
You can assign access keys to any links or form items so as to provide keyboard shortcuts to them. The problem with access keys is there's no convention so the few sites that use them do so in whichever way they choose. Site visitors are unlikely to spend the time getting accustomed to your website's particular access keys.
For example, you could assign the access key, 'h', to the home link. PC users can then simply press ctrl+h (Mac users press alt+h) followed by enter to access the home link. Another website may assign the access key, '1', to the home link; another website may use 'o' (say if 'h' is being used for the help link) and so on.
Access keys can also override keyboard shortcuts for screen readers.
This article was written by Trenton Moss. Trenton's crazy about web usability and accessibility – so crazy that he went and started his own usability and accessibility consultancy, Webcredible, to help make the Internet a better place for everyone. He can often be found carrying out an accessibility audit and spends much of his time working on the world's most accessible CMS.