Creating Government Accessibility Services

Presented by Ryan Leisinger / @ryanleisinger

Accessibility In WA State Gov

Some shared centralized services
HR, Finance, Contracts, Phone, Network, Email
Agencies support business solutions

Guideline To Policy

2005 Guideline
2016 Accessibility Policy
Yellow sign with number 188

WA State Policy #188

August 11th, 2016
Washington State Chief Information Officer
OCIO Policy #188
ALL TECH MUST MEET WCAG 2.0 AA

Resources to support #188

  • Agencies don't have accessibility experts
  • Agencies look to Central IT for help
  • Resources are slim
  • Agencies at different maturity levels
  • Small Agency Support

Training

Training on Policy requirements
Procurement training
Accessibility 101 training
Design, Publishing, Development, Testing

Design

Consult on Inclusive Product Design
Facilitate a design sprint
Design from the edge

Development

Web Platform

  • Drupal sites with our custom base theme
  • Module library
  • Using GitHub for versioning

Testing

Who?

Existing User Experience Team with a passion and interest in Accessibility
Using current UX Lab.

Multiple layer approach to testing

  • Code Validation & Automatic Testing
    •
  • Functional Testing
    •
  • Real User/UX Testing

    •
Code Validation & Automatic Testing - Functional Testing - Real User Testing

Code Validation

Run DOM against WCAG 2.0 AA code validation service.
  • In browser
  • Manually submit page
  • Service

Simple or complex
Chrome plugin or automated testing in continuous integration system (Git Flow, CircleCI & Pa11y)

Zero errors does not mean the site is accessible, it mean go to the next step.

Deliverable

Errors & Warnings
Referenced back to standard
Recommended action
1.1.1 Non-text Content (Level A)
2.4.4 Link Purpose (In Context) (Level A)

Recommendation: Add screenreader available only text to button
Code Validation & Automatic Testing - Functional Testing - Real User Testing

Functional Test

Test of predetermined criteria against a site or app, including using assisted technology (screen reader) & input methods that parallel those of people with disabilities (keyboard only navigation).

Checklist

Modified version of WebAim & UW Checklist

Deliverable

Checklist results - Pass/Fail & Comment
Referenced back to standard
Recommended action
Document AT used including version and setting
Code Validation & Automatic Testing - Functional Testing - Real User Testing

Real User Test

Actual users doing real things
Facilitation is important
Power users not always best testers

Deliverable

Multi page report on all user's experience
Section that compares/contrasts AT user's experience
Generally less techinical recommendations

What we've noticed
  • Too much text
    •
  • Not all accessibility errors are equal
    •
  • Don't rely on main nav
    •
  • Focus on forms
    •
  • Documents are an issue
    •
  • Product owners and devs should attend
    •
  • Record your sessions
    •

More

Ryan Leisinger
ryan.leisinger@watech.wa.gov
My roles
@ryanleisinger