1: Identify

Quick and easy method browser extensions

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

2: Verify

What kinds of manual tests can we do?

3: Plan

Many small changes? Organize by page or flow

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

3: Plan

Set goals per release

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

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

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

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

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

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

4: Due diligence

Pa11y http://pa11y.org

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

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

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

Pa11y http://pa11y.org

🎉

Auditing your site for accessibility: now what?