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

Revisit: input_haspopup_conflict - can we tighten scope? #1622

Closed
tombrunet opened this issue Aug 29, 2023 · 1 comment · Fixed by #1917
Closed

Revisit: input_haspopup_conflict - can we tighten scope? #1622

tombrunet opened this issue Aug 29, 2023 · 1 comment · Fixed by #1917
Assignees
Labels
engine Issues in the accessibility-checker-engine component priority-3 (low) Ready for QA

Comments

@tombrunet
Copy link
Member

tombrunet commented Aug 29, 2023

This rule fires some "Needs review" items. Can we identify scenarios where this definitely passes so that we can tighten the scope and trigger fewer "Needs Review" items for this.

@tombrunet tombrunet added engine Issues in the accessibility-checker-engine component priority-3 (low) labels Aug 29, 2023
shunguoy added a commit that referenced this issue Jun 5, 2024
shunguoy added a commit that referenced this issue Jun 6, 2024
@philljenkins
Copy link
Contributor

philljenkins commented Jun 18, 2024

Previous messages were:

image

Messages now display as follows:

Screenshot 2024-06-18 at 4 44 28 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine Issues in the accessibility-checker-engine component priority-3 (low) Ready for QA
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants