overview of Accessibility testing with an explanation of the WCAG numbering system. Features Earl Gray Cat.

1. Kristian McManus
Digital Accessibility Technical Analyst
IT Web Services
We Can Do It!
Accessibility Testing

2. 2
Kristian McManus
www.linkedin.com/in/kristianmcmanus
University of California San Francisco – UCSF
Digital Accessibility Technical Analyst
Kristian.McManus@ucsf.edu
digitalAccess.ucsf.edu
• Awareness
• Testing
• Training
• Support
About Me

3. 3
Accessibility refers to the inclusive practice of
removing barriers that prevent interaction with, or
access to websites, by people with disabilities.
When sites are correctly designed, developed and
edited, all users have equal access to information
and functionality.
https://tinyurl.com/uccandoit
Accessibility in this Context

4. 4
UC Policy IMT-1300
The University of California is committed to
supporting an information technology (IT)
environment that is accessible to all and in
particular to individuals with disabilities. To this
end, the University seeks to deploy information
technology that has been designed, developed, or
procured to be accessible to people with
disabilities.
It is also US Law and the right thing to do.
Accessibility is UC Policy

5. 5
Put CodeSniffer in your
bookmark bar and use it
on any web page.
CodeSniffer – Get your hands dirty

6. 6
Resources: tool picker, test page
Browser Extensions: aXe, Wave, SiteImprove
Bookmarklets: CodeSniffer, Totally, etc.
Online Tools: AccessLint, FAE
Many, many choices,
styles and formats
https://tinyurl.com/uccandoit
Free Automatic Testing Tools

7. 7
Web Content Accessibility Guidelines (WCAG)
are guidelines are produced by the World Wide
Web Consortium (W3C) and are the standard
means,
adopted and used to evaluate and guide
website accessibility.
 2.0 is the current version
 AA is the level UC follows
WCAG 2.0 AA and Why We Use It

8. 8
2.1.2 :four Principals
2.1.2 :twelve Guideline
2.1.2 :Success Criteria
(54)+ :97 Tests (yes/no question)
Examine:
WCAG (2.0 A) 2.1.2
WCAG - Three Segmented Number

9. 9
Operable, Keyboard Access with no
Keyboard Trap(s), passes by
answering yes to Question #54:
Is there a way to get in and out of
every component on the page (e.g.
widget or control) using only the
keyboard?
WCAG (2.0 A) 2.1.2 =

10. 10
Automatic
 Standardized and easily repeated
 Covers 20-30 percent of the rules
Manual
 Requires context and judgment
 Is slow, but precise
 Promotes greater understanding
https://tinyurl.com/uccandoit
Automatic and Manual Testing

11. 11
Purpose:
 Easily find and report, errors and warnings
 Locate errors and give guidance
 Aid manual checks
Warning:
 May have false positives
 Others use these tools to
rate and rank your site.
https://tinyurl.com/uccandoit
Automatic Testing Tools

12. 12
What cannot be machine tested:
 Keyboard operable: tab around (no mouse)
 Accuracy of alt text in context
 Confusing, busy, inconsistent
 Accurate Captions
 Visual Hierarchy
 Zoom
 BYOT – bring your
own tests
https://tinyurl.com/uccandoit
Manual Testing

13. 13
WCAG 2.0 A 1.2.2
Perceivable / Time-based media / Captions
#19 - Does the captioning accurately describe the
prerecorded video (dialogue and important
sounds)?
Manually Check a Video

14. 14
Hands-on: Play with the Tools

15. 15
Tools:
 PAVE – PDF cloud service
 Grammarly – free and paid
versions
 Accessibility Checker – for
WYSIWYG editors
 MS Accessibility Tools
https://tinyurl.com/uccandoit
Find, Fix, and Learn Tools

16. 16
Consider:
 Results will be used for: demo,
find and fix, reporting,
monitoring?
 What is the purpose, features,
and tasks of website/page?
 Are you doing a page sampling
or whole site?
 What else could you include
while you are at it: branding,
grammar check?
Prepare to Test

17. 17
Hands-on:
There are 18
accessibility
errors on this
page. Use
any tool and
find as many
as you can.
https://www.washin
gton.edu/accessco
mputing/AU/
Automatic and Manual Testing

18. Correctly Captioned Earl
the Gray Cat says Thank
you