-
Notifications
You must be signed in to change notification settings - Fork 287
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
[DOCS]: Screen reader is not announcing the descriptive information for the ‘Here’ link. #4764
Comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
16 similar comments
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue . |
What happened?
Screen reader is not announcing the descriptive information for the ‘Here’ link, which is present on the page multiple times, it is announcing as ‘Link here'.
How do we reproduce the behavior?
Repro steps:
Open the URL: PWABuilder - Meta Quest in edge dev browser and login with v-.
2. Turn on the screen reader through Ctrl+ Windows+ Enter key.
3. Navigate to the ‘Here’ link through tab key.
4. Observe the issue.
What do you expect to happen?
Screen reader should announce the descriptive information for the ‘Here’ link. Screen reader should announce as ‘Follow the instruction on link here’.
What environment were you using?
Test Environment:
OS: Windows11
OS Version: 23H2 (Build 25905.1000)
Browser: Edge Dev (Version 117.0.2007.0 (Official build) dev (64-bit))
Screen reader: Narrator
Additional context
Notes:
User Impact:
Screen reader users will get impacted as users will not be able to the purpose of the link and will not be able to interact or make track of the content properly.
WCAG reference link:
Understanding Success Criterion 2.4.9: Link Purpose (Link Only) | WAI | W3C
Attachments:
Screen.reader.is.not.announcing.the.descriptive.information.for.the.Here.link.mp4
The text was updated successfully, but these errors were encountered: