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

A11y_AzureNotebooks_Jupyter_EditMetada_ScreenReader: NVDA reads 'Clickable clickable Cancel button' twice when the focus is on 'Cancel' button. #4008

Closed
AccessibilityTestingTeam-TCS opened this issue Sep 20, 2018 · 2 comments

Comments

@AccessibilityTestingTeam-TCS

EnvironmentDetails:
Application Name:AzureNotebooks_Jyupter
Login Url: notebooks.azure.com
BrowserDetails:
Edge:Microsoft Edge 41.16299.611.0
Chrome:Version 68.0.3440.106
Operating System:Windows10

Steps to reproduce:
1.Login with the appropriate credentials to azure notebook account.
2.Go to Get started à libraries à Select any of the libraries à click on clone to clone the library.
3.Start NVDA.
3.Click on Run or right click and select Run to run the notebook.
4.Navigate to any file present under Files tab-->Hit enter-->View Menu-->Cell Toolbar-->Edit Metadata. Click on Edit Metadata button appeared on page.
5. Verify how NVDA reads when the keyboard focus is on 'Cancel' Button.

Actual:
NVDA reads 'clickable clickable cancel button' when focus is on 'Cancel' Button.

Expected:
NVDA should read 'Cancel button' just once when the focus is on 'Cancel' button.

User Impact:
Screenreader user will get confuse when NVDA would read the controls twice.

Attachment:
(https://github.com/jupyter/notebook/files/2401214/A11y_AzureNotebooks_Jupyter_EditMetada_ScreenReader.pptx)

@joshuazeltser
Copy link
Contributor

We tested this on Windows 10 using Microsoft Edge with NVDA and were not able to reproduce the bug

@jtpio
Copy link
Member

jtpio commented Feb 20, 2024

Closing as there are now different issues tracking accessibility improvements for Jupyter Notebook 7, for example #6800

Thanks!

@jtpio jtpio closed this as completed Feb 20, 2024
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

4 participants