New issue
Advanced search Search tips

Issue 788950 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug

Blocking:
issue 764125



Sign in to add a comment

MD Extensions: A11y: Low Contrast in Search Box

Project Member Reported by hcarmona@chromium.org, Nov 28 2017

Issue description

What steps will reproduce the problem?
1. Navigate to chrome://extensions
2. Run axe-core audit (go/axe-core-chrome-extension)
3. Search field will have low contrast

What is the expected result?
A11y audit should pass
 
Low Contrast.png
2.8 KB View Download
Same test passes in chrome://settings and fails in chrome://history and chrome://downloads

Comment 2 by dpa...@chromium.org, Nov 28 2017

Is there a chance that the test accidentally passes in chrome://settings? It seems to me that both Settings and Extensions have the exact same contrast. Does the tool output the observed contrast values to compare?

Comment 3 by dpa...@chromium.org, Nov 28 2017

Cc: hcarmona@chromium.org
From investigating this further, I've found that the color contrast test doesn't finish in settings, so doesn't fail >_<

The contrast issue seems to be that the foreground color is #fbfbfb and background color is #f1f1f1. This doesn't seem right from looking at the screenshot. I'm guessing it's an issue with the a11y check in axe-core.

I'm updating the extension so it shows incomplete tests as well as failures.

The colors that we have (taken from screenshot) will pass contrast tests except for WCAG AAA which requires 7:1 contrast ratio.
https://webaim.org/resources/contrastchecker/?fcolor=C0CAE3&bcolor=2E4FA3
Status: WontFix (was: Available)
Marking this issue as "WontFix" since it's a false positive from the a11y library. Reason this wasn't finishing in settings was that the page was scrolled and the audit couldn't determine the contrast of off-screen items. ¯\_(ツ)_/¯

Sign in to add a comment