[Outreachy Testing Task] Add accessibility testing results using axe-cli #878
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
For this outreachy testing task, I utilized the axe-cli tool for conducting accessibility testing on the Ushahidi platform. Axe-cli is a widely-used accessibility testing engine known for its robust features and comprehensive reports. The decision to choose axe-cli was based on its reputation in the accessibility testing community and its ability to provide actionable insights into accessibility issues.
Evaluation:
Why did you select this tool?: I selected axe-cli for its reputation, robust features, and comprehensive reports. It's widely used in the accessibility testing community and provides actionable insights into accessibility issues.
How do you like it?: I found axe-cli to be user-friendly and efficient in identifying accessibility issues within the Ushahidi platform.
Does the output make sense to you?: Yes, the output generated by axe-cli was clear and easy to understand, providing detailed information about accessibility violations.
Was it easy or really hard to implement?: Implementing axe-cli was straightforward. Its command-line interface allowed for easy integration into our development workflow.
Do you "trust" the output or do you think it misses something?: I trust the output generated by axe-cli, but it's essential to note that automated tools like axe-cli can't catch all accessibility issues. Manual testing is still necessary to ensure comprehensive accessibility compliance.
Any other comments or insights you would like to share: Overall, axe-cli proved to be a valuable tool for conducting accessibility testing on the Ushahidi platform. Its ease of use and comprehensive reporting capabilities make it a valuable asset for ensuring accessibility compliance in our development process.