Notification role for accessibility |
||||
Issue descriptionCurrently notifications are treated as "buttons" in the context of accessibility. cf. https://cs.chromium.org/chromium/src/ui/message_center/views/message_view.cc?q=message_view.+package:%5Echromium$&l=116 I think it's good for us to have "notification" role instead.
,
Jun 1 2017
,
Jun 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/99d72b12adfe2db83d7f7dbd409794b73c265a10 commit 99d72b12adfe2db83d7f7dbd409794b73c265a10 Author: yoshiki <yoshiki@chromium.org> Date: Wed Jun 21 06:01:29 2017 Add an accessibility description for notification Previously, Chromevox speaks "button" on notification. With this CL, it changes to "notification". BUG= 728489 TEST=manual (chromevox speaks "notification" at notifications) Review-Url: https://codereview.chromium.org/2918483002 Cr-Commit-Position: refs/heads/master@{#481120} [modify] https://crrev.com/99d72b12adfe2db83d7f7dbd409794b73c265a10/ui/arc/notification/arc_notification_content_view.cc [modify] https://crrev.com/99d72b12adfe2db83d7f7dbd409794b73c265a10/ui/message_center/views/message_view.cc [modify] https://crrev.com/99d72b12adfe2db83d7f7dbd409794b73c265a10/ui/strings/ui_strings.grd
,
Jun 21 2017
,
Jul 6 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by yoshiki@chromium.org
, Jun 1 2017