Review accessibility tools, make recommendations about alpha HOT 5 CLOSED

From slack:

Aaron Hans 23 hours ago
did some tool reviewing, unfortunately the current ca.gov was a good candidate for finding issues in a11y audits, notes added to tool. I'd recommend starting with the following toolset initially

• Webhint for linter integrated into code editor
• Lighthouse for CI integration (We will also use lighthouse for CI integrated performance audits)
• axe chrome plugin for manual test runs against live site versions

from alpha.

Thanks for your help with this @abquirarte after reviewing the accessibility reports for some of our baseline pages and the user experience of the in browser version of webhint, lighthouse online, lighthouse in dev tools and wave. We have updated our recommendations:

• Use Lighthouse in dev tools to trigger an audit on page (There is a firefox extension as well)

Still sticking with lighthouse for CI
and webhint for in editor linking

from alpha.

from alpha.

We saw identical results from webhint and in browser dev tools lighthouse accessibility reports on multiple pages so going with the built in lighthouse tool. Wave missed some issues on the licensed contractor page. Wave is also one of the tools that is not open source so we are dropping that from the candidate list.

from alpha.

Attempting to document the steps for our reference:
@aaronhans @lukefretwell @humancenteredhuman @artuoma @orielgomez @jpetrucione @carterm @ChadABratton @hilaryhb @KimberlyglennTSM

1. To access this, you can go to your browser (Chrome or Firefox)
2. You have to be on the page you are trying to test
3. Control + Shift + I to access Dev tools
4. Go to Audits

When you run the audit you will get the following:

The audit will timestamp when you run the report
To run a new one, click on the plus sign on top of the left corner.

from alpha.