Issue metadata
Sign in to add a comment
|
Accessibility: Automatic Clicks Improvements Needed |
||||||||||||||||||||||||
Issue descriptionOS: Chrome M52.0.2723.2 What steps will reproduce the problem? (1) Navigate to settings > accessibility (2) Enable the feature "automatically click when the pointer stops" (3) Set the delay before click to very long Notice that "very long" really has no difference from long or even short. Some users may need to extend this considerably -- by multiple seconds, to ensure that they are able to position the pointer in the right place before it clicks. We need a better range here, and it would also be helpful to indicate the amount of seconds each level is (e.g. very short = .2 seconds, short = .5 seconds, very long = 4 seconds, etc.). It's pretty vague right now and makes the user have to try out all of the options to determine which is best. (But for now, many are too similar to be able to tell the difference anyway, IMO). The second part of this bug is more of a request. We received feedback from motor impaired users that they want to have a focus ring drawn around what will be clicked. Some other services (e.g. head tracking systems) operate this way -- you move the pointer with head tracking or a joystick, or whatever tool you are using, then you pause over a given item and a circle is drawn. The best way to do this would actually be to show progress of loading a circle all the way around, to give visual indication for how much time is left in the hover before it clicks. So, you could start the animation at the top of a circle and move counterclockwise around until the circle is closed, indicating the click.
,
May 11 2016
,
May 11 2016
,
May 14 2016
Started may 11.
,
May 16 2016
lpalmaro@chromium.org this is what i have so far for the request. Let me know if you have any feedback.
,
May 16 2016
CC'ing dmazzoni@
,
Jun 24 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a commit 820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a Author: sammiequon <sammiequon@chromium.org> Date: Fri Jun 24 18:47:13 2016 Show a visual indicator for the progress of auto-click. BUG= 610476 CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2016073004 Cr-Commit-Position: refs/heads/master@{#401913} [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/ash/autoclick/autoclick_controller.cc [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/ash/autoclick/autoclick_controller.h [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/ash/autoclick/autoclick_unittest.cc [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/app/chromeos_strings.grdp [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/chromeos/accessibility/accessibility_manager.cc [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/chromeos/accessibility/accessibility_manager.h [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/chromeos/preferences.cc [add] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/chromeos/ui/autoclick_ring_handler.cc [add] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/chromeos/ui/autoclick_ring_handler.h [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/resources/options/browser_options.html [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/resources/settings/a11y_page/a11y_page.html [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/browser/ui/ash/ash_init.cc [modify] https://crrev.com/820646ff0c3aa9fb6ea4d8ff727e9f5b02b1ca2a/chrome/chrome_browser_chromeos.gypi
,
Jun 24 2016
,
Jul 1 2016
,
Jul 18 2016
I think we should update the strings to use seconds, not milliseconds. The current (new) strings are: * extremely short (600 ms) * very short (800 ms) * short (1000 ms) * long (2000 ms) * very long (4000 ms) IMO "4s" is friendly than "4000 ms". Also, as a nit, 600ms is not really "extremely short". :-\
,
Jul 20 2016
I agree with the comments in #10. Reopening to further discuss.
,
Sep 23 2016
lpalmaro@ Should I change to as #10 suggested or is further discussion needed.
,
Oct 24 2016
Yes, I think this sounds great. Thank you!
,
Oct 24 2016
Just chatted with Sammie a bit more and we decided that we should make this even more relatable for our users and write everything in seconds: 4s, 2s, 1s, .8s, .6s instead of writing these in ms. We will plan to move forward with this unless anyone objects.
,
Oct 25 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/064a1ca8e1b1f3d7f5c6e315598d638c55a0fc6e commit 064a1ca8e1b1f3d7f5c6e315598d638c55a0fc6e Author: sammiequon <sammiequon@chromium.org> Date: Tue Oct 25 18:55:49 2016 cros: Updated autoclick section for md-settings. Changed autoclick options strings. Also made autoclick options disabled when autoclick is not enabled. BUG= 610476 , 629425 TEST=none CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2449643002 Cr-Commit-Position: refs/heads/master@{#427429} [modify] https://crrev.com/064a1ca8e1b1f3d7f5c6e315598d638c55a0fc6e/chrome/app/chromeos_strings.grdp [modify] https://crrev.com/064a1ca8e1b1f3d7f5c6e315598d638c55a0fc6e/chrome/app/settings_strings.grdp [modify] https://crrev.com/064a1ca8e1b1f3d7f5c6e315598d638c55a0fc6e/chrome/browser/resources/options/browser_options.html [modify] https://crrev.com/064a1ca8e1b1f3d7f5c6e315598d638c55a0fc6e/chrome/browser/resources/settings/a11y_page/manage_a11y_page.html [modify] https://crrev.com/064a1ca8e1b1f3d7f5c6e315598d638c55a0fc6e/chrome/browser/resources/settings/a11y_page/manage_a11y_page.js
,
Oct 25 2016
,
Oct 31 2016
verified on 56.0.2903.0 |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by lpalmaro@chromium.org
, May 10 2016