Use aXe Accessibility Engine in tests to ensure accessibility
Open
Nobody has claimed this yet.
1. to develop
design
enhancement
feature: accessibility
tests
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
It seems that we could use aXe in our tests to make sure that modifications don’t break accessibility.
https://github.com/dequelabs/axe-core#getting-started
@MorrisJobke @skjnldsv @juliushaertl @nextcloud/accessibility is this something we can add to our testing stack so it is run automatically?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or existing test is named. Start with the linked aXe getting-started documentation and inspect the project's testing stack to determine where accessibility checks could run automatically. Done means tests use aXe and detect accessibility regressions in later modifications.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100