Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistency: Prioritize cantTell over pass #558

Merged
merged 1 commit into from
Feb 1, 2024
Merged

Conversation

WilcoFiers
Copy link
Collaborator

Based on feedback @dbjorge: from w3c/wcag#3616 (comment)

I agree that cantTell was too low down the list. If a check reports pass and cantTell, it's incorrect to conclude that's a pass. It wouldn't work for satisfying rules. I think it does not go above untested though. Any untested outcome should prevent a check from getting mapped as consistent, and if we put cantTell before untested that wouldn't happen; Checks can be consistent when they report cantTell as long as that isn't the only thing they report.

@WilcoFiers
Copy link
Collaborator Author

Approved by TF on 2024/02/01

@WilcoFiers WilcoFiers merged commit 0b752d0 into main Feb 1, 2024
3 checks passed
@WilcoFiers WilcoFiers deleted the consistency-order branch February 1, 2024 14:14
github-actions bot added a commit that referenced this pull request Feb 1, 2024
SHA: 0b752d0
Reason: push, by WilcoFiers

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit that referenced this pull request Feb 1, 2024
SHA: 0b752d0
Reason: push, by WilcoFiers

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant