-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Toggling radio buttons makes all of them appear checked to JAWS #9400
Comments
_Welcome to a11y @bradrich. |
AFAICT on the demo site, |
I will take a look at this asap. |
@bradrich - this will be merged in 1.1.2... so we have time. |
@bradrich have you been able to reproduce? |
Running through a series of tests prove that there is indeed something wrong with our radio button system when accessed by a screen reader. Here is what I found: Mac OS 10.11.6
Windows 10 64 bit
The biggest difference between our radio button structure and that of the other test website is that our radio buttons are built with one HTML element: <input id="overnight" type="radio" name="shipping" value="overnight">
<label for="overnight">Overnight</label><br> I am investigating ways to correct this problem. Any suggestions would be appreciated. |
@crisbeto - can you pair with Brad here? |
I couldn't reproduce it with JAWS 17.0 on Windows @jelbourn. It properly read out everything as not checked and if I provided a pre-filled checked value it also worked. |
I managed to track this one down. It's because of |
…value * Fixes all of the radio buttons within a radio group having `aria-checked` set to true on load, when using `ng-value`. * Cleans up the `radioButton` directive. Fixes angular#9400.
Seems like ngAria always ends up doing the wrong thing when you're already mindful of a11y... Nice debugging. |
…value * Fixes all of the radio buttons within a radio group having `aria-checked` set to true on load, when using `ng-value`. * Cleans up the `radioButton` directive. Fixes angular#9400.
Have a report that, with an
<md-radio-group>
, all of the options are appearing checked at the same time with JAWS. We should investigate with IE11, Edge, Chrome, and Firefox.The radio button template looks something like
The text was updated successfully, but these errors were encountered: