-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Highest
-
Affects Version/s: 7.17.1
-
Component/s: Accessibility
-
- 1.3.1
- AXSR-30
- Accessibility
- Level-A
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-confluence
- ax-confluence-calendar
- ax-confluence-dc-2022-vpat
- ax-confluence-dc-vpat
- ax-confluence-dc-vpat-calendar
- ax-confluence-dc-vpat-pg09
- ax-critical
- ax-critical-priority
- ax-customer-escalated
- ax-esc-apple
- ax-qa
- ax-qa-verified
- ax-triaged
- ax-windows-chrome
- samurai
- spike-needed
-
Severity 3 - Minor
Issue Summary
The dates in the table are announced with incomplete information to the screen reader user making them unaware of the date they are on.
Screen Recording
Screen Recording 2022-05-11 at 2.00.15 PM.mov![]()
Steps to Reproduce
- Navigate to the main content area where the calendar for the space is present.
- Navigate to the calendar region keeping the screen reader on and navigating between the dates.
Actual Results
In the calendar table, when the user navigates within the dates in the read mode with the screen reader, the user is not able to understand the whole content of the table. The screen reader announces it such as "Row 3 of 7 7" - for May 7, 2022, Sat.
Additionally, if there is any event added to the date it is not announced together.
This will not make the assistive technology user understand on which date the user is interacting and will create confusion for them.
Expected Results
When the user navigates into the Calendar, the screen reader user should announce the whole date and the content available in the data table. If the data contains any event present that is associated with it, it should be announced as well.
An aria-label or aria-labelledby with a value such as "May 7, 2022, Sat" could be associated with the table row which will clearly suggest the date correctly.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...