Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Hello,
since I am blind, I use a screenreader, primarily relying on my Braille display (speech is nice to have, but I often work without it).
I've reproduced this bug using both Firefox and Google Chrome on Windows 101, with Jaws screenreader version 2023.
When interacting with a mat-select element using up and down arrow keys, the changed value isn't displayed on the Braille display. However, this can only be reproduced when just tapping onto the select and pressing the arrow keys. When expanding the dropdown first (using either the enter key or the mouse), the values change as expected. This means a downgrade from the native select, since there the bug doesn't exist. Both variants can be found on given REPL link.

Reproduction

The interactive example in this Angular documentation can be used to reproduce:
https://material.angular.io/components/select/overview

Steps to reproduce:

1. Turn on Jaws screenreader and either connect a Braille display, or use the Braille viewer
2. Tap to the mat-select (don't expand it as described above), and press up and down arrow keys

Expected Behavior

Selected option on the Braille display changes synchronized to the actual value on screen.

Actual Behavior

The value on the screen gets asynchronous from the value on the Braille display. Changes are sent through as flash messages, but once they disappear we're out of sync, so following the convention would be better here.
Continue tapping until you get to the native select on the same page, and there you find it working as it should.

Environment

• Angular: 15.2.9
• CDK/Material: Wasn't displayed when running ng version
• Browser(s): Firefox 116.0.3, Google Chrome 116.0.5845.111
• Operating System (e.g. Windows, macOS, Ubuntu): Windows11