dequelabs / dequelabs/axe-core
Why aren't deterministic RGAA tests (8.1.1/8.1.2, 10.1.1/10.1.2) reported?
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 933
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 17
Description
### Product
axe-core
### Question
I'm wondering why RGAA tests such as `8.1.1` and `8.1.2` (doctype present / valid) aren't reported by axe-core. They look deterministic and straightforward, and a helper that checks the doctype already exists: `axe.commons.dom.isHTMLS`
Today it's only consumed by `html5-scope-evaluate.is` to decide whether scope is valid, so the result never surfaces as a finding.
Also tests such as `10.1.1` and `10.1.2` (no presentational tags / attributes in the generated source) look just as mechanical and they are listed in the axe-core report.
Is there a strong reason these are missing, or is it more a matter of community involvement and contributors? Happy to help with a PR either way.
Contributor guide
Research direction
Start by tracing axe.commons.dom.isHTMLS and its current use in html5-scope-evaluate.is, then compare how RGAA tests 10.1.1 and 10.1.2 are represented in the axe-core report. Check the existing RGAA rule tests and mappings to determine whether 8.1.1 and 8.1.2 can be surfaced independently. Done means documenting the rationale and, if accepted, adding coverage and report entries for the missing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100