Issue metadata
Sign in to add a comment
|
a11y dialogs: bounding box around non-highlighted buttons color too low contrast against background |
||||||||||||||||||||||||
Issue descriptionGoogle Chrome 66.0.3356.0 (Official Build) canary (64-bit) (cohort: Clang-64) Google Chrome 64.0.3282.167 (Official Build) (64-bit) (cohort: Stable) Note: there has been a change in UI between 64 and 66 but this issue affects both versions. This affects all dialogs on Mac and Windows where a focus ring appears. This is specifically for buttons without focus, focus ring on another button. The bounding box contrast is too low. Please see attached screenshots. Foreground (bounding box):#B1B1B1 Background:#FFFFFF The contrast ratio is: 2.1:1
,
Mar 5 2018
I'm not aware of a requirement for a specific contrast ratio for the focus ring. I couldn't find it in the WCAG. Please let me know if there is one. I don't think it's quite so simple to determine whether a focus ring is clear enough. I think the thickness matters too - a thin line with a lot of contrast is similar to a thick line with less contrast, for example. Also, the amount the focused object *changes* when focused is pretty important too.
,
Mar 6 2018
Good points there. It seems to be especially problematic for me when the item in focus doesn't change in response and/or the focus ring surrounds a similarly colored box. Here's an example: Focus not on My Account button: https://screenshot.googleplex.com/6WdLG87VpkB.png Focus on My Account button: https://screenshot.googleplex.com/BYd6ipjkEcR It's a pretty much imperceptible difference. A nice orange highlight ring like the one on Chrome OS is an example of one I like. I'm also bumping this down to p2 since it looks like it could be a false positive here given no WCAG requirement.
,
Mar 6 2018
,
Mar 6 2018
I discussed with dmazzoni@ and the problem here is not the strict ratio of the color of the bounding box to the background but instead the overall delta between focused and unfocused. This requires further UX exploration. Therefore, I'm going to dupe this bug into 819312. That way, the bug will capture the real issue and not the false positive here. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Feb 28 2018