Issue metadata
Sign in to add a comment
|
STS reading buttons that aren't visible in Google Sites editor |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 67.0.3369.0 (Official Build) canary (64-bit) Firmware Version Google_Samus.6300.276.0 Flag enabled: #enable-experimental-accessibility-features Steps to repro: # Enable Select to Speak in Accessibility settings # In Google Drive, go to New > More > Google Sites # Once new site template launches, press ctrl + a to select all # Press search + s to start STS Expected: just text read Actual: buttons are read including buttons that aren't actually visible like Add Footer. The Add Footer button only becomes visible if mouse hovers over that area towards the bottom. It's also unclear to me if STS should be reading button labels at all or if it should only read text on screen.
,
Mar 19 2018
,
Mar 28 2018
The "Add footer" button appears to be aria-disabled:false and have a valid width/height in the automation tree. It doesn't have offscreen or invisible states. I don't know any other way we could recognize that this node isn't visible on the page using Automation API. Marking as P3 because it'd be nice to have but I don't think it's blocking, nor do I think it's straight forward to fix.
,
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 katie@chromium.org
, Mar 19 2018