-
Bug
-
Resolution: Done
-
High
-
8.20.1
-
- 4.1.2
- AXSR-13
- AXSR-20
- AXSR-26
- Level-A
- WCAG21
- accessibility
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-critical
- ax-critical-priority
- ax-customer-escalated
- ax-desktop
- ax-dev-ready
- ax-esc-dt
- ax-esc-jpmc
- ax-high-priority
- ax-jira
- ax-macos-safari
- ax-merged
- ax-platform-dc
- ax-qa
- ax-qa-bl
- ax-qa-prioritised
- ax-qa-verified
- ax-triaged
- ax-vpat-critical
- ax-windows-chrome
- ax-windows-firefox
- axsr-high-priority
- axsr-march-22
-
8.2
-
Severity 2 - Major
-
Issue Description
in "Create issue" modal dialog, The Calendar popup provided for "Due date" is not accessible with screen reader & keyboard-only users.
Similar issue is present in "Releases" page for "start date" & "release date" calendars.
Steps to reproduce
- Turn on screen reader and activate "Create" link from header region.
- Navigate to the "Select a date" element present near "Due date" input field & activate it with enter key.
- The calendar popup will open but the element inside popup can’t be navigated with keyboard.
Actual Behaviour
When screen reader users try to navigate in calendar component with up/down keys or Tab key, it is not responding i.e this calendar component is inaccessible for screen reader users.
When user activates the "Select a date" button the calendar popup is displayed. But the elements inside the popup such as "close", "Previous month", "Next month", etc can not be navigated with keyboard & screen reader doesn’t announce the contents.
Although when user press arrow keys the Different dates can be selected but screen reader doesn’t announce which date is currently focused.
This makes screen reader & keyboard users difficult to access the functionality of the Calendar effectively.
Expected Behaviour
When the popup opens the keyboard focus should go inside the popup contents. All the elements inside the Calendar popup such as "close", "Previous month", "Next month", etc should receive keyboard focus & screen reader should announce the elements.
Following code changes needs to be made.
- Provide role="dialog" & aria-label="Select date" to the parent <div> container of the popup.
- Mark the elements such as "Close", "Previous month", "Next month", etc as <button> elements.
- Provide clear & descriptive labels to these buttons.
- Mark the month text inside <h2> element & provide aria-live="polite" along with an unique id.
- Provide role="grid" & aria-labelledby to the <table> element.
- Provide aria-selected="true" to the currently selected date inside table.
- When user press up/down/left/right arrow keys to navigate to different dates, the screen reader should announce the date.
- Remove Following elements from <table> & <th> markup.
- Help
- September 2022
- close
- Previous year & Next year
- Previous Month & Next month
- Today
Refer to the following Example of Accessible Calendar popup.
https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/datepicker-dialog.html
Screenshot
Create Issue dialog
Releases page.
AXQA Ref:AXQA-184
- duplicates
-
JRASERVER-73448 Create issue modal dialog : Calender component inaccessible for screen reader and keyboard only users
-
- Closed
-
-
JRASERVER-73468 Create issue modal dialog : Calender component is inaccessible for screen reader users
-
- Closed
-
- is resolved by
-
JRASERVER-73446 Backlog : Calendar popup is inaccessible for screen reader & keyboard only users.
-
- Closed
-