Consistency: Prioritize cantTell over pass #558
Merged
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.
Based on feedback @dbjorge: from w3c/wcag#3616 (comment)
I agree that
cantTell
was too low down the list. If a check reportspass
andcantTell
, it's incorrect to conclude that's a pass. It wouldn't work for satisfying rules. I think it does not go aboveuntested
though. Anyuntested
outcome should prevent a check from getting mapped asconsistent
, and if we putcantTell
beforeuntested
that wouldn't happen; Checks can be consistent when they reportcantTell
as long as that isn't the only thing they report.