Fitting accessibility into an agile development cycle can be challenging. Often accessibility specialists are spread thin across agile squads and they have to deliver quickly into multiple sprint cycles. To meet the demand I looked to Lean UX principles and developed The Lean Accessibility Audit Workshop (LAAW). LAAW has two goals 1) detect accessibility problems quickly and 2) spread the accessibility knowledge. This is accomplished by training members of agile squads on accessibility basics, evaluation methods and tools. The training evolves into an accessibility audit as squad members collaboratively capture, share and prioritize findings. The LAWW method compresses a 6-8 week evaluation process into a 2 weeks process while training squad members to detect and avoid accessibility issues in the future. And it can be pretty fun. This session will explain how to bring LAAW to your organization.

1. Dyslexia Task
Empathy Building
Visual Impairment Glasses Mobility TaskColor Blindness Simulation
These activities are not meant to simulate disabilities.
They provide a sliver of that experience to help us
understand how disabilities can affect the user experience

2. I Am the LAAW!
Lean Accessibility Audit Workshops
MIKE RYAN
#IAmTheLAAW
#UXPA2019
June 27, 2019
@ryaninteractive

3. LAAW
#IAmTheLAAW
Agenda
● Define the Problem
● LAAW (Lean Accessibility Audit Workshops)
1. Build Empathy
2. Define Web Accessibility
3. Detect Accessibility Issues
4. Prioritize Accessibility Issues
5. Design for Inclusivity
● Results and Tips

4. Define the
Problem
“If I were given an hour in which to do a problem
upon which my life depended, I would spend
40 minutes studying it,
15 minutes reviewing it and
5 minutes solving it.”
Albert Einstein
http://scienceblogs.com/builtonfacts/2008/12/15/greatest-physicists-2-albert-e/

5. LAAW
#IAmTheLAAW
Waterfall Development > Agile Development
https://blog.ganttpro.com/en/waterfall-vs-agile-with-advantages-and-disadvantages/

6. LAAW
#IAmTheLAAW
Prior Accessibility Audit Method
● 6 week process
● Performed by accessibility specialists
● Annually performed
● Viewed as compliance
● Many issues left unfixed

7. LAAW
#IAmTheLAAW
How Can This Audit Process Be Improved?
● 6 week process
● Performed by accessibility specialists
● Annually performed
● Viewed as compliance
● Many issues left unfixed
https://blog.ganttpro.com/en/waterfall-vs-agile-with-advantages-and-disadvantages/
● Faster process
● Spread the knowledge
● Performed more often
● Not a rubber stamp
● Fix more issues

8. What are some frustrations
you have had with
accessibility audits?

9. LAAW
#IAmTheLAAW
We All Have a Role in Accessibility
● Accessibility Specialists & UX Researchers - Train
● UX Designers - Design
● Content Strategy - Label
● Front-End Development - Implement
● Quality Assurance - Detect
● Product Owners - Prioritize
https://blog.ganttpro.com/en/waterfall-vs-agile-with-advantages-and-disadvantages/

10. Problem:
How can we include accessibility in agile
software development across many teams?

11. LAAW
#IAmTheLAAW
LAAW (Lean Accessibility Audit Workshops)
● 6 week process
● Performed by accessibility specialists
● Annually performed
● Viewed as compliance
● Many issues left unfixed
https://blog.ganttpro.com/en/waterfall-vs-agile-with-advantages-and-disadvantages/
● 2 week process
● Performed by agile teams
● Continuous
● Seek improvement not perfection
● Teams can detect earlier or avoid

12. Build Empathy
LAAW the First
LAAW (Lean Accessibility Audit Workshops)
1. Build Empathy
2. Define Web Accessibility
3. Detect Accessibility Issues
4. Prioritize Accessibility Issues
5. Design for Inclusivity

13. LAAW
#IAmTheLAAW
Build Empathy
Activities
● Motor
● Low Vision
● Total Blindness
● Hearing Loss or Impairment
● Cognitive
● W3C Perspective Videos
https://twitter.com/AxessLab/status/1034482989286285312
These activities are not meant to simulate
disabilities. They provide a sliver of that
experience to help us understand how
disabilities can affect the user experience.

14. Define Web
Accessibility
LAAW the Second
LAAW (Lean Accessibility Audit Workshops)
1. Build Empathy
2. Define Web Accessibility
3. Detect Accessibility Issues
4. Prioritize Accessibility Issues
5. Design for Inclusivity

15. “The usability of a product,
service, environment or facility by
people with the widest range of
capabilities.”
ISO 9241-171

16. LAAW
#IAmTheLAAW
Define Web Accessibility
Topics
● What is web accessibility?
● Assistive technology and strategies
● WCAG 2.1 (Web Content Accessibility Guidelines)
● Benefits of accessibility
● Set expectations
● Most common problems

