-
Type:
Suggestion
-
Resolution: Low Engagement
-
None
-
Component/s: Front-end API
→ If the <h1> heading should read "All Sprints", the <h1> element must also enclose the text "All Sprints".
→ The headings structured with <h6> must be marked with <h2>. Formats are to be adapted using CSS.
→ The additional <h1> label "Jira-Software" in the upper navigation bar is not a meaningful heading and must be removed.
→ If the <h1> heading is to read "Backlog", the <h1> element must also be positioned around the text "Backlog" and must not include other elements.
The subordinate headings are all structured with <h3> and <h4>, but the correct sequence in the structure would be <h2> and <h3>. In addition, the detail area starts with <h4> and in between a heading is marked with <h3>. The sub-headings are completely missing in the main area. It is not possible for screen reader users to recognize a meaningful heading structure.
→ The substructure must be completely labeled with hierarchically correct headings from <h2>.
→ The additional <h1> label "Jira-Software" in the upper navigation bar is not a meaningful heading and must be removed.
→ Findings of this kind extend over the entire application and basically have to be improved almost everywhere.