Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Feat: <md-aria-status> directive to be consumed by mdToast and mdAutocomplete #3174

Closed
marcysutton opened this issue Jun 8, 2015 · 4 comments
Assignees
Labels
- Breaking Change a11y This issue is related to accessibility P4: minor Minor issues. May not be fixed without community contributions.
Milestone

Comments

@marcysutton
Copy link
Contributor

To enable $mdToast accessibility, Angular Material needs a global version of the <aria-status> directive used in mdAutocomplete. A single Live Region directive for an entire app, which could be used by multiple components as a reusable message center. It would also make screen reader messages easier to localize, per #1696. This should be part of the core functionality to ensure its inclusion for Angular Material components, though I could see a message service being useful for other live regions.

mdAutocomplete uses aria-live="assertive" so that messages will be announced immediately as you type, but I'm investigating whether it can use aria-live="polite", which would be more appropriate for mdToast. Components using the global directive will have to share live region settings, as far as I know (role, atomic, relevant, etc.).

@marcysutton marcysutton added the a11y This issue is related to accessibility label Jun 8, 2015
@marcysutton
Copy link
Contributor Author

The announce feature of this library could be useful: https://github.com/dequelabs/ngA11y/blob/master/src/nga11yannounce.js

@ThomasBurleson ThomasBurleson modified the milestone: Backlog Jul 6, 2015
@ThomasBurleson ThomasBurleson modified the milestones: 0.12.0, Backlog Sep 4, 2015
@naomiblack
Copy link
Contributor

@jelbourn it would be really nice to do this in 1.0 bc of breaking change (and overall a11y), but I'm concerned about time needed to get it right. Do you think this is something you could squeak in along with other m12 tasks on your plate?

@jelbourn
Copy link
Member

jelbourn commented Sep 8, 2015

@marcysutton Could you elaborate on the problems with having multiple live regions on a page?

@marcysutton
Copy link
Contributor Author

@jelbourn if there are multiple live regions doing the same thing on a page (and with the same politeness level), they can cause confusion in a screen reader–especially if we can't control how many components are used that require announcements. It makes sense for Angular Material to handle messages centrally to reduce complexity under the hood and optimize for assistive technology. Here is a little more info and a solution that seems to work but may need some more testing in IE: http://spa-a11y.divshot.io/#14

@jelbourn jelbourn modified the milestones: 0.12, 0.13 Oct 15, 2015
@ThomasBurleson ThomasBurleson modified the milestones: 1.0-rc2, 1.0-rc3 Oct 30, 2015
@ThomasBurleson ThomasBurleson modified the milestones: 1.0-rc3, 1.0-rc4 Nov 7, 2015
@ThomasBurleson ThomasBurleson modified the milestones: 1.0-rc4, 1.0-rc5 Nov 16, 2015
@ThomasBurleson ThomasBurleson removed this from the 1.0-rc5 milestone Nov 25, 2015
@ThomasBurleson ThomasBurleson modified the milestones: 1.0-rc6, 1.0-rc5, 1.0-rc7 Nov 25, 2015
@ThomasBurleson ThomasBurleson modified the milestones: 1.0-rc7, 1.0-rc8 Dec 13, 2015
@ThomasBurleson ThomasBurleson modified the milestones: 1.0-rc8, 1.1.0, Backlog Jan 5, 2016
@ThomasBurleson ThomasBurleson added P4: minor Minor issues. May not be fixed without community contributions. and removed priority: medium labels Jan 15, 2016
@ThomasBurleson ThomasBurleson modified the milestones: - Backlog, Deprecated Apr 26, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
- Breaking Change a11y This issue is related to accessibility P4: minor Minor issues. May not be fixed without community contributions.
Projects
None yet
Development

No branches or pull requests

4 participants