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

Keyboard-only users (ambulatory), do not see the hoverable/tooltip of the icons in heading and in code cells when focusing on the elements. #6931

Open
Tracked by #6800
tonyfast opened this issue Jun 16, 2023 · 4 comments

Comments

@tonyfast
Copy link
Collaborator

tonyfast commented Jun 16, 2023

Issue Area # 3

  • Expectation: Is content that appears on hover or keyboard focus dismissible, hovberable, and persistent? (WCAG Criteria 1.4.13 (AA))
  • Observed:
    • All hoverables (tooltips) are not appearing on keyboard focus based on what I could tell. AKA, people using only keyboard do not know that the play button in the heading has meaning "Run the selected cells (Shift + Enter)". They just have to guess what all of these buttons do.
@tonyfast
Copy link
Collaborator Author

@manfromjupyter i can confirm that keyboard focus does not show the tools tips.

Display the title attribute on focus indicates that this behavior requires javascript to be implemented.

i imagine there are a few folks that have the chops to land this.

@andrii-i andrii-i added enhancement and removed status:Needs Triage Applied to issues that need triage labels Jun 20, 2023
@andrii-i
Copy link
Contributor

Title should appear on keyboard focus in JupyterLab as well

@Cheukting
Copy link
Contributor

I have a play with the CSS-only version, and it looks weird, I guess it needs to go down the js route?

Screen.Recording.2023-06-21.at.21.03.45.mov

One more question, it seems the ui-component is from a JupyterLab library. Maybe fixing one will fix both? (I am not sure, just asking)

@tonyfast
Copy link
Collaborator Author

One more question, it seems the ui-component is from a JupyterLab library. Maybe fixing one will fix both? (I am not sure, just asking)

we suspect that a lot of notebook fixes will also be jupyterlab fixes since notebook uses jupyterlab components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants