1.
Web Accessibility Best Practices
For People With Deafblindness
creating an inclusive digital world
intopia.digital intopia
Andrew Arch
Principal Consultant
amja
Sarah Pulis
Director
sarahtp

2.
We’re creating an
inclusive digital world
(from down under!)
We help organisations be more inclusive
and accessible.
Together, we create enjoyable, efficient
digital experiences for everyone.
Let’s go on an accessibility adventure
together.

3.
Thursday morning’s panel session #1
• ‘nothing about us without us’
• Many of our clients are bringing in people with disability
for user research and usability testing
• Things not working for you? Let the company know!
• Suggestions on W3C site at http://bit.ly/2N39CKD

4.
Thursday morning’s panel session #2
• Developers need to do the right thing
• We’re increasingly being asked for design and developer
workshops on accessibility
• Apps need accessible frameworks to develop in
• React has good accessibility – up to developers to use it

5.
Outcomes from today
1. Gather feedback to help improve the international
standard for digital accessibility
• Intopia is a World Wide Web Consortium member
• Intopia is on Web Accessibility Initiative working groups
2. Intopia also works with many organisations to help
them improve their digital accessibility
• Use this feedback to improve clients websites

6.
Web Accessibility
• means that people with disabilities can use the Web
• means that people with disabilities can perceive,
understand, navigate, and interact with the Web, and
that they can contribute to the Web
• also benefits others, including older people with
changing abilities due to aging

7.
Web Content Accessibility Guidelines
(WCAG)
• WCAG is a set of guidelines for improving digital
accessibility
• WCAG is referenced either directly or indirectly by
most countries with Disability Discrimination
legislation

8.
WCAG history lesson
• WCAG 1.0 published in 1998
• WCAG 2.0 published in 2008
• WCAG 2.1 published in 2018
• Extended WCAG 2.0 with additional criteria for low vision,
mobile users and cognitive impairments

9.
WCAG 2 framework
WCAG 2
Perceivable
Text
Alternatives
Time-based
Media
Adaptable
Distinguish-
able
Operable
Keyboard
Accessible
Enough
Time
Seizures
Input
Modalities
Navigable
Understandable
Readable
Predictable
Input
Assistance
Robust
Compatible
Principles
Guidelines
Success
Criteria
A: 
AA: 
AAA:

10.
WCAG and deafblindness
Specifically, some will be helped by:
• The requirements for low vision
• The requirements for blindness/screen readers
• The requirements for deafness

11.
Additional help from WCAG
• Good document structure such as headings
• Good labels and instructions for forms
• Clear links
• Consistent navigation and functionality
• Visible keyboard focus
• Text reflows when size is increased
• Timing adjustable

12.
Is
everything
good
then?

13.
WCAG sometimes fails for
deafblindness #1
CAPTCHA fails

14.
WCAG sometimes fails for
deafblindness #2
Video requirements can fail
Some people will not be able to access
• Captions
• Audio description
• Sign language
Transcripts may provide universal access but is not a
requirement at Level AA, only at Level AAA

15.
WCAG sometimes fails for
deafblindness #3
Contrast requirements can fail
• Minimum text contrast is 4.5:1
• Enhanced text contrast is 7:1
• Non-text contrast is 3:1
However, most organisations only implement Level AA
requirements.

16.
WCAG sometimes fails for
deafblindness #4
Language used can be difficult to understand or translate
• Unusual words or language
• Abbreviations and acronyms
• Reading level
Unfortunately all these criteria are Level AAA

17.
Other requirements for deafblind
Issue of combinations of disabilities need to be considered!
What else would make it easier for deafblind people to use
• the web
• mobile apps
• access digital services

18.
Let’s continue the conversation
Intopia
amja
andrew@intopia.digital
creating an inclusive digital world
intopia.digital