a11y: mat-dialog description not read by NVDA in Chrome #10591
Assignees
Labels
Accessibility
This issue is related to accessibility (a11y)
area: material/dialog
G
This is is related to a Google internal issue
P3
An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Comments
|
Looks like this works correctly if you Disable the following NVDA settings under Preferences > Browse mode...
Still not great that this doesn't work with the default settings especially when the wai-aria modal dialog example works fine regardless. |
mmalerba
added
P3
|
CC @jelbourn since it's a little fuzzy how we should handle it on our end. |
|
@diminutivesloop could you clarify which example dialog you're referring to? It looks like the page you linked to has several as part of the example. |
|
@jelbourn Hmm... I checked the page and I'm not sure what you mean by several dialog examples. The demo I had in mind can be activated by clicking the Add Delivery Address button under the Modal Dialog Example. Does that help clarify? |
|
@crisbeto that example dialog is doing the same thing as our's with focus behavior; I think there's something else in play that's causing it to read the dialog's label on open, but I'm not sure what exactly. |
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Dec 15, 2018
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Dec 15, 2018
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Dec 15, 2018
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Dec 15, 2018
…readers Currently we focus the first focusable element inside a bottom sheet as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the bottom sheet content. These changes switch to focusing the bottom sheet container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the autoFocus option. Relates to angular#10591.
jelbourn
pushed a commit
that referenced
this issue
Dec 18, 2018
…readers (#14534) Currently we focus the first focusable element inside a bottom sheet as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the bottom sheet content. These changes switch to focusing the bottom sheet container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the autoFocus option. Relates to #10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jan 13, 2019
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
josephperrott
pushed a commit
to josephperrott/components
that referenced
this issue
Jan 14, 2019
…readers (angular#14534) Currently we focus the first focusable element inside a bottom sheet as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the bottom sheet content. These changes switch to focusing the bottom sheet container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the autoFocus option. Relates to angular#10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Apr 3, 2019
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
May 20, 2019
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
May 26, 2019
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jun 20, 2019
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
jelbourn
pushed a commit
that referenced
this issue
Sep 6, 2019
Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes #10591.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Dec 26, 2020
…ders Currently we focus the first focusable element inside a dialog as per the accessibility recommendations, however moving focus to the first item causes some screen readers not to read out the rest of the dialog content. These changes switch to focusing the dialog container by default which allows screen readers to read out everything. If users press tab, they'll land on the first tabbable element anyways. The old behavior can still be opted into via the `autoFocus` option. Fixes angular#10591.
|
Should've been resolved by #23085. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
When opening a Mat-Dialog via a screen-reader the specified description should be read in full before reading the dialog content or currently focused control. This happens as expected when using NVDA with the wai-aria modal dialog example.
What is the current behavior?
The dialog description is either not read at all or only read partially before NVDA abruptly switches to reading the auto-focused control.
What are the steps to reproduce?
mat-dialog-title: https://stackblitz.com/edit/mat-dialog-a11y-descriptionMatDialogConfig.ariaDescribedBy: https://stackblitz.com/edit/mat-dialog-a11y-description-ddagpeMatDialogConfig.ariaLabel: https://stackblitz.com/edit/mat-dialog-a11y-description-nx3hbhWhich versions of Angular, Material, OS, TypeScript, browsers are affected?
Material: 5.2.4
Chrome: 65.0.3325.181
NVDA: 2018.1
The text was updated successfully, but these errors were encountered: