Issue metadata
Sign in to add a comment
|
(web content) Inspection and select function is missing keyboard accessibility
Reported by
norman.b...@gmail.com,
Mar 21 2016
|
||||||||||||||||||||||
Issue description
Chrome Version : 47.0.2526.80
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Go to URL https://bugs.chromium.org/p/chromium/issues/entry?template
2. Keyboard tab to "Advanced Search".
3. Activate the Inspect functionality via right CTRL+Shift+I.
4. Note the Inspect: Elements source focuses on HTML source body class t2.
5. Close the Inspect function.
6. Right click on "Advanced Search" using the pointer.
7. Note the Inspect: Elements source focuses on Advanced Search in HTML source.
8. Place pointer over "select an element in the page to inspect it" (Ctrl + Shift + c) and activate inspect select function.
9. Select "Search tips".
10. Note the Inspect: Elements source focuses on HTML source "Search Tips".
11. Click on body of HTML content to gain keyboard focus in document.
12. Tab to "Saved queries".
13. Activate keyboard shortcut for inspect select function (Ctrl + Shift + c).
14. Inspect: Elements source is not updated. Keyboard focus is lost. Only pointer access is provided.
What is the expected result?
Content that currently has keyboard focus should be highlighted and focused in the Inspection: Elements pane. Activating the keyboard shortcut for Inspect select function should keep keyboard focus and allow selection of elements via Enter key (or any appropriate key to activate equivalent to selection with pointer).
What happens instead of that?
Inspection: Elements focus on first HTML body element, instead of actual element and providing the same behavior users have via right click using pointer. Keyboard access is lost. Inspect selection is only available via pointer selection.
Please provide any additional information below. Attach a screenshot if
possible.
Keyboard accessibility is required. People relying upon screen readers, keyboard access, or alternative device access due to mobility issues, cannot perform inspection or testing without assistive technology or additional software that includes emulation of a mouse, touchpad, or pointer control device.
I've read through the keyboard shortcuts and developer documentation but did not find any special configuration to modify this as an exception or configuration issue for the end-user as a work-around. Please beat me with a cluestick if I missed it, however I suggest is not found, and certainly should be a default product functionality without special configuration or special shortcuts.
UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.80 Safari/537.36
,
May 2 2016
,
Mar 28 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 4 2017
,
Aug 4 2017
,
Dec 14 2017
,
Dec 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 17
Joel, can we close this? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ashej...@chromium.org
, Apr 1 2016Labels: -Type-Bug Type-Feature
Status: Untriaged (was: Unconfirmed)