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.

Sign up for GitHub

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

Jump to bottom

Fix ruleID target_spacing_sufficient for potential_overlap to ignore this kind of inline links #2070

Open
philljenkins opened this issue Oct 14, 2024 · 2 comments
Open

Fix ruleID target_spacing_sufficient for potential_overlap to ignore this kind of inline links #2070

philljenkins opened this issue Oct 14, 2024 · 2 comments
Assignees
@shunguoy
Labels
Bug Something isn't working engine Issues in the accessibility-checker-engine component priority-3 (low)

Comments

@philljenkins
Copy link
Contributor

philljenkins commented Oct 14, 2024 •
edited
Loading

In this example where both links are inline text, the overlap test is an exception and should not be reported.

Requirement: 2.5.8 Target size (minimum)

Exceptions: ... If the target is an Inline link in body text, it does not need to meet the minimums.

Screenshot 2024-10-14 at 2 28 05 PM
@philljenkins
Copy link
Contributor Author

@shunguoy Should this issue be scheduled for this release or put in the Tool backlog Project?

@philljenkins
Copy link
Contributor Author

philljenkins commented Oct 14, 2024 •
edited
Loading

Use this file as a test case
rwlp_jaxrs2.0_atom_wfm_scanned.html.zip

  • it should not report Needs Review for Potential_overlap

@philljenkins philljenkins added Bug Something isn't working priority-3 (low) engine Issues in the accessibility-checker-engine component labels Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shunguoy shunguoy

Labels
Bug Something isn't working engine Issues in the accessibility-checker-engine component priority-3 (low)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@philljenkins @shunguoy