A comprehensive guide to improving accessibility for people with visual impairments.
According to the World Health Organization, an estimated 253 million people live with vision impairment across the globe. 36 million are blind and 217 million have moderate to severe vision impairment.
As of 2014, there are around 360,000 people registered as blind or partially sighted in the UK. But these are just the people who are registered. According to the RNIB the figure doesn’t take into account, “those who are waiting for treatment, those whose sight could be improved, those who have not registered for whatever reason and people whose sight loss is not at a level that allows them to register.”
RNIB estimates that a truer figure is roughly two million people living with significant sight loss in the UK.
These are some of the realities of people living with sight loss in the modern world:
However, advancements in web-related technology has opened up the world to blind and partially sighted people in a positive away, and can help them feel more connected to friends, family and services across the world.
As Paul Johnson’s interview with blind internet user Sunil Peck, who grew up in the pre-internet era, reveals, “The arrival of the internet was (even more) profound for those with visual impairments. [Sunil] explained “it was thanks to the internet that at the age of 25 I read my first newspaper.” At the time things we took for granted were just not available to the blind.”
For 3% of the UK, navigating the online world has it’s own specific set of issues that arise not just because of bad design, but also thoughtless design. We can do our best to avoid building a website with poor navigation and confusing menus, but how many of us forget to add alt-text to images, or even make them vaguely readable?
This article is intended to walk you through the various ways you can ensure your own website is as accessible as possible for people with visual impairments.
It’s an investigative piece, drawing information from numerous sources and opinions, that won’t necessarily get overly technical – but I will point to resources where you can find out more. It will also tackle various levels of vision ability, including colour blindness.
In November 2016, Gov.uk published the results of their assistive technology survey, in which the Government Digital Service asked 712 users about what devices, web browsers and assistive technology they used to access GOV.UK.
These are the results:
According to the survey, 30% of users told Gov.uk that they use a screen magnifier, which is a piece of software that enlarges and enhances anything users are reading and interacting. 38% of those magnifiers also have screen reader capabilities, with ZoomText being the most commonly used in both categories. Other popular screen magnifiers included Supernova and MAGic.
Almost the same percentage of respondents accessed GOV.UK with a screen reader. A screen reader is described by Gov.uk as an application that turns on-screen content into speech or shows it on a Braille display. Most screen readers are made up of two things: the screen reader software, and a Text To Speech (TTS) engine, which is what converts the text from the screen reader into speech.
The most commonly used is JAWS, (or Job Access With Speech). This is followed by VoiceOver, a feature for Apple products that gives, “auditory descriptions of each onscreen element and provides helpful hints along the way — whether you prefer using gestures, a keyboard or a braille display.”
Here’s computer programmer Austin Seraphin, who has been blind since birth, on the iPhone’s VoiceOver feature and how it impacted his life.
The next popular option is NVDA (NonVisual Desktop Access), a free and open-source software that you can download or transfer to a USB stick so you can use it with any computer.
Another interesting takeaway from the survey is that despite the worldwide dominance of Google Chrome (54% market share, with the next popular being Safari with 14%) this isn’t translating to users with assistive technology.
In fact the most common browser and assistive technology combinations are:
This is a rather complex snapshot of how blind and visually impaired people are accessing the internet. And although it should be noted that this is a survey of people who specifically use the Gov.uk website, it should reveal the range of options available and the way they can be configured to best improve accessibility.
So how can you improve the accessibility of your own website for people visiting your website using this range of assistive technology?
I talked to Andreas Savva, an accessibility consultant at a leading charity, and asked his advice…
Andreas: What I suggest is that developers and designers should know their audience, and that includes people with a variety of abilities and disabilities. Accessibility should not be considered at the end of the development process, often the last ‘check’, but incorporated through the design and development process of the website/product.
There are guidelines (WCAG 2.0) that can help designers and developers to create accessible websites. Also, the WAI-ARIA Authoring Practices 1.1 (working draft) provide a comprehensive documentation of design patterns that can be used to create accessible website ‘components’.
However, that does not necessarily mean a website that conforms to the guidelines will be easy to use by people with disabilities. It is important to include people with disabilities during the evaluation process to ensure that a website/product is easy to use.
Andreas: Here are some of the more frequent problems found by blind users:
We often find that the problems reported by blind and partially sighted people differ a lot.
Andreas: There are a few approaches that can be used to avoid problems for people with colour blindness on the web.
The same principles that apply to writing clear and concise copy for the web also apply to writing content that can easily be translated by a screen reader.
Gov.uk offers a breakdown of how screen readers respond to content, which is important to keep in mind and is definitely worth taking the time to read.
Basically it reiterates how the English language is a complex beast even at the best of times. We have plenty of words that are spelled the same but sound different: we tie a “bow” or take a “bow”, we pronounce the acronym of Value Added Tax as “VAT” and “vat.”
But any good screen reader should be customisable enough to work in most effective way for the individual user. Some include dictionaries where you can change the way a word is pronounced, or add pronunciations for new words.
As Gov.uk points out though, the more you make your content accessible for people with visual impairments, the less accessible you may be making it for other people. You can add spaces between letters like “V A T” to make it more screen reader friendly but it will make things difficult for sighted people to read, especially if they have low literacy or find reading difficult due to dyslexia.
Here’s the major takeaway from Gov.uk’s advice on the subject:
“Don’t write content that works specifically for screen readers, write content that works well for everyone. Use correct punctuation, spelling and grammar, use standard conventions for acronyms and abbreviations, and use words that are appropriate for your audience.”
Gov.uk decided to test the efficiency of 10 free automated testing tools earlier this year by building the “world’s least accessible webpage” complete with 143 accessibility failures grouped into 19 categories.
Here it is in all its glory:
According to Gov.uk the page contains such common failures as images without alt-text, blank link text, flashing content that doesn’t carry a warning and overly complicated language.
Here are the results:
For the most effective accessibility testing, Gov.uk advises you to, “Think of a testing tool as like using a spellchecker. It can certainly help you pick up issues, but it should never be used in isolation.”
The only way you can be sure that you’re picking up every accessibility issue is by combining automated tools with manual checking and user testing.