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

[PWA Builder]: Insufficient Target Hit Size for Links and Interactive Elements in PWA Builder Web App #4709

Closed
Priyanshu073 opened this issue Apr 12, 2024 · 6 comments
Assignees
Labels
A11ySev2 Accessibility Team tag - P2 items A11yTTValidated Accessibility team tag for closed bugs A11yWCAG Accessibility Team tag - Web Content Accessibility Guidelines Accessibility [E+D] Issues found by the accessibility E+D Team at Microsoft bug 🐛 HCL-E+D needs attention 👋 WCAG2.2 Accessibility Team tag - Web Content Accessibility Guidelines Version 2.1

Comments

@Priyanshu073
Copy link
Collaborator

What happened?

Links and interactive elements within the PWA Builder Web app have target hit sizes that are too small, requiring precise pointer or touch input for activation.

How do we reproduce the behavior?

  1. Open the PWA Builder URL in Anaheim dev browser.
  2. PWA Builder page will appear.
  3. Now run target size checker app, or check hit size of the interactive controls.
  4. Verify the issue.

What do you expect to happen?

Links and interactive elements should have adequate target hit sizes, allowing users to easily activate and interact with them using various input methods, including mouse, touch, or keyboard navigation.

What environment were you using?

OS: Windows 11(Version 24H2 (Build 26090.112)
Browser: Edge Dev (Version 125.0.2506.0 (Official build) dev (64-bit))
URL: https://docs.pwabuilder.com/#/home/
User ID: V-
Tool: Target Size app

Additional context

User Experience:
Users with motor impairments, touchscreen devices, or those using alternative input methods may struggle to activate and interact with links and interactive elements due to their insufficient target hit sizes, resulting in a less accessible and frustrating user experience.

WCAG Reference:
https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html

Attachments:
image (5)
image (4)

@Priyanshu073 Priyanshu073 added bug 🐛 needs triage 🔍 A11yWCAG Accessibility Team tag - Web Content Accessibility Guidelines Accessibility [E+D] Issues found by the accessibility E+D Team at Microsoft A11ySev2 Accessibility Team tag - P2 items HCL-E+D labels Apr 12, 2024
@DhananjaySaini007 DhananjaySaini007 added the WCAG2.2 Accessibility Team tag - Web Content Accessibility Guidelines Version 2.1 label Apr 15, 2024
@jgw96 jgw96 self-assigned this Apr 15, 2024
@jgw96
Copy link
Contributor

jgw96 commented Apr 15, 2024

Hey! So, I looked at the rules and these links are inline, and so would fall under the inline rule (the one highlighted in the attached photo. Am I wrong on that?
image

@jgw96
Copy link
Contributor

jgw96 commented Apr 18, 2024

@DhananjaySaini007 any feedback on the above?

@Priyanshu073
Copy link
Collaborator Author

Hello @jgw96 ,

It will fall in the same rule.

@jgw96
Copy link
Contributor

jgw96 commented Apr 22, 2024

@Priyanshu073 so this means then that I dont need to make any changes here then, right? As the links marked red are all inline links.

@jgw96
Copy link
Contributor

jgw96 commented May 8, 2024

ping here

@Priyanshu073
Copy link
Collaborator Author

Closing this issue as this is not a failure according to exception criteria of https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html

@Priyanshu073 Priyanshu073 added the A11yTTValidated Accessibility team tag for closed bugs label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11ySev2 Accessibility Team tag - P2 items A11yTTValidated Accessibility team tag for closed bugs A11yWCAG Accessibility Team tag - Web Content Accessibility Guidelines Accessibility [E+D] Issues found by the accessibility E+D Team at Microsoft bug 🐛 HCL-E+D needs attention 👋 WCAG2.2 Accessibility Team tag - Web Content Accessibility Guidelines Version 2.1
Projects
None yet
Development

No branches or pull requests

3 participants