Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.4.11: Gradient Backgrounds #1862

Closed
benja11y opened this issue Jun 10, 2021 · 3 comments · Fixed by #1967
Closed

2.4.11: Gradient Backgrounds #1862

benja11y opened this issue Jun 10, 2021 · 3 comments · Fixed by #1967

Comments

@benja11y
Copy link
Member

benja11y commented Jun 10, 2021

The understanding document goes into detail on how to approach gradational focus indicators, but no examples have been given describing how to handle gradational backgrounds. Pages that have a non-solid background image covering the whole page or make use of parallax scrolling effects will result in a near-infinite number of color combinations if a page is scrolled and/or changes are made to the viewport size.

How can this be addressed pragmatically to benefit users without causing undue burden on testers at the same time?

This issue has been raised on behalf of TPGi, based on an internal consultation process. An article containing all of our comments can be found on our blog, along with an introduction and acknowledgments.

@alastc
Copy link
Contributor

alastc commented Jun 10, 2021

Would it not be the same as for text-contrast for text on a gradient background?

I.e. there isn't a programmatic method (yet), but it is fairly easy to manipulate the page to find the worst-case, and test that.

@alastc alastc added this to To do in WCAG 2.2 via automation Jun 10, 2021
@mraccess77
Copy link

My personal opinion is that if the contrast of background colors that change are close enough to need to be tested for each combination then they would likely not meet the user need of people with low vision in certain scroll combinations and would likely fail in certain combinations as well. I agree that the text would have the same issue today under SC 1.4.3. In these cases it would be an easy solution to use a double ring focus indicator or some other mechanism to indicate focus such as a solid box with a border to guarantee there is sufficient contrast across variations of background images or background gradients.

@DavidMacDonald
Copy link
Contributor

DavidMacDonald commented Jul 2, 2021

Agree with @mraccess77 that this is the same issue as 1.4.3 currently.

I suggest adding the following to the Understanding:

Some designs have pages with a non-solid background image covering the whole (or part) of the page or make use of parallax scrolling effects which result in a near-infinite number of color combinations if a page is scrolled and/or changes are made to the viewport size. If the contrast of background colors that change are close enough to need to be tested for each combination then they would likely not meet the user need of people with low vision in certain scroll combinations and would likely fail in certain combinations as well. In these cases it would be an easy solution to use a double ring focus indicator or some other mechanism to indicate focus such as a solid box with a border to guarantee there is sufficient contrast across variations of background images or background gradients.

WCAG 2.2 automation moved this from To do to Done Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
WCAG 2.2
  
Done
Development

Successfully merging a pull request may close this issue.

4 participants