According to the Office for National Statistics, there are over 10 million disabled people in the UK, representing around 15% of the population. More than ever before, the need to deliver inclusive, accessible digital products and services constitutes both a moral and a commercial imperative. Accessible products ensure that people with disabilities, whether they are cognitive, physical, visual or auditory can interact, navigate and contribute to the web.
But that’s doesn’t really cover the whole picture. At some point in our lives we might all suffer from an impairment that will limit our abilities to interact with the world around us. This could be temporary or longer-term but as we grow older we are all likely to go through changes that will affect our sight, our hearing, and our overall mobility. We also need to consider the impact that poorly designed digital products and services can have on people’s confidence and independence. Rather than see it as a test before product release, accessibility should be built into your design and development approach from the start.
Chris will guide you through the various challenges and obstacles that commonly prevent users from engaging with digital services and show you some easy to implement accessibility principles that will help you ensure you are providing the best possible experience for the widest range of abilities.
After this session you will have a better appreciation of how you and your team can deliver fully inclusive solutions.
5. Everyone has challenges
► Disability is more common than you may imagine.
► We will all experience disability at some point.
► By the age of 45 most of us will need glasses
- glasses are considered as an assistive tech.
► Yet many websites do not support dynamic text.
► Many on iPhone use 'Large Text,' many apps are
still not compatible.
6. Acquiring a disability ≠
being born with a disability
► Molly was born deaf but sighted and then lost
vision.
► Molly is now registered blind however still rely on
the remaining vision I have left (5% in one eye)
► Many think if you are blind you use auditory tech
► Being born blind if different to being born sighted.
► Only 5% of blind people have no useful sight.
► The rest have some, however not completely
useful.
7. So, what is the best way to think about
designing for inclusion?
12. Vision
Ability to see, or
process visual
information
Hearing
Ability to hear, or
process acoustic
information
Motor
Ability to interact
with a device
accurately and
quickly
Cognitive
Ability in mentally
demanding areas;
reading, memory,
attention, complex
concepts or language
Types of impairment
13. Vision
Blindness,
low vision &
colour blindness
Hearing
Hearing loss
Motor
Dyspraxia,
RSI, arthritis
and
cerebral palsy
Cognitive
Down’s syndrome,
Asperger’s and
dyslexia, learning
difficulties
Types of impairment – long term
14. Vision
Forgot my glasses
Glare when using a
device in bright
sunlight
Hearing
Communication
within a noisy
environment
Motor
Temporary injury
such as a broken
wrist
Carrying a child
Cognitive
Medication,
Tiredness, Stress,
Hangover :D
Types of impairment – temporary & situational
34. Getting started
► Try to include users with inclusive needs in
your usability sessions (1 or 2 per session)
► People are people - focus on needs first
► Remember that not all users will self-
identify as having an inclusive/accessibility
need
► Not every blind person uses a screen
reader
► Understand the users personal needs.
Treat them how they want to be treated
(Space, Time)
38. Prepared by Sigma: Putting users at the heart of our
solutions delivers better products to a happier audience
www.wearesigma.com
Prepared by Sigma: Putting users at the heart of our
solutions delivers better products to a happier audience
www.wearesigma.com
Notas do Editor
Solution
- Provide 1mm inactive space around elements
- Balance enough information density and target ability of UI elements
- Standard touch size of 7-10mm
“There are many things you can do in the design phase to improve readability including…
Clear visual hierarchy
Good background contrast against the text
10 – 15 words per line
120 – 150% line height
Less likely to mis-spell
Sets exppectations
Allows for quick ‘Idea change’
On forms – using links to errors at the top of a form makes it easier for screen readers to find the errorError messages should be as explanatory as possible, telling users what they did wrong and how to fix the problem.
Link at the top of the form that goes directly to the errors is also good for screenreaders but it also makes it easier for those with cognitive impairments because the error is then easy to find
On forms – using links to errors at the top of a form makes it easier for screen readers to find the errorError messages should be as explanatory as possible, telling users what they did wrong and how to fix the problem.
Link at the top of the form that goes directly to the errors is also good for screenreaders but it also makes it easier for those with cognitive impairments because the error is then easy to find