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 verbalization of Flutter logos in search results page #10540

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

Fix verbalization of Flutter logos in search results page #10540

atsansone opened this issue May 8, 2024 · 0 comments
Assignees
Labels
e2-days Effort: < 5 days infra.structure Relates to the tools that create docs.flutter.dev 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/337307320

Observed Results

Navigating through the page specifically on the flutter buttons, listen to how are verbalized by SR.

Expected Results

Ensure that the flutter button should have the correct label that is a button opening a new window/tab.

Example: Flutter button that opens the use of memory in a new window/tab.

User Impact

Screen reader and Cognitive users are affected because those buttons are announced as images and never indicate that open a new window/tab.

Steps to Reproduce

  1. Enabled VoiceOver using Command + F5 also ChromeVox using Ctrl + Alt + Z
  2. Open the following page: https://docs.flutter.dev/search?q=devtools
  3. Continue the linear navigation using the Tab key and reach the flutter buttons.
  4. Listen that they are announced as thumbnail images and never notified that open a new window/tab.

GAR Assessment

Flutter Docs

GAR Details

1.11. Is the purpose of each link, control, and button clear?

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 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 infra.structure Relates to the tools that create docs.flutter.dev 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 infra.structure Relates to the tools that create docs.flutter.dev 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

2 participants