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

Clarify use of certain buttons and links #10534

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

Clarify use of certain buttons and links #10534

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/337111280

Observed Results

Navigating through the page specifically on the video cards, learn/more links and format/disable buttons, need a clear purpose to users.

Expected Results

Ensure that more links should have a clear description to users for example:

  • More video options link.
  • Learn more about flutter link.
  • Format button.

User Impact

Screen reader and Cognitive users are affected because learn/more and forma/disabled buttons/links do not have an understandable purpose to them.

Steps to Reproduce

  1. Enabled VoiceOver using Command + F5 also ChromeVox using Ctrl + Alt + Z

  2. Open the following pages:

  3. Continue the linear navigation using the Tab key and reach the cards components.

  4. Navigate through the links specifically on learn/More links also format/disable buttons and listen to the results.

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