Does not count gradient as a background color about tota11y HOT 5 OPEN

There is no feasible way to check for the gradient programmatically, but the color error should still be valid because it falls under the same category as having an image there.

The way I see it is - if the background image didn't load (or if the gradient wasn't supported in that browser), the user would see the button's background-color. In this case, white, which fails a contrast check. In short, there should be an explicit background color on this button (even if the gradient overrides it) that has viable contrast. Scratch this, we're not reading the background-color if there's a gradient there.

Would be nice to communicate this to the user, though. Perhaps check for background-image and modify the error message to include the info I just wrote above?

from tota11y.

Oh. I forgot to mention. If you look at the css it does have an explicit
fallback background color that is valid. (it's strikes out because chrome
is is using background-image insted). So I guess that might be a bug?

But yeah if you can't check for the gradient colors, at least a check for
background-image with an explanation would be good. The explenations are
one of the great strengths of this project.
On 9 Jun 2015 17:04, "Jordan Scales" [email protected] wrote:

There is no feasible way to check for the gradient programmatically, but
the color error should still be valid because it falls under the same
category as having an image there.

The way I see it is - if the background image didn't load (or if the
gradient wasn't supported in that browser), the user would see the button's
background-color. In this case, white, which fails a contrast check. In
short, there should be an explicit background color on this button (even if
the gradient overrides it) that has viable contrast.

Would be nice to communicate this to the user, though. Perhaps check for
background-image and modify the error message to include the info I just
wrote above?

—
Reply to this email directly or view it on GitHub
#5 (comment).

from tota11y.

Oh, my mistake, you're absolutely right. Checking either end of the gradient is probably the best we can do.

from tota11y.

I went ahead and filed the first bit - descriptive error messages for background images - as its own issue in #6.

from tota11y.

GoogleChrome/accessibility-developer-tools#79

May need to leave it up to them.

from tota11y.