Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Which accessibility testing tool should you use? #177

Closed
ExperimentsInHonesty opened this issue Nov 7, 2019 · 5 comments
Closed

Which accessibility testing tool should you use? #177

ExperimentsInHonesty opened this issue Nov 7, 2019 · 5 comments
Assignees
Labels
Complexity: Missing documentation Documentation creation Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing

Comments

@ExperimentsInHonesty
Copy link
Member

Overview

Figure out which accessibility tool is right for testing the accessibility of the newly added project status indicator and indicate your recommendation in this issue.

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
SiteImprove
Tenon
WAVE
Lighthouse

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

@KianBadie
Copy link
Member

KianBadie commented Nov 10, 2019

Thank you for the starting resources for search of what accessibility tool to use Bonnie! I've only done a little bit of research, but it definitely does seem like a little bit of a rabbit hole trying to find "the ones" to use.

As a starting point, using a combination of the trio of aXe, SiteImprove, and WAVE sound ok to me. Like they would be able to pick up at least low hanging fruit? I will try to do more research, but I also want to type this out to prevent myself of endlessly going down the rabbit hole.

I think I have been seeing WAVE and aXe around though. From the article you provided, it seemed like aXe and SiteImprove had some thorough testing, which was appealing for me. I'll try to play around with the 3 on our site and see what my experience is.

AS for using these tools, there were command lines tools (which I think was used for automated testing) and browser extensions. I was going to use browser extensions, but was automated accessibility testing something you were interested in? Sorry if that question isn't super clear, I still don't fully understand automated accessibility testing.

@ExperimentsInHonesty
Copy link
Member Author

This issue is template I built to introduce all developers to the concept if useability testing. I think you have the concept now. So, its time to just start experimenting and as you make pr requests, if they are going to change the look of the site, run whatever accessabilty tools you think are appropriate and mention which in your pull requests so others can learn from reading the closed issues.

@KianBadie
Copy link
Member

Got it, makes sense, I will be doing that from now on then!

@KianBadie KianBadie assigned harishlingam and unassigned KianBadie Nov 12, 2019
@ExperimentsInHonesty ExperimentsInHonesty removed their assignment Nov 12, 2019
@ExperimentsInHonesty
Copy link
Member Author

@harishlingam you can close this when you have finished reading.

@ExperimentsInHonesty
Copy link
Member Author

@harishlingam can we close this issue now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing documentation Documentation creation Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing
Projects
Development

No branches or pull requests

4 participants