Role is not defined for the 'Long event' button present in calendar in Windows. #2776
Description
Check that this is really a bug
- I confirm
Reproduction link
https://jquense.github.io/react-big-calendar/examples/index.html?path=/docs/about-big-calendar--page
Bug description
Test Environment:
OS: Windows 11 Version 24H2(OS Build 26120.1930)
Browser: Edge Version 131.0.2903.112 (Official build) (64-bit)
Screen reader: NVDA Version 2024.4.2
URL: https://jquense.github.io/react-big-calendar/examples/index.html?path=/docs/about-big-calendar--page)
User Impact:
Screen reader users will get impacted as they will not be able to understand the purpose of the control and get the information properly if Screen reader is not announcing the role for the control.
Observation:
This issue is observed with all three screen readers.
Pre-Requisites:
1.Turn on Screen Readers:
NVDA: Ctrl + Alt + N
2.Verbosity:
NVDA: Default
Repro steps:
- Open the URL: https://jquense.github.io/react-big-calendar/examples/index.html?path=/docs/about-big-calendar--page in the latest browser.
- 'Big calendar' page will open.
- Verify using arrow keys whether name is provided, and correct role is provided for "Long event" button in Landing screen or not.
Refer Attachment:
- Role is not defined for the 'Long event' button present in calendar in Windows.png
- Role is not defined for the 'Long event' button present in calendar in Windows.mp4
https://github.com/user-attachments/assets/9c0e0bb1-e751-4688-a3e2-cb154087e7a4
Expected Behavior
On pressing arrow key when focus moves to the 'long event' control, Screen reader should announce it as 'Clickable long event button' in Windows.
Actual Behavior
On pressing arrow key when focus moves to the 'long event' control, screen reader announces it as 'Clickable long event' in Windows.
react-big-calendar version
1.19.0
React version
18
Platform/Target and Browser Versions
Edge Version 131.0.2903.112 (Official build) (64-bit)
Validations
- Read the docs.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
- Make sure this is a react-big-calendar issue and not an implementation issue
Would you like to open a PR for this bug?
- I'm willing to open a PR