Do an accessibility benchmark & gap analysis of our food-seeker website

[fancyham]

Overview and goals

We currently don't know how accessible our website is for people with low vision/ blind, neurodivergence, etc.

We'd ideally like to be accessible to as many people as possible, so let's find out where we can improve.

So let's learn about how to do an accessibility review, do that review to identify areas for improvement, and enter those areas as issues.

Action Items

• [ ] Find the appropriate accessibility audits / benchmarking procedures that we should be using (please share with FOLA team!)
• [ ] Do an accessibility review of our site
• [ ] Make a gap analysis report
• [ ] Add github issues for items that we would like to improve

Resources/Instructions

Hack for LA used to use "Lighthouse" for accessibility auditing, but check if that's still the case. https://www.boia.org/blog/googles-lighthouse-accessibility-tests-are-helpful-but-not-perfect

If Hack for LA still recommends that (and you agree), go onto this page: https://github.com/hackforla/food-oasis/issues/new/choose and scroll down and you'll see a bunch of "Lighthouse" issue templates. We never used them but choose a template and they seem to have instructions for an audit?

If based on your research there are better ways to do it nowadays, make a recommendation or let's discuss

Related

Look at previous discussion here:

• 325

Is also somewhat related to

• 1144

[fancyham]

Some resources to find accessibility auditing tools/checklists/methods:

Ask for tips/resources on HfLA Slack channel #accessibility-design as well as on the web to find out what’s the current best practice (that are feasible for us)

Also, it looks like our Slack is on a temporary free trial so do some searches and you might find something.

What types of accessibility are we looking at? Vision is one, are there others we might want to consider?

It seems like HfLA used to use Google’s Lighthouse perhaps a few years ago. Not sure if that's specifically for accessibility or if it's a current best practice. It sounds like it's not specifically about accessibility.

Some possibly helpful resource links:

• https://www.a11yproject.com/checklist/
• https://accessibility.day/
• https://chrome.google.com/webstore/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd
• https://inclusivedesign24.org/2022/schedule/
  • These sound interesting:
  • A designer’s guide to documenting accessibility (this was interesting — look at around 24 minutes in)
  • Web Accessibility for Speech Recognition users - A pragmatic approach
  • The UX of accessibility checklist

Also, try out large font sizes on our site — that's probably the most common accessibility thing folks do!

[staceyrebekahscott]

@fancyham @jnaito777 James- are you interested in working on this?