Register with Forum Nokia now and you'll enjoy the full benefits of the Forum Nokia membership.
Register LoginInnovation Series Videos highlighting Forum Nokia developers
Nokia releases new Qt developer offerings
Forum Nokia Developer Conference, India
Optimise your website for mobile devices with mobile web templates and layouts
Zoom and Rotate Gestures in FlashLite for touch-enabled devices
Jackson Feijó
Read more about Jackson on the Champions website.
Nokia Developer Days in South Africa
December 01, 2009
Johannesburg, South Africa
Forum Nokia Developer Conference ’09, India
December 07, 2009
Bangalore, India
LeWeb
December 09, 2009
Paris
Web Runtime Coding With Aptana WRT Plug-in
December 09, 2009
9am New York | 2pm London | 4pm Helsinki
Web Runtime Coding With Aptana WRT Plug-in
December 09, 2009
9:30am New Delhi, noon Beijing
It isn’t always enough just to make a product easy to use for the average user. About 18 percent* of the U.S. population is considered to have some sort of disability, so the “slice of the pie” is not necessarily small. Age—young or old—can also pose special accessibility demands. Like general usability, paying attention to accessibility can result in a major competitive advantage.
The most important information is amassed before the actual design and implementation begins. Base the entire product concept on verified user needs and requirements. When asked, users want many things, but often these things are not what they need to reach their goals. When making design and implementation decisions, remember that the point of the application is to allow users to reach their goals efficiently and smoothly.
When designing for accessibility, take these situations into account:
Visual impairment
- Avoid color combinations that are difficult for the color blind, such as red and green or blue and yellow. Test also in
black and white.
- Use clear visual elements with high contrast (dark symbols on light surface) that are sufficiently big.
- Do not rely on visual clues only. Mobile devices also have vibration and sound.
- Design text content so that a reader program will read them out correctly.
- Allow the user to change text and UI elements to a preferred size.
Hearing impairment
- Do not rely on sound alone. Use vibration and visual clues as well.
- Give users control over sound volume.
Motor disabilities
- Offer alternative methods of control in addition to the keypad. The elderly and people with motor disabilities may find
the keys on a mobile device difficult or impossible to use. Offer options like voice commands, touchscreen gestures, and even
moving the device itself.
Cognitive and other impairments
- Use clear and simple language that is familiar to the user. Avoid jargon.
- Do not rely on text alone getting the message across; the product may be used by someone who can’t read.