-
Notifications
You must be signed in to change notification settings - Fork 286
Update F81 #1033
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
base: main
Are you sure you want to change the base?
Update F81 #1033
Conversation
ObjectionThe line "A minimum contrast ratio of 3:1 is considered sufficient." does not belong in this criterion and creates a conflict with the other SCs that define luminance. Side note: the term is luminance not luminosity. Also, the word "are" was incorrectly removed from the change in the first paragraph. |
The exception regarding contrast was already in F81, without an exact specification of the contrast ratio. The text has been inserted to be compliant with https://www.w3.org/WAI/WCAG21/Techniques/general/G183 and with #873. |
@@ -1,14 +1,17 @@ | |||
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only</title><link rel="stylesheet" type="text/css" href="../../css/sources.css" class="remove"></link></head><body><h1>Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only</h1><section class="meta"><p class="id">ID: F81</p><p class="technology">Technology: failures</p><p class="type">Type: Failure</p></section><section id="applicability"><h2>When to Use</h2> | |||
<p>All technologies</p> | |||
</section><section id="description"><h2>Description</h2> | |||
<p>This objective of this technique is to describe the failure that occurs when a required field or an error field is marked with color differences only, without an alternate way to identify the required field or error field. This can cause problems for people who are blind or colorblind, because they may not be able to perceive the color differences that indicate which field is required or which field is causing an error.</p> | |||
<p>This objective of this technique is to describe the failure that occurs when a required field or an error field is marked with color differences only, without an alternate way to identify the required field or error field. This can cause problems for people who colorblind, because they may not be able to perceive the color differences that indicate which field is required or which field is causing an error.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a verb missing @JAWS-test2
This can cause problems for people who colorblind
to
This can cause problems for people who are colorblind
<p>In both examples, the color could be used without failure if the text was sufficiently different in visual presentation (e.g. bold or in a different font) that it would be easily differentiated from the surrounding text if the color were removed. It would also not fail if the color chosen had sufficient luminosity difference (lightness) from the other text that it would be easily be seen as different if viewed in black and white. A minimum contrast ratio of 3:1 is considered sufficient. In these cases - the information would not be displayed in color (hue) alone but also in "presentation" or "lightness" respectively. </p> | ||
</div> | ||
<div class="note"> | ||
<p>For users of assistive technology, required or error fields must also be perceptible. This is checked with the SCs 1.3.1 and 3.3.1.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perceptible
Should that be perceivable (just because that is what WCAG uses elsewhere and it seems to be good to re-use nomenclature :-)
Fixes #873