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

Non-text contast - Adjacent colors and example clarifications. #681

Merged
merged 6 commits into from
Jul 30, 2019

Conversation

alastc
Copy link
Contributor

@alastc alastc commented Apr 3, 2019

Updating the explanation of Adjacent colors based on this email thread.

Also:

  • Added a couple of clarifications on the example descriptions from @mbgower.
  • Removed the text-based techniques from the techniques section, as they aren't specifically for non-text contrast. However, a note has been added in the 'required for understanding' section cross-referencing text contrast.

Preview on statically.

@alastc alastc changed the title Adjacent colors, and example clarifications. Non-text contast - Adjacent colors and example clarifications. Apr 3, 2019
alastc added 2 commits April 3, 2019 16:55
And adding a cross-reference note in ‘required for understanding’
@Myndex
Copy link
Member

Myndex commented Apr 14, 2019

Hi Alastair,

The terms "brightness" and "luminance" are not interchangeable. Brightness is a perceptual quality, luminance is a measurable quantity. As such, I suggest removing the parenthetical (luminance) at the end of the sentence.

I'd like to mention that drop shadow, outlines & borders are often not just ornamental, but used to enhance perceptual contrast. In that regard they should indeed be used as part of a contrast assessment. However the equations listed in the W3C understanding section on contrast are not useful for such assessment.

I'm not certain that "subsumed" is correct, more like "while multiple colors used in borders and drop shadows can have an effect on total perceived contrast, there is not a practical way to define this programatically. As such the designer should be cautious and use appropriate judgement to ensure adequate contrast."

An "Image Appearance Model" such as ICAM might be able to do this programmatically, but otherwise requires judgment on the part of the designer. This is related to a separate issue I recently opened for discussion. xref w3c/wcag3#192

@alastc
Copy link
Contributor Author

alastc commented Apr 17, 2019

Brightness is a perceptual quality, luminance is a measurable quantity.

I trust that is correct, but luminance is not a well known term. Brightness is a well known term, and the closest I know of to describe how someone would perceive luminance.

We use a luminance measure, but what (common) term would you use to convey that?

We could say something like this, but it seems unnecessarily wordy:

color closest in brightness (measured by luminance)

On this part:

I'm not certain that "subsumed" is correct, more like ...

That misses the point of the section, it is trying to say that you can ignore certain colors for the calculation. That should make it easier to measure. If you look at the rendered version I think that's clear.

@Myndex
Copy link
Member

Myndex commented Apr 19, 2019

Brightness is a perceptual quality, luminance is a measurable quantity.

I trust that is correct, but luminance is not a well known term. Brightness is a well known term, and the closest I know of to describe how someone would perceive luminance.

We use a luminance measure, but what (common) term would you use to convey that?

Hi @alastc I see, you want to relate to the measured term used elsewhere. Then I think you could say:

..brightness (perceived luminance).

@alastc alastc merged commit bf2c6d0 into master Jul 30, 2019
@alastc alastc deleted the non-text-contrast-2019-04 branch July 30, 2019 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants