Presentation to technologists at UNC-Chapel Hill, Nov. 3, 2017

1. Web accessibility in action
Bringing online experiences to all people
Phil Daquila
pdaquila@unc.edu
Nov 2017

6. JUSTIFYING
ACCESSIBILITY
1. Staying ahead
of the law
2. Business
survival
3. Improving lives
through
inclusiveness

7. IMPORTANCE OF A11Y
> What it is, who it affects
> aka #a11y
> AT = assistive technologies
> Commitment here at UNC
> Shift thinking from making tech accessible to
enabling people

8. I ordered my Amazon Echo to add
'accessibility presentation' to my
calendar and sync it with Google
This is what
Alexa heard . . .

9. RANGE OF DISABILITIES
> Up to 20% of all people ➡ more than 1 billion
> Increases with age
> Huge range: congenital, disease, trauma, temp
> Most challenging to least:
1 Visual
2 Dexterity
3 Hearing
4 Language/Speech
5 Cognitive
6 Social davidberman.com

10. LEGAL BACKGROUND
> ADA Title III (1990/2008), "public accomodation"
> Lawsuits on the rise
> Uncertainty in courts
> Gil v. Winn-Dixie Stores, Inc. (June 2017)
> WCAG success criteria widely accepted
> Better to act now than to pay later

11. LEGAL BACKGROUND
> Rehab Act of 1973, Section 508 ICT (2001)
> Section 504 and financial assistance from US DOE
> OCR at DOE enforces law, fields complaints
> Major efforts to integrate common in higher ed
> Link in UNC toolbar

12. GOOD NEWS
> Well-documented solutions
> Achieved mostly via HTML & CSS
> WordPress building it into core https://make.wordpress.org/accessibility/
> Many free online tools https://www.w3.org/WAI/ER/tools/
> Shoot for 'readily achievable' gains
+ longer strategy

13. GUIDELINES
> WCAG 2.0 AA from W3C https://www.w3.org/WAI/WCAG20/quickref/
1. Success Criteria: must, should, could
2. Techniques
> Solutions = automated tests + manual fixes
QUICK REF

14. TOOLS FOR TESTING
1. Chrome DevTools
2. tota11y
3. Siteimprove
4. aXe
5. FAE
6. AChecker
7. ChromeVox

15. AREAS FOR TESTING
1. Document structure and headings
2. Text alternatives to non-text items
3. Color contrast
4. Links
5. Video/audio captions and transcripts

16. AREAS FOR TESTING
Excluded from this talk (but equally important):
1. Forms and input labels
2. Tables
3. Landmarks
4. Content!

17. MANUAL TESTING
1. Tab key navigation test
2. Select-all test
3. Code examination and review
4. Media review (video/audio)

18. DIGITAL SERVICES′ EFFORTS
> Training selves and professional development
> Making improvements to existing sites
> Accessibility-first approach to development
> Offering consultation with customers and our
UNC Creative partners
> Future: Clinics for all website owners

19. CUSTOMERS
> ITS, Digital Services, Web-Dot, Help
> Creative, Identity
> Diversity, EOC, HR
> Privacy, Teaching & Learning
> Our themes
AFTERBEFORE

21. INVOLVING USERS IN
ACCESSIBILTY TESTING

22. ACTUAL USERS
Amanda
> SILS grad student, 22
> blind since 5
> yellow lab Keith
> Binghamton, NY
> JAWS screen reader

23. ACTUAL USERS
Demi
> MPH grad student, 25
> muscular dystrophy
> planned U of Alabama disability symposium
> wheelchair
> MBP, mouse, keyboard overlay
VIDEO

24. ACTUAL USERS
John
> retired professor, 73
> macular degeneration
> authored several history books
> JAWS screen reader on desktop
> magnifying glass

25. STEPS TO TAKE NOW
1. Speak to your developer
2. Add testing tools to your workflow
3. Fix any glaring problems
4. Make new content accessible from the start
5. Find real users to test your pages
6. Post your a11y statement and stick to it
BONUS
Budget lots
of time for
study

26. I am here to help.
Please feel free to ask.