Accessibility issues found by aXe
Open
Nobody has claimed this yet.
1. to develop
enhancement
good first issue
hacktoberfest
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
To find the issues yourself:
- install the aXe browser extension
- open the network tab and go to the aXe panel
- click 'Analyze'
This issue is about solving some remaining errors:
(The first one is a false-positive due to ng-if)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
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
Install the aXe browser extension, open the app's network tab and aXe panel, and click Analyze to reproduce the remaining errors shown in the issue. Exclude the first reported item as the noted ng-if false positive; done means the other accessibility errors no longer appear when Analyze is run again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100