Issue metadata
Sign in to add a comment
|
STS always reads buttons that are only visible on mouseover/focus |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 67.0.3383.0 (Official Build) dev (64-bit) Firmware Version Google_Samus.6300.276.0 Chrome OS with flag enabled: #enable-experimental-accessibility-features # Enable STS # Navigate to https://photos.google.com/ # Upload a photo if you don't have one present # Use search button + mouse to draw ring around photo Expected: photo information read once Actual: photo info read twice because of an invisible checkbox that only appears on mouseover or with ChromeVox linear navigation Please see this video for the repro and ChromeVox showing the checkbox (side note: please forgive the extraneous tabbing in the middle of the video): https://drive.google.com/file/d/1BXkxx-PlUKoiTCF2rke4VZA6hzQrP8_v/view Also, this is the outerHTML for this checkbox showing it's not a standard checkbox: <path d="M12 2C6.48 2 2 6.48 2 12s4.48 10 10 10 10-4.48 10-10S17.52 2 12 2zm-2 15l-5-5 1.41-1.41L10 14.17l7.59-7.59L19 8l-9 9z"></path> It has an ARIA role of checkbox which might be of interest here.
,
Apr 14 2018
Another place to see this is on notes in Google Keep. The buttons on notes are only visible on mouse hover but are read by STS no matter what. When using ChromeVox over these buttons, the buttons visually appear since focus is placed on them. Here's the HTML from those buttons: <div role="button" class="Q0hgme-LgbsSe Q0hgme-Bz112c-LgbsSe euCgFf INgbqf-LgbsSe VIpgJd-LgbsSe" aria-label="Collaborator" aria-disabled="false" style="user-select: none;" tabindex="0"></div>
,
Apr 14 2018
I'm bumping up to p2 because I'd imagine there are many other places where controls are only visible when focused upon. STS seeming to read buttons that aren't there does create confusion for the user.
,
Apr 14 2018
Also applies to YouTube - control buttons disappear while video is playing but STS still reads them.
,
Apr 14 2018
Also in YouTube the videos on the right have a hidden action menu that is read but only visible on mouse over.
,
Apr 14 2018
I also saw this UI in places on Facebook and Amazon. It seems to be a popular design choice. Please make this a higher p2. Thanks!
,
Sep 27
This bug is related to overflow and visibility. Select-to-Speak cannot determine when an element is visible or invisible if that is not reflected in the a11y tree. For example, a 1px by 1px element that is on the screen may be read whether or not it has overflow:hidden. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Apr 12 2018