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

A11y: Global Styles - Light Mode Warning Yellow not hitting contrast ratio standard #3145

Closed
rmstinson opened this issue Sep 30, 2021 · 22 comments
Assignees
Labels
4 - verified Issues that have been released and confirmed resolved. a11y Issues related to Accessibility fixes or improvements. design Issues that need design consultation prior to development. docs Issues relating to documentation updates only. p - low Issue is non core or affecting less that 10% of people using the library ready for dev Issues ready for development implementation. research Issues that require more in-depth research or multiple team members to resolve or make decision.

Comments

@rmstinson
Copy link

Light mode warning yellow doesn't hit contrast ratio standards on a white background. Dark mode warning yellow is fine as long as it's on the prescribed background colors.
Screen Shot 2021-09-30 at 3 46 43 PM

Recommend we use the dark yellow #7D7227 we use for headlines and links on the homepage as part of the out-of-the-box yellow theme option. It's kind of ugly but it's as close to yellow as we can get without it being completely brown:

Screen Shot 2021-09-30 at 3 46 53 PM

Thoughts?

@rmstinson rmstinson added bug Bug reports for broken functionality. Issues should include a reproduction of the bug. a11y Issues related to Accessibility fixes or improvements. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Sep 30, 2021
@rmstinson rmstinson self-assigned this Sep 30, 2021
@github-actions
Copy link
Contributor

More information is required to proceed with this issue:

This issue will be automatically closed in three days if the information is not provided. Thanks for your understanding.

@github-actions github-actions bot added the need more info Issues that are missing information and/or a clear, actionable description. label Sep 30, 2021
@macandcheese
Copy link
Contributor

This came up in a previous issue and because the icon / accent bar color is purely decorative - and the text content itself should convey severity - it was deemed non-actionable: #994 (comment)

I'll leave this issue open if others want to chime in here.

@benelan benelan added need more info Issues that are missing information and/or a clear, actionable description. and removed need more info Issues that are missing information and/or a clear, actionable description. labels Oct 1, 2021
@rmstinson
Copy link
Author

@macandcheese Gotcha! I'm wondering tho, if an icon isn't unimportant enough to not be legible for some users, should we be using the icon at all? It feels like it's not just an accessibility issue, the globe icons in the chips are barely legible to me and I don't have any visual impairments.

Screen Shot 2021-10-01 at 3 28 16 PM

It seems to me like we should reassess, since it's the only global style we have in the set.

@macandcheese
Copy link
Contributor

Yeah, maybe we could look at adjusting the yellow value (although, if the result of that is a brown-yellow, folks will likely just override it). As far as using the icon - it's already opt-in / user-overridable so it is ultimately up to the implementing design team.

since it's the only global style we have in the set.

What do you mean by this?

@benelan benelan removed the need more info Issues that are missing information and/or a clear, actionable description. label Oct 4, 2021
@rmstinson
Copy link
Author

since it's the only global style we have in the set.

@macandcheese Must have lost a word in editing should be "since it's the only inaccessible global style."

@rmstinson
Copy link
Author

Warning Icons

Discussing it with @mitc7862 and other members of the design team, we got a lot of consensus around this direction - maintaining the yellow color theme, while keeping the warning icon as the default gray to ensure legibility - icons that are emphasizing messaging need to hit at least a 3:1 contrast ratio.

Hopefully this strategy can banish the gold/brown direction for all time

@macandcheese
Copy link
Contributor

Per conversation with @rmstinson and @mitc7862 - design work / proposal to follow.

@macandcheese macandcheese added the design Issues that need design consultation prior to development. label Oct 5, 2021
@benelan benelan added this to the Sprint 10/11 – 10/22 milestone Oct 6, 2021
@benelan benelan removed the needs triage Planning workflow - pending design/dev review. label Oct 6, 2021
@jcfranco
Copy link
Member

@macandcheese Any update on the design work/proposal?

@macandcheese
Copy link
Contributor

@jcfranco not yet - needs to be done in coordination with the dark theme update to ensure any new colors work then. This should be pre v1 for sure but no immediate work has been done.

@jcfranco
Copy link
Member

Got it. Thanks for the info!

@benelan We should probably adjust the milestone of this one since #3122 is in the Freezer. WDYT?

@benelan
Copy link
Member

benelan commented Oct 15, 2021

Yeah I agree, they should be together. I think we should freeze this one and add it to the v1 priorities project.

@jcfranco
Copy link
Member

the_shining_-jack-frozen

@geospatialem geospatialem added the enhancement Issues tied to a new feature or request. label Jul 12, 2022
@geospatialem geospatialem removed the 0 - new New issues that need assignment. label Jul 12, 2022
@geospatialem geospatialem added docs Issues relating to documentation updates only. and removed enhancement Issues tied to a new feature or request. labels Mar 3, 2023
@geospatialem
Copy link
Member

I believe we satisfy the AA req since the use of warning yellow is on secondary items (e.g. icons) and the "warning" itself would be written in the text. Even in the Chip example above, if the yellow Chip is meant to be a warning of some kind, that would be communicated in the chip text and the yellow border would be secondary to communicating that information.

With the above, we believe to be adhering to the a11y success criterion. @SkyeSeitz and @ashetland verified Figma documentation provides guidance for designers.

Additional research will be conducted to determine if additional documentation is needed to ensure devs do not rely on color alone, and provide additional supporting text content.

@geospatialem geospatialem added the research Issues that require more in-depth research or multiple team members to resolve or make decision. label Mar 3, 2023
@geospatialem
Copy link
Member

Removing the design label as research has been conducted previously.

@geospatialem geospatialem removed the design Issues that need design consultation prior to development. label Mar 17, 2023
@yelenakreyndel
Copy link

@geospatialem Aaron and I were wondering if this issue is good to be closed or if something else is needed?

@geospatialem
Copy link
Member

@yelenakreyndel Yes, didn't comment on this sooner, but I assigned myself to determine if the documentation site needs to be modified to ensure we mention color should not be the only means to convey information on our site. Reassigned to the April milestone to tackle.

@geospatialem geospatialem added the p - low Issue is non core or affecting less that 10% of people using the library label Apr 13, 2023
@geospatialem geospatialem added ready for dev Issues ready for development implementation. 2 - in development Issues that are actively being worked on. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels May 4, 2023
@geospatialem
Copy link
Member

Added a section to the the accessibility page on color considerations, anticipated in next Wednesday's doc release on Wed May 10.

@geospatialem geospatialem added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 2 - in development Issues that are actively being worked on. labels May 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented May 5, 2023

Installed and assigned for verification.

@geospatialem geospatialem added 4 - verified Issues that have been released and confirmed resolved. and removed 3 - installed Issues that have been merged to master branch and are ready for final confirmation. labels May 5, 2023
@geospatialem
Copy link
Member

Verified on next.sites on the accessibility page - targeted for release on Wed May 10.

verify-a11y

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 - verified Issues that have been released and confirmed resolved. a11y Issues related to Accessibility fixes or improvements. design Issues that need design consultation prior to development. docs Issues relating to documentation updates only. p - low Issue is non core or affecting less that 10% of people using the library ready for dev Issues ready for development implementation. research Issues that require more in-depth research or multiple team members to resolve or make decision.
Projects
None yet
Development

No branches or pull requests

9 participants