Calling all web developers….

I’ve just been asked this question from a web developer who identifies standard arguments against accessibility as including “too expensive, and takes too long for such a small percentage of users” He then goes onto ask if I’m aware of any kind of figure regarding users who have accessibility requirements when using a computer.

Here’s my reply.

There are some contentious and deep rooted issues here about attitudes to diversity and difference (too expensive, and takes too long for such a small percentage of users????) in a digital society in particular where government is moving towards ‘digital by default’ services underpinned with the perception that communication and information technologies save time and money. Digital divides are the inevitable result if design and delivery favours a narrow range of access criteria rather than principles of inclusive practice.

With regard to users of assistive technologies, no one knows how many there are – or would be – if it were less expensive and more supported – but here are some facts and figures:

  • There are around 11 million disabled adults in the UK, this includes limiting long standing illness. This is equivalent to 20 % of the population
  • 17% people are born with a physical, sensory or cognitive impairment – 83% acquire one in later life.
  • At 2009, there are over 6.9 million or 18.3% of working age people (one in five) who are disabled
  • There are about 2 million people in the UK with significant sight loss. There are an estimated 25,000 children with sight problems.
  • It is estimated that there are almost 9 million people with hearing impairment  http://www.papworth.org.uk/downloads/disabilityfactsandfigures2010_100202152740.pdf 
  • It is estimated that 130,000 people have a stroke in the UK each year, resulting @ 67,000 deaths leaving a potential of 63,000 people with a physical, sensory or cognitive impairment. http://www.thestrokesociety.com/
  • There are 10 million people (1 in 5) living with arthritis in the UK; arthritis can cause severe restriction of movement making it difficult to use a computer.   http://www.arthritiscare.org.uk
  • Then there are issues around learning disability. Acquired Brain Injury is the largest cause of disability amongst the working age population. There are about 1.5 million – nearly 3 in 100 – in the UK who have a learning disability. Just 1 in 3 people with a learning disability take part in some form of education or training. About 200 babies are born every week with a learning disability http://www.papworth.org.uk/downloads/disabilityfactsandfigures2010_100202152740.pdf 

These figures relate specifically to ‘disability’ but I think we need to take a broader view.  Inclusive design/accessibility is not only about ‘disability’; inclusion is about accepting the full range of human diversity with respect to ability, language, culture, gender and age. Society promotes increasingly digital lifestyles and ways of working and web developers are in the unique position of being able to make a real difference – we need to ensure that difference is about ensuring equitable digital access rather than being discriminatory.

exclusion by language…

I’ve been sent a link reporting on an Accessibility Hack Event at Birmingham. This is a great idea – put together the people who are interested in accessibility. We should do this at Lincoln. Here’s a few comments on the blog post.  

The affordances of digital data have never been utilised effectively – it’s the optimum opportunity for ensuring equality of digital access but too often the theory gets privileged over practice and the opening promotion video by GPII is typical:

e.g. user is recognised at public access point and now sees large print on ticket machine = one happy user  but…. magnified text requires increased screen size – other wise you need navigational devices which then mean all the information can’t be seen at once… another e.g…..back of seat monitor on aircraft customised to suit user preferences – you can hardly see (or hear) these in the first place – so increased text size is not going to assist…

The ratio between content and monitor size is so relevant but easily overlooked.  I’m working with someone with macular degeneration whose family have bought them a new widescreen Acer laptop all set up to display large tools and text. But email via Windows Live is almost unusable because the screen size doesn’t support the chosen display size. Sounds obvious but unless you’ve tried it….

The idea of providing accessibility rather than having to  adapt to a standard environment has long been a dream of Assistive Technology users. This is why I’m so interested in the idea of ‘intuitive digital data’ which knows how to adapt to the device being used or ideally can provide itself in the appropriate file format as requested – something I believe we are working towards.

A keynote speaker at the event was correct in saying accessibility should be a right for all, and whereas most people see accessibility as about disabled people, it is actually about everybody – then they spoiled it saying the aim is to deliver the best website that is ‘accessible to as many people as possible, a website that is accessible to everyone would just be text, which would be ugly’.

This second statement is both contradiction and backwards step – accessibility is not about as many people as possible – it’s about everyone full stop – and a website which is accessible to everyone does not have to be plain text – that’s the reason text-only alternatives were dropped. A fully accessible website can have pictures and multimedia and interactive forms – it just needs to include the information to be given in alternative formats,  and all content to be correctly and appropriately labeled for screen readers.

An Accessibility Hack Day is a great opportunity to bring people together to talk about important issues. It’s in the nature of digital exclusion to be invisible. But the key issue the blog post raised for me is how the language was indicative of the current cultural shift away from the social model of disability – which sees the external environment as disabling by not recognising and providing for a diversity of requirements (digital disability is an ideal example where we have the technology to ensure 100% access but all the barriers are economic, political etc) and back to the old medical model of disability which saw the reason for lack of participation as being caused by individual impairment – be that physical, sensory or cognitive. It’s concerning how the language of disability is changing with references to disabled people rather than people being disabled by society – you may think this is being pedantic – but it isn’t.

The GPII video says ‘those of us with disabilities often run into a situation where the technology doesn’t work well enough to meet our abilities’. Another presenter refers to ‘people who are severely disabled with motor neurone disease’  These are examples of language use which need to be challenged. The Social Model calls for disability to be seen as something imposed on individuals by society – motor neurone disease is an impairment – and to call someone disabled by it is an example of the old medical model in action. I worked with someone with motor neurone disease whose used a computer for years. But the disease is reducing ability to move fingers and keyboards are designed with the assumption that we will only hit one key at a time.  With a keyguard in place, the computer can be used again (although it means a laptop remains inaccessible). 

The solution lies first and foremost in the external environment where the limitations of the technology are the disabling factor. Subscribing to a social barriers model is an essential prerequisite to enabling independence and social participation – in particular with ensuriong digital inclusion.  Technology can be empowering but the problems begin when perceived solutions derive from the viewpoint of the technologist – not the user – we have to step outside of our world and into the life-world of other people in order to experience the barriers to know how best to help remove them.

Finally – the disclaimer at the end of the GPII video sort of says it all.

The contents however do not necessarily represent the policy of the funders and you should not assume endorsement by the federal government.  It would have been more encouraging if it had said Accessibility is the policy of the funders and you can assume endorsement!

lest we forget….

While protests are in the news there’s another – more invisible – coalition led disaster which is causing exclusion and distress on a daily basis. This is the government’s attitude towards people with sight loss who are struggling to operate in digital environments because of insufficient action to ensure digitally inclusive practice and accessible web design. As the government moves towards the online-only provision and management of welfare it’s doing nothing to challenge the increasingly visual nature of the Internet and digital designers assumptions of a narrow range of access criteria (i.e. everyone uses a Mouse, their Eyes and Ears – the MEE-Model). This is making it difficult to impossible for users of assistive technology, in particular screen readers, to have equity of digital access. At the same time it also ensures denial of participation in the public sphere where the platforms for debate and dissent are increasingly digital ones.

Digital discrimination is already a serious problem and will become even more critical as more services look to online provision believing it will increase efficiency and cut costs. Assumptions about access need to be challenged; not everyone can operate an out of the box laptop bought from a local supermarket or a high street retailer and the way in which the government is choosing to ignore this is an issue which needs to be made more public.