Is this a regression?
The previous version in which this bug was not present was
No response
Description
When you open the date picker you can easily use the arrow keys to navigate between the days of the month.
But if you use a screen reader (tested with nvda and the integrated one from windows) the arrow keys won't work properly anymore.
The reason is because the screen reader switches to browse mode instead of focus mode and catches the keyboard events. If you switch manually to the focus mode (in nvda its the nvda key + space) it works again.
Reproduction
Just try it in one of the examples at the official site https://material.angular.dev/components/datepicker/examples
- without screen reader: keyboard navigation works
- with screen reader: keyboard navigation won't work - you have to switch manually to focus mode
Expected Behavior
I expect the keyboard navigation to work regardless if a screen reader is active or not. It should also not be needed to manually switch to focus mode
Actual Behavior
- without screen reader: keyboard navigation works
- with screen reader: keyboard navigation won't work - you have to switch manually to focus mode
Environment
- Angular: 22
- CDK/Material: 22
- Browser(s): Chrome, Firefox
- Operating System: Windows 11
Is this a regression?
The previous version in which this bug was not present was
No response
Description
When you open the date picker you can easily use the arrow keys to navigate between the days of the month.
But if you use a screen reader (tested with nvda and the integrated one from windows) the arrow keys won't work properly anymore.
The reason is because the screen reader switches to browse mode instead of focus mode and catches the keyboard events. If you switch manually to the focus mode (in nvda its the nvda key + space) it works again.
Reproduction
Just try it in one of the examples at the official site https://material.angular.dev/components/datepicker/examples
Expected Behavior
I expect the keyboard navigation to work regardless if a screen reader is active or not. It should also not be needed to manually switch to focus mode
Actual Behavior
Environment