Slide 1
Slide 1 text
Sarah Barrett @documentalope
http://bit.ly/inclusiveIA
IA as inclusive design
BUILD A (BETTER)
WORLD
Slide 2
Slide 2 text
Accessibility is important.
Slide 3
Slide 3 text
Accessibility can feel fraught,
and that’s okay.
Slide 4
Slide 4 text
>700 lawsuits in the US in 2017
over inaccessible websites.
ADA Title III 2017 Report
Slide 5
Slide 5 text
15% of people have a disability.
WHO World report on accessibility
Slide 6
Slide 6 text
Only 0.02% of our visitors use IE6 - 8.
Slide 7
Slide 7 text
Supporting legacy browsers increases
development time by at least 30%.
We do it all the time.
But The Client Wants IE 6 Support!
Slide 8
Slide 8 text
Anne Gibson’s “An Alphabet of Accessibility” (PDF)
It’s the right thing to do.
Slide 9
Slide 9 text
Microsoft Inclusive Design resources
Inclusive design is the method.
Accessibility is an outcome.
Slide 10
Slide 10 text
Accessibility is important.
Slide 11
Slide 11 text
Accessibility is important
for other people.
Slide 12
Slide 12 text
Bad news:
IA is an accessibility problem.
Slide 13
Slide 13 text
Broad, shallow navigation
performs better in general.
Hochheiser - Revisiting breadth vs. depth in menu structures for blind users of screen readers
Slide 14
Slide 14 text
Blind users need 8x as long to
accomplish a task when navigation
is deep.
Nogueira et al - Comparing sighted and blind users task performance in responsive and non-
responsive web design
Slide 15
Slide 15 text
Half the problems encountered by
dyslexic users are IA problems.
Freire - Empirical results from an evaluation of the accessibility of websites by dyslexic users
Slide 16
Slide 16 text
Common IA issues are barriers to
access.
Ramakrishnan – “Non-visual web browsing: Beyond web accessibility"
Bigham – “The effects of ’not knowing what you don’t know’ on web accessibility for blind web
users (PDF)
Lazar – What frustrates screen reader users on the web: A study of 100 blind users (PDF)
Slide 17
Slide 17 text
Good news:
Accessibility is an IA problem.
Slide 18
Slide 18 text
No content
Slide 19
Slide 19 text
Simple, if not always easy:
“Provide captions for all
prerecorded media.”
WCAG 2.1 guideline for captions
Slide 20
Slide 20 text
Complex, strategic IA task:
“When the sequence in which content is
presented affects its meaning, a correct
reading sequence can be
programmatically determined.”
WCAG 2.1 guideline for meaningful sequence
Slide 21
Slide 21 text
Adherence to standards is a poor
predictor of usability.
Power - Guidelines are only half of the story: accessibility problems encountered by blind users
on the web
Freire - Empirical results from an evaluation of the accessibility of websites by dyslexic users
Slide 22
Slide 22 text
Automated tools can check against
30% of standards.
Pa11y
Slide 23
Slide 23 text
Frameworks help, they don’t do it
for you.
Ethan Marcotte - Accessibility is not a feature
Slide 24
Slide 24 text
Include people with access needs
in your research, but also use what
we know.
The Value of Involving People with Disabilities in User Research
Running research sessions with people with disabilities
Tips For Conducting Usability Studies With Participants With Disabilities
Slide 25
Slide 25 text
4 challenges to be inclusive in your
IA:
Slide 26
Slide 26 text
Do the training your
developers do.
1.
(If you don’t have developers of your own, store-bought
is fine: Udacity - Web Accessibility )
Slide 27
Slide 27 text
Read the guidelines.
2.
WCAG guidelines explained part 1
WCAG guidelines explained part 2
Slide 28
Slide 28 text
Find one thing to add
to your IA artifacts.
3.
Slide 29
Slide 29 text
Practice saying, “This is
an accessibility issue.”
4.
Slide 30
Slide 30 text
Accessible IA is good IA.
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
No content
Slide 33
Slide 33 text
IA + Accessibility =
Better experiences for everyone
Slide 34
Slide 34 text
Thank you!
@documentalope
http://bit.ly/inclusiveIA