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

[Accessibility] No H1 heading is defined in the 'Graph Explorer' page. #1903

Closed
ElinorW opened this issue Jul 7, 2022 · 0 comments · Fixed by #1921
Closed

[Accessibility] No H1 heading is defined in the 'Graph Explorer' page. #1903

ElinorW opened this issue Jul 7, 2022 · 0 comments · Fixed by #1921
Assignees
Labels
priority:p2 Medium. Generally has a work-around and a smaller sub-set of customers is affected. SLA <=30 days type: accessibility A general accessibility issue
Milestone

Comments

@ElinorW
Copy link
Contributor

ElinorW commented Jul 7, 2022

Test Environment:
OS Build: Version 22H2(OS Build 25136.1000) 
Browser: Version 104.0.1278.2 (Official build) dev (64-bit)
URL: Graph Explorer | Try Microsoft Graph APIs - Microsoft Graph
Tool- Accessibility insight for web
Screen reader: Narrator

Repro Steps:

  1. Open above URL in Edge dev browser.
  2. Turn on Narrator then scan mode using Caps+ Space key.
  3. Navigate to headings on the page by pressing the 'h' in scan mode and also check with Accessibility insight tool.
  4. Observe the issue here.

Actual Result:
No H1 heading is defined in the 'Graph Explorer' page.

Expected Result:
'Graph Explorer' text on the page should be defined under H1 heading tag programmatically.

User Impact:
Screen reader users will be confused with the structure of page if no H1 heading is defined programmatically on the page.

MAS Reference:
Info and Relationships - Liquid (microsoft.com)

Additional context
Issue: https://office.visualstudio.com/OC/_workitems/edit/6195406

@ElinorW ElinorW added priority:p2 Medium. Generally has a work-around and a smaller sub-set of customers is affected. SLA <=30 days type: accessibility A general accessibility issue labels Jul 7, 2022
@ElinorW ElinorW added this to the July-2022 milestone Jul 7, 2022
@ghost ghost added the ToTriage label Jul 7, 2022
@ElinorW ElinorW self-assigned this Jul 12, 2022
@ghost ghost removed the ToTriage label Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:p2 Medium. Generally has a work-around and a smaller sub-set of customers is affected. SLA <=30 days type: accessibility A general accessibility issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant