-
Type:
Bug
-
Resolution: Done
-
Priority:
High
-
Affects Version/s: 8.20.1
-
Component/s: Accessibility
-
- 4.1.2
- AXSR-15
- Level-A
- WCAG21
- a11y-triaged
- accessibility
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-customer-escalated
- ax-desktop
- ax-esc-boa
- ax-high-priority
- ax-jira
- ax-jira-dc-vpat
- ax-jiradc-viewissue
- ax-macos-safari
- ax-platform-dc
- ax-qa
- ax-qa-bl
- ax-qa-prioritised
- ax-qa-verified
- ax-vpat-serious
- ax-windows-chrome
- ax-windows-firefox
- axsr-high-priority
- axsr-march-22
- ozghonnyk
-
8.2
-
Severity 2 - Major
Steps to reproduce:
- Navigate to and activate "Issues" link from left navigation region.
- With a screen reader running in background, navigate to "All", "Comments", "Worklog", etc. links under the "Activity" section.
Screenshot:
Actual behaviour:
Appropriate role and state is not defined for tab panel controls present under "Activity" section. The tabs appear as plain links to screen reader users and they are unaware of tabpanel being present on page.
Expected result:
- The <ul> element should have a role of "tablist" and the <li> elements present inside it should have role of "tab". This will ensure correct announcement of tab when the "All", "Comments", "Worklog", etc. links receive focus.
- The container displaying content for that tab should have a role of "tabpanel" and the container should be referenced with its respective tab control using "aria-controls" attribute.
For more details on implementation, refer https://www.w3.org/TR/wai-aria-practices/examples/tabs/tabs-2/tabs.html
AXQA Ref:AXQA-130
- is related to
-
JRASERVER-75371 Viewing an Issue: Link role not defined
-
- Closed
-
- mentioned in
-
Page Loading...
- relates to
-
COM-20 Loading...