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

Fix descriptions for Visit <page> links #10533

Open
Tracked by #9495
atsansone opened this issue May 8, 2024 · 0 comments
Open
Tracked by #9495

Fix descriptions for Visit <page> links #10533

atsansone opened this issue May 8, 2024 · 0 comments
Assignees
Labels
e2-days Effort: < 5 days p2-medium Necessary but not urgent concern. Resolve when possible. st.triage.ltw Indicates Lead Tech Writer has triaged t.a11y Relates to an accessibility concern

Comments

@atsansone
Copy link
Contributor

From https://buganizer.corp.google.com/issues/337104253

Observed Results

Navigating through the page specifically on Visit links, listen that all of them are announced the same description.

Expected Results

Ensure that Visit links should have a descriptive name to users example

  • Visit accessibility site link.
  • Visit Animation and Motion link...

User Impact

Screen reader and Cognitive users are affected because all "Visit" links have the same description and are confused to them.

Steps to Reproduce

  1. Enabled VoiceOver using Command + F5 also ChromeVox using Ctrl + Alt + Z
  2. Open the following page: https://docs.flutter.dev/ui/widgets
  3. Continue the linear navigation using the Tab key and reach the cards components.
  4. Navigate through the links specifically on Visit links and listen to the results.

GAR Assessment

Flutter Docs

GAR Details

1.1. Do all non-text content and user interface components have meaningful accessible names and alternative text?

Environment Details

Machine: MAC/ChromeBook
Browser: Chrome Version 120.0.6099.272 (Official Build) (64-bit)
Screen reader: VoiceOver / ChromeVox.
Bug filling time: 15 mins.

@atsansone atsansone self-assigned this May 8, 2024
@atsansone atsansone added p2-medium Necessary but not urgent concern. Resolve when possible. t.a11y Relates to an accessibility concern st.triage.ltw Indicates Lead Tech Writer has triaged e2-days Effort: < 5 days labels May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2-days Effort: < 5 days p2-medium Necessary but not urgent concern. Resolve when possible. st.triage.ltw Indicates Lead Tech Writer has triaged t.a11y Relates to an accessibility concern
Projects
None yet
Development

No branches or pull requests

1 participant