Some years ago, I wrote a presentation about how to recognise accessibility issues. To really make people understand the difficulties that some users face, I built a simulator. Since then, the simulator has been used in a handful of teaching sessions by various tutors around the world. Check it out for yourself and get a …
Apps, websites and other softwares should be available to everyone regardless of their abilities; a system should work equally well for a sighted person using a standard mouse and screen, as it should for a blind person using a Braille output or screen reader. There are other issues too; audio cues won’t work for deaf people, features that …
I’ve been doing some accessibility testing recently and came across WebbIE 3 If you’re testing against visual impairments then it’s worth checking WebbIE 3 out. In their own words: “WebbIE re-presents the information from a web page in an accessible format suitable for a screen reader.” Basically, this browser will strip pages down to just the content …
Hick’s Law states that the time is take to make a decision increases as the number of choices increases. If you give your user too many options then you site or application may become too time-consuming to be of use.
This is fairly obvious; the simpler you make something, the easier it will be to use. If you think about a car remote locking control, it only has one button – to turn on and turn off the locking system. Simple = easy to use. Now picture one of those programmable universal TV/Hi-Fi/DVD/etc. remote controls …
Accessibility shouldn’t be a concession. As you design your next site you should be trying to make sure that all content is available to all ranges of abilities without resorting to secondary content streams – you shouldn’t need alternate content for people with different abilities; the original content should be able to support all abilities