17. LAAW
#IAmTheLAAW
WCAG Accessibility Guidelines
1. Perceivable
1.1 Provide text alternatives for any non-text content so that it can be changed into other forms
people need, such as large print, braille, speech, symbols or simpler language.
1.2 Provide alternatives for time-based media.
1.3 Create content that can be presented in different ways (for example simpler layout) without
losing information or structure.
1.4 Make it easier for users to see and hear content including separating foreground from background.
2. Operable
2.1 Make all functionality available from a keyboard.
2.2 Provide users enough time to read and use content.
2.3 Do not design content in a way that is known to cause seizures.
2.4 Provide ways to help users navigate, find content, and determine where they are.
3. Understandable
3.1 Make text content readable and understandable.
3.2 Make Web pages appear and operate in predictable ways.
3.3 Help users avoid and correct mistakes.
4. Robust
4.1 Maximize compatibility with current and future user agents, including assistive technologies.
https://www.w3.org/WAI/WCAG20/quickref/

18. Permanent,
Temporary,
& Situational
Disabilities
https://download.microsoft.com/download/b/0/d/b0d4bf87-09ce-4417-8f28-d60703d672ed/inclusive_toolkit_manual_final.pdf

19. LAAW
#IAmTheLAAW
Most Common Problems
● Color contrast
● Labeling
● Keyboard only
● Captioning
● Real-time messaging
● Content reflow
● Well-formed HTML
● Color only

20. What other common accessibility
problems do you find?

21. Detect
Accessibility
Issues
LAAW the Third
LAAW (Lean Accessibility Audit Workshops)
1. Build Empathy
2. Define Web Accessibility
3. Detect Accessibility Issues
4. Prioritize Accessibility Issues
5. Design for Inclusivity

22. LAAW
#IAmTheLAAW
Case Study: The Junior League of Boston
https://www.jlboston.org/

23. LAAW
#IAmTheLAAW
Scope the Audit
● What product are you evaluating
and why?
● What will happen with the results?
● How much time do you have?
● Consider:
○ Disabilities
○ Guidelines
○ Devices
■ Operating systems
■ Browsers

24. LAAW
#IAmTheLAAW
Scope the Audit
https://www.jlboston.org/
● 10-20 pages
● Highest traffic
● Most common layouts

25. LAAW
#IAmTheLAAW
Detect Accessibility Issues
● Workshops over 3-4 days
● For each evaluation type
○ Home page as a group
○ Teams assigned pages

26. LAAW
#IAmTheLAAW
Detect Accessibility Issues
Audit Activities
○ Automatic Tools: WAVE,
Accessibility Insights
○ WCAG Quick Reference
○ Keyboard Only
○ Magnification of screen and text
○ Screen readers
○ Manual checks (color only, captions)

27. What other accessibility tools
and methods do you use?

28. Prioritize
Accessibility
Issues
LAAW the Fourth
LAAW (Lean Accessibility Audit Workshops)
1. Build Empathy
2. Define Web Accessibility
3. Detect Accessibility Issues
4. Prioritize Accessibility Issues
5. Design for Inclusivity

29. LAAW
#IAmTheLAAW
Prioritize Accessibility Issues
Capture Findings
● White pads for each page
● Write top findings on stickies
● Stickies can include:
○ Description
○ Your initials
○ Page
○ WCAG standard

30. LAAW
#IAmTheLAAW
Prioritize Accessibility Issues
● Group findings and name groups
● Assign severity to each group
S1: Critical Barriers
S2: Frustrating
S3: Annoying
S4: Minor
S0: Unknown

31. Design for
Inclusivity
The Final LAAW
LAAW (Lean Accessibility Audit Workshops)
1. Build Empathy
2. Define Web Accessibility
3. Detect Accessibility Issues
4. Prioritize Accessibility Issues
5. Design for Inclusivity

32. LAAW
#IAmTheLAAW
Report Prioritized Findings

33. LAAW
#IAmTheLAAW
Design for Inclusivity
● Make recommendations
● Design with cross functional team
● Test with representative users
● Add to backlog and track
● Share learnings
● Perform frequent mini-audits
● Add learnings to overall process

34. Results

35. LAAW
#IAmTheLAAW
Results
● Accessibility workshops for Sales, Service,
Claims and Website in 2019
● More awareness overall
● More expertise
● Faster detection and fixing of issues
● Core feature of design system
● Accessibility Guild
https://www.ebsco.com/blog/article/building-products-with-user-accessibility-in-mind-an-e-books-case-study

36. Takeaway Tips
1. Involve designers, developers, QA, content and POs
2. Focus on most common problems
3. Goal is continuous improvement, not perfection
Questions!
@ryaninteractive #IAmTheLAAW