You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The issue occurs when using a date picker component with a custom input. Previously, up until version 6.2.0, the input field was accessible using findByRole combined with name, even when the calendar container was open. However, starting from version 6.3.0 (and persisting in 8.0.0), the input element is no longer accessible in this way when the calendar is open. Potential accessibility issues if screen readers also struggle to find the input.
To Reproduce
Create date picker component with custom input
Click / type / clear the input so the calendar container opens
Try to get / find input element when calendar container is opened
Expected behavior
Input should by accessible by findByRole in combination with name even though calendar container is opened. It works like this till 6.2.0. The first broken version if 6.3.0 and it is still not accessible in version 8.0.0
The text was updated successfully, but these errors were encountered:
Describe the bug
The issue occurs when using a date picker component with a custom input. Previously, up until version 6.2.0, the input field was accessible using findByRole combined with name, even when the calendar container was open. However, starting from version 6.3.0 (and persisting in 8.0.0), the input element is no longer accessible in this way when the calendar is open. Potential accessibility issues if screen readers also struggle to find the input.
To Reproduce
Expected behavior
Input should by accessible by
findByRole
in combination withname
even though calendar container is opened. It works like this till 6.2.0. The first broken version if 6.3.0 and it is still not accessible in version 8.0.0The text was updated successfully, but these errors were encountered: