Skip over navigation

Restore visual elements.

 

 

 

 

TechDis logo


Valid XHTML 1.0 Strict

 


Warning: mysql_connect() [function.mysql-connect]: Unknown MySQL server host 'www.onebluessssdog.co.uk' (1) in /var/www/techdis.org.uk/httpdocs/connection.php on line 3

Warning: mysql_connect() [function.mysql-connect]: Unknown MySQL server host 'www.onebluessssdog.co.uk' (1) in /var/www/techdis.org.uk/httpdocs/connection.php on line 3

Buttons, bells and whistles: Accessibility criteria when purchasing mobile devices


This article – written by JISC TechDis to support MoleNet projects – is designed to help project managers take accessibility into account when deciding between alternative devices to support their projects. The article looks first at the issues of interface accessibility and then takes a broader look at questions to ask when weighing up possible purchases. Inevitably compromises need to be made between conflicting criteria and these are discussed objectively before summarising with four key conclusions.

Key things to look for in terms of interface accessibility

Buttons

Look for buttons that:

Keys

Where you are expecting learners to input text or numbers via a keyboard there is an immediate correlation between device size and keyboard size. Many of the points in the section on buttons also apply to keys but two critical points include:

Screen

For most users the following are important – all the more so if the user has visual difficulties or dyslexia:
Regarding font size and colour, this is may be adjustable at the level of the operating system, or at software level. Alternatively you may be able to get third party software that allows the changes you require – for example freeware for the Palm system will allow personalisation of colours on most Palm programs and menus.

Navigation process

For most devices the navigation system is critical to usability and accessibility. Questions to ask include:

Power

Power management is critical to usability and may also impact on accessibility if a disabled learner is relying on additional software (such as text to speech) with consequential power drains. Power criteria include:

Suggested criteria to take into account when weighing up alternative purchases

It is recognised that accessibility is one of many factors that have to be weighed up. Whilst there is no legal imperative to make accessibility the only purchasing criteria it would be foolhardy – given the legal entitlements of disabled learners - for it not to have formed a demonstrable part of your purchasing decision; even if you ended up opting for a less accessible solution in the final reckoning. Suggested criteria to take into account include:
Accessibility is not something that lends itself to rules, regulations and simple checklists. Like all aspects of teaching it is multi-dimensional and needs intelligent debate and consideration. But ignoring it is not an option and somewhere in your project documentation you should capture the accessibility issues you considered and the decisions you made. There are many cases of institutions settling out of court with disgruntled disabled learners. In most cases the issue was simply that the provision was inadequate, the policies unclear and anticipation non-existent. If the policies and anticipation are sound, the provision should be better and the legal resilience will be significantly enhanced.

Conclusions