question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItĀ collects links to all the places you might be looking at while hunting down a tough bug.

And, if youā€™re still stuck at the end, weā€™re happy to hop on a call to see how we can help out.

[Carbon 10 šŸ”˜ ] Radio Button WCGA 2.1 Guideline 1.4.1 violation

See original GitHub issue

1.4.1 Use of Color Level A violation by C10 radio button

Browser

Firefox

Detailed description

What version of the Carbon Design System are you using?

v 10.25.0 carbon-components-react v 7.25.0

What did you expect to happen?

ā€œColor is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.ā€ We should still see the radio button selected after removal of color or the implementation of another technique: ā€œSituation A: If the color of particular words, backgrounds, or other content is used to indicate information: G14: Ensuring that information conveyed by color differences is also available in text G205: Including a text cue for colored form control labels G182: Ensuring that additional visual cues are available when text color differences are used to convey information G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify themā€

What happened instead?

Button selected versus unselected states look the same after color removal.

What WCAG 2.1 checkpoint does the issue violate?

1.4.1 Use of Color Level A

Steps to reproduce the issue

Issue can be tested in CDS storybook: image

In Firefox Fonts & Colors settings select System Colors and set ā€œOverride the colors specified by the page with your selections aboveā€ to ā€œAlwaysā€ image

Click one of the radio buttons. User cannot see button selected. image

Instructions to remove color may vary between browser. Additional guidance to configure the browser to ignore colored text:

FirefoxĀ®:

Select Tools > Optionsā€¦ On the Content tab, in the Fonts & Colors section, select the Colorsā€¦ button. In the Colors dialog box, select the Use system colors checkbox and deselect the Allow pages to choose their own colors, instead of my selections above checkbox. Select OK to save changes. Select OK to exit the Options dialog box. For Internet ExplorerĀ®:

Select Tools >Internet Options. On the General tab, in the Appearance section, select the Accessibility button. Check the box Ignore Colors Specified on Web Pages and select OK. On the General tab, in the Appearance section, select the Colors button and ensure that the checkbox Use Windows colors is selected and select OK to save this setting. Select Apply and OK to save changes. Note for iOS platform: Mobile Safari does not support removing color from text. Therefore, use a desktop browser to perform the required unit tests.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
dakahncommented, Jun 16, 2021

That same doc also specifies the method for Edge šŸ˜ƒ.

Yes, with the use of a browser extension. But without third party tooling Chromium browsers donā€™t support this use case ā€“ which was the point I was making. That said, the Chromium browser extension recommended in those docs will desaturate the page (make it grayscale) which would potentially allow someone to see a 1.4.1 violation for requiring a user to perceive or distinguish color šŸ‘šŸ½

Our squad has to use Carbon and we simply need to pass and be compliant.

Completely understand where youā€™re coming from. The reason this issue remains closed is because this testing methodology doesnā€™t actually ensure 1.4.1 compliance. There could be something fundamental I donā€™t understand about 1.4.1 and if thatā€™s the case Iā€™m happy to reopen. ā˜®ļø

Although its not well documented I think this setting simply imports Windows foreground, background, and link color values from the OS. Which if thatā€™s the case thereā€™s no reason this setting should be overwriting that SVG fill on the selected radio. Meaning instead of a 1.4.1 violation what youā€™ve potentially found is an upstream bug with this Firefox setting.

1reaction
Majavitacommented, Jun 16, 2021

@dakahn That same doc also specifies the method for Edge šŸ˜ƒ. They just expect the radio button center dot to stay visible. You disagree with the Accessibility teamā€™s directions and therefore with AVTā€™s use of this to open accessibility defects.
image I have shared your disagreement in the channel already and shall wait for their decision. Will tag you to the comment. Other non-Carbon radio buttons and toggles do a better job, but Iā€™ll let the Design folks escalate. Our squad has to use Carbon and we simply need to pass and be compliant.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Web Content Accessibility Guidelines (WCAG) 2.1 - W3C
2.1 defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, includingĀ ...
Read more >
Radio button not accessible in High Contrast #7280 - GitHub
Detailed description. User should be able to tell which radio button is selected. What WCAG 2.1 checkpoint does the issue violate?
Read more >
Radio button - Carbon Design System
Use radio buttons when you have a group of mutually exclusive choices and only one selection from the group is allowed.
Read more >
WCAG 2.1 Guidelines Explained with Examples | The C2 Group
Overall, WCAG 2.1 provides 17 new success criteria as guidance for mobile device users by supporting interactions using touch, handling moreĀ ...
Read more >
If I display a hidden button, based on a radio button selection ...
Even if you don't use assistive technologies, hiding the "Continue" button may be confusing, as it sounds like an essential action that isĀ ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found