search

cityofaustin / techstack

Project management for the City of Austin's new digital service delivery platform, Austin.gov.
11 stars 3 forks source link

Acceptance Criteria -- Accessibility (A11y) Audit #115

Open ifsimicoded opened 6 years ago

ifsimicoded commented 6 years ago

Before we encourage external users, we need to make sure our site is compliant with a11y standards and legal requirements. We should also document what standards we are holding ourselves to moving forward.

  1. Document resources on a11y standards and requirements in gov.
  2. Implement workflows to help automate future a11y compliance.
  3. Accessibility Audit on alpha.austin.gov including usability testing with screen reader.
mateoclarke commented 6 years ago

one part of the preflight checklist has a section for a11y: https://github.com/thedaviddias/Front-End-Checklist#accessibility

amenity commented 6 years ago

So we think that the A11y audit should be separate from the rest of the dev audit? I really like this Front-End-Checklist @mateoclarke shared.

mateoclarke commented 6 years ago

https://a11yproject.com/checklist

mateoclarke commented 6 years ago

https://accessibility.blog.gov.uk/2018/02/28/how-weve-made-gov-uk-elements-even-more-accessible/

mateoclarke commented 6 years ago

https://www.w3.org/WAI/WCAG20/quickref/

mateoclarke commented 6 years ago

A couple more resources I worked through briefly with @juliazbyron: http://wave.webaim.org/ https://developers.google.com/web/fundamentals/accessibility/how-to-review Chrome now comes with an auditing tool called "Lighthouse" baked in: https://developers.google.com/web/tools/lighthouse/#devtools

mateoclarke commented 6 years ago

https://accessibility.blog.gov.uk/

amenity commented 6 years ago

@cthibaultatx - are you putting together a doc with this checklist?

mateoclarke commented 6 years ago

@amenity, @cthibaultatx, Let's put resources here if appropriate: https://github.com/cityofaustin/janis#accessibility-guidelines-wip

amenity commented 6 years ago

@ifsimicoded @mateoclarke @cthibaultatx - I added ☝️ to the Janis readme. So that leaves us at:

~1. Document resources on a11y standards and requirements in gov.~

  1. Implement workflows to help automate future a11y compliance.
  2. Accessibility Audit on alpha.austin.gov including usability testing with screen reader.

What are next steps for this? 2 looks like it might deserve its own issue...

juliazbyron commented 6 years ago

I can't tell where to put this on the accessibility guidelines @mateoclarke linked to, but I think 2 good steps in the criteria would be to run the design/prototype/site through the WAVE analyzer and the Google Dev Tools Accessibility analyzer and reach 100% passing. I don't think 100% is unmanageable after doing it myself, it seems to be pretty basic necessities.

amenity commented 6 years ago

@juliazbyron - https://github.com/cityofaustin/janis#accessibility-guidelines-wip should take you to the section, but if it's causing problems just add links here and I'll copy 🍝

cthibaultatx commented 6 years ago

1. Document resources on a11y standards and requirements in gov.

  1. Implement workflows to help automate future a11y compliance. 3. Accessibility Audit on alpha.austin.gov including usability testing with screen reader. moved to issue #267
juliazbyron commented 6 years ago

I know we started talking about this again this sprint, but can we put it back down until next sprint since we're kind of overloaded?