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_AzureNotebooksWelcome_ScreenReader: In the dialog which get displayed after selecting "heading" from the dialog, Used heading markup for the text "Use markdown headings" is inaccurate. #3936

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

Comments

@AccessibilityTestingTeam-TCS

Environment Details:
Application Name: AzureNotebooks_Jupyter
Login URL: notebooks.azure.com
Browser Details:
Edge: Microsoft Edge 42.17134.1.0
Chrome: Version 68.0.3440.106
Operating System:Windows10

Repro Steps:
1.Login with the appropriate credentials to azure notebook account.
2. Navigate to run button & hit enter --> Navigate to Azure Notebooks welcome & hit enter.
3. Navigate to Combobox present after the "Restart Kernal" button.
4. Select Heading list item by using arrow key.
5.Verify heading markup using screen reader.

Actual:
In the dialog which get displayed after selecting "heading" from the dialog, the text "Use markdown headings" is markup using H4 which is inaccurate.

Expected:
Heading markup should be accurate for the content on page.
It should be markup using H1.

User Impact:
Screen reader user will not able to understand the content structure of popup.

A11y_AzureNotebooks_Jupyter_AzureNotebooksWelcome_ScreenReader.pptx

@takluyver
Copy link
Member

Does this mean all dialogs should have an <h1> heading? Or is it something specific about the 'Use markdown headings' dialog?

@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