You can click the color in the Color Contrast Calculator. This opens a color picker with a control that lets you select the color from anywhere from screen.
The accessibilityDifferentiateWithoutColor property isn't suggesting you should fallback to a black and white color scheme, it's suggesting that you should use shapes or glyphs to convey information instead of color.
To exemplify what @VaughnNicholson said, differentiating without color can be for something like required fields. Instead of saying "required fields are red" or "invalid fields have a red border and valid fields have a green border", at least use an additional indicator. You can still use those colors, but *also* put an icon or symbol to show the difference ("required fields have a red star" or "invalid fields are red and have a warning icon"). See WCAG 2.x 1.4.1: Use of Color
It's a really good lesson. Thank you for always providing great lectures.
You can click the color in the Color Contrast Calculator. This opens a color picker with a control that lets you select the color from anywhere from screen.
The accessibilityDifferentiateWithoutColor property isn't suggesting you should fallback to a black and white color scheme, it's suggesting that you should use shapes or glyphs to convey information instead of color.
To exemplify what @VaughnNicholson said, differentiating without color can be for something like required fields. Instead of saying "required fields are red" or "invalid fields have a red border and valid fields have a green border", at least use an additional indicator. You can still use those colors, but *also* put an icon or symbol to show the difference ("required fields have a red star" or "invalid fields are red and have a warning icon"). See WCAG 2.x 1.4.1: Use of Color