Which accessibility testing tool should you use?

[ladissi]

Overview

There are more than 100 accessibility testing tools. Figuring out which ones to use can be a black hole. For guidance we recommend this article: Which accessibility testing tool should you use?

Summary of Article

The author recommends using the tools in the following order fixing as you go along, since no one tool catches all the relevant issues

• aXe - Bruce
• SiteImprove - Bhagya
• WAVE - Nandana
• Lighthouse - Max

Tenon will be skipped since it is throwing errors

But if you want to test your site with other tools, here is a bigger list

List of Issues:

List of Issues:

• Fix Contrast on Buttons to Pass Accessibility Threshold #1094
• Properly label form elements for accessibility #1102
• Display for orgs on View Organization #1112
• Update link colors to pass accessibility test #1122
• Link Purpose (In Context) Accessibility #1107
• Image with no alt attribute  #1106
• "Bold" tag used to format text #1104
• Header sizing accessibility issues #1101

[bruceplai]

Spreadsheet with ongoing audit results is here:

https://drive.google.com/drive/folders/1daFpdXPo07KCxrPKFfexrqX-yqIdpdu3?usp=sharing

[mariastudnicka]

Per @cnk Caltech uses Wave. Here's a link to tool choices for reference from the CMS she works with https://wagtail.io/accessibility/

[ladissi]

@bruceplai and dev team to do additional run through to make sure there are no duplicate documented issues. Afterwards if support is needed in creating issues please tag @kevindphan and I in the comments

[bruceplai]

@ladissi @kevindphan Accessibility issues have been consolidated in the spreadsheet. Before we get into creating front end issues, we may need to consult with @chalimar. Some of the spreadsheet items are related to design (for example 1) sufficient color contrast for elements such as links and buttons 2) sequential heading text sizes to help the user navigate the page hierarchy)

[ladissi]

@bruceplai to set some time with UI/UX and include PM's as optional to review issues

[ladissi]

@chalimar FYI a session will be needed to determine how the accessibility updates will need to be implemented through a ui/ux lens. @bruceplai will be reaching out to you

[bruceplai]

@chalimar after more analysis for the sequential header accessibility issue, it seems aXe really does want headers to increase only one level at a time as you dig deeper into the page hierarchy. On some pages the header size updates won't be noticeable, but on others it will. It's not a high severity level issue like color contrast. How should we handle it? Leave the headers alone as long as the h values are increasing down the page?

[kevindphan]

Will discuss with Chali

[ladissi]

@chalimar please provide update

1. Progress
2. Blockers
3. Availability
4. ETA

[ladissi]

Dev team to create issues that dont require UI/UX based off spreadsheet. To be placed in New Issue Approval for PM's to review

[ExperimentsInHonesty]

@chalimar It looks like there are design issues that need to be discussed. Can I help you review that and make issues. We want to lock this down before you get massively busy. lol, I know you are already busy.

[smsada]

If there are more accessibility issues, let's open up new tickets. Closing this issue now