Auditing Your Site for Accessibility: Now What?

A presentation at North Bay Python in November 2018 in Petaluma, CA, USA by Zach Passen

Slide 1

Auditing your site for accessibility: now what?

Slide 2

Caveats

Slide 3

1: Identify

Slide 4

Screenshot of 2017 PyOhio site

Slide 5

Screenshot of 2018 PyOhio site, circa June

Slide 6

1: Identify

Quick and easy method browser extensions

WAVE
aXe
Lighthouse

Slide 7

Automation can only catch about 1/3 of potential accessibility issues

Slide 8

2: Verify

Slide 9

2: Verify

What kinds of manual tests can we do?

Keyboard
Screen reader
Browser zoom
Touch devices

Slide 10

3: Plan

Slide 11

3: Plan

Many small changes? Organize by page or flow

Many large changes? Incremental updates (long-term feature branch)

Slide 12

3: Plan

Set goals per release

Percentage or numeric value of defects closed
No regressions in a particular area
1+ new thing learned per feature

Slide 13

Screenshot of site_base_onecolumn.html highlighting {% block body %}

Slide 14

Screenshot of site.js will all functions collapsed to highlight file length

Slide 15

Screenshot of site.js:handleHomeAlert() (showing short function)

Slide 16

Screenshot of site.js:handleSignupErrors() (showing long function)

Slide 17

Screenshot of site.js:handleSignupErrors(), with everything blurred except the comment describing the function

Slide 18

Screenshot of site.js:handleCommonTalkDataForm() (showing long but more direct function)

Slide 19

4: Due diligence

Slide 20

4: Due Diligence

Keep fixing
Keep testing
Future proofing

Slide 21

4: Due Diligence

Pa11y http://pa11y.org

Slide 22

Resources

WAVE https://wave.webaim.org/about

Slide 23

Resources

aXe https://www.deque.com/axe/

Slide 24

Resources

Lighthouse https://developers.google.com/web/tools/lighthouse/

Slide 25

Resources

Pa11y http://pa11y.org

Slide 26

🎉