WCAG2ICT comment: deal with accessible non-web software against usability in general, take purpose & usage context into account

[This email has been submitted as a comment on the July 27, 2012 draft of "Applying WCAG 2.0 to Non-Web Information and Communications Technologies"]


In a number of scenarios it can be envisioned that accessibility and usability do not coincide, for example where a software sends out "information" to the user in a concurrent manner, possibly leading to information overflow which can only be kept at bay by reducing the amount of information and boiling it down to the most essential aspects. Thus for example, color, shape or blinking/movement could be used to steer attention to the currently most relevant information. It may be next to impossible to make that incarnation of that software accessible at the same time, and it may rather have to be rewritten (or another mode of operation may have to be implemented), to make it 'accessible' (but maybe not nice / efficient to use anymore for other users).  Typically it will have to be asked what kind of user is using the software for what purpose / tasks (does software that controls a nuclear power plant really have to be accessible?).

In a nutshell:
make the connection between accessibility and usability, and take usage context and purpose/tasks into account.


Olaf



-- 
Olaf Druemmer | Managing Director | callas software GmbH | Schoenhauser Allee 6/7 | 10119 Berlin 
Tel +49.30.4439031-0 | Fax +49.30.4416402 | o.druemmer@callassoftware.com | www.callassoftware.com
Amtsgericht Charlottenburg, HRB 59615 | Geschäftsführung: Olaf Drümmer, Ulrich Frotscher

Received on Wednesday, 5 September 2012 11:18:21 UTC