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

Stepper and Stepper Item - Ensure parts of graphical objects essential for understanding content have sufficient contrast - (2036570235) #7839

Closed
dqateam opened this issue Sep 19, 2023 · 4 comments
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. design Issues that need design consultation prior to development. needs triage Planning workflow - pending design/dev review.

Comments

@dqateam
Copy link
Collaborator

dqateam commented Sep 19, 2023

Violation:

Ensure parts of graphical objects essential for understanding content have sufficient contrast

image

image

WCAG Reference:

Severity:

5

Media Type:

Color and Contrast


Areas for Remediation:

  • Title: Stepper and Stepper Item - Ensure parts of graphical objects essential for understanding content have sufficient contrast - (2036570235)
  • Module: Stepper and Stepper Item
    Issue
    The "Complete" icon with a color contrast ratio below 3.00:1, when checking with "Toggle theme" on.

Foreground: #1B6793
Background: #353535
Contrast ratio: 2.0:1

User Impact
Users with low vision will have difficulty identifying this content.

Suggestion
Ensure parts of graphical objects essential for understanding content have sufficient contrast. The required minimum contrast ratio is 3.00:1.

Common examples of qualifying objects include lines in a chart, meaningful icons, and annotations within an image.

Graphics that require particular presentation to preserve their meaning are exempt from this requirement.

To evaluate color contrast, see the Accessible Color Picker extension: https://www.accessibility.dev/


Additional Resources:

  • Report Source: Product accessibility evaluation conducted on the Calcite Design System in August, 2022.
@dqateam dqateam added 0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. needs triage Planning workflow - pending design/dev review. labels Sep 19, 2023
@geospatialem geospatialem added the design Issues that need design consultation prior to development. label Dec 27, 2023
@geospatialem
Copy link
Member

geospatialem commented Dec 27, 2023

The current contrast for the completed icon for our modes is:

Should we mitigate to different color schemes?

@geospatialem
Copy link
Member

For design consideration - is there an alternative color refer to the above comment we should provide for the "completed" icon, or since it is supplemental, should we close the issue? cc @SkyeSeitz @ashetland

@SkyeSeitz
Copy link

The optional icon prop is not essential for understanding status and considered an additive, decorative element for sighted users. For non-sighted users, can we confirm that AT is correctly providing status information?
Thanks so much!

@geospatialem
Copy link
Member

The optional icon prop is not essential for understanding status and considered an additive, decorative element for sighted users. For non-sighted users, can we confirm that AT is correctly providing status information?
Thanks so much!

Context is not currently provided to AT when the stepper has the icon attribute, and its children have status information, such as complete or error. Since its an unrelated issue, will close out the above, which refers to the color contrast and open a new issue to tackle for a11y context. There does not appear to be an existing issue.

@geospatialem geospatialem closed this as not planned Won't fix, can't repro, duplicate, stale Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. design Issues that need design consultation prior to development. needs triage Planning workflow - pending design/dev review.
Projects
None yet
Development

No branches or pull requests

3 participants