Issue metadata
Sign in to add a comment
|
A11y tree rendered as one long line for screen reader on chrome://accessibility |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 70.0.3524.2 (Official Build) dev (64-bit) Firmware Version Google_Lulu.6301.136.57 # Launch ChromeVox with ctrl + alt + z # Navigate to chrome://accessibility # Click "show accessibility tree" for any tab (except chrome://accessibility, see bug 877714) # Tree expands # Linear navigate into the tree Expected: tree is rendered as multiple lines to allow for easier navigation Actual: entire tree is one line
,
Aug 25
,
Aug 27
There are newlines ('\n') between each line of the tree, but that doesn't cause the tree to be split into one node per line in the accessibility tree.
I'm wondering whether that is something we should address at the tree computation level - since a newline will cause a line break for a sighted user, should it start a new text node in the tree?
If not, we can probably just wrap <p></p> tags around each line in the <pre> containing the tree, and make appropriate CSS changes to ensure the appearance remains the same.
,
Sep 14
,
Sep 14
,
Sep 17
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Aug 24