Skip to content

Update glossary contrast ratio #912

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.

Sign up for GitHub

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

Closed
wants to merge 4 commits into from
Closed

Update glossary contrast ratio #912

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
28d540b
Outdated link
JAWS-test Sep 11, 2019
75d880a
Update contrast-ratio.html
JAWS-test Oct 4, 2019
fe776f4
Update on-input.html
JAWS-test Oct 23, 2019
316e785
Revert "Update on-input.html"
JAWS-test Oct 23, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions guidelines/terms/20/contrast-ratio.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,20 +15,20 @@

<p class="note">Contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1).</p>

<p class="note">Because authors do not have control over user settings as to how text is rendered
(for example font smoothing or anti-aliasing), the contrast ratio for text can be
<p class="note">Because authors do not have control over user settings as to how text and non-text content is rendered
(for example font smoothing or anti-aliasing), the contrast ratio can be
evaluated with anti-aliasing turned off.
</p>

<p class="note">For the purpose of Success Criteria 1.4.3 and 1.4.6, contrast is measured with respect
to the specified background over which the text is rendered in normal usage. If no
background color is specified, then white is assumed.
to the specified background over which the content is rendered in normal usage. If no
background color is specified, then white is assumed. If no
foreground color is specified, then black is assumed.
</p>

<p class="note">Background color is the specified color of content over which the text is to be rendered
in normal usage. It is a failure if no background color is specified when the text
<p class="note">It is a failure if no background color is specified when the foreground
color is specified, because the user's default background color is unknown and cannot
be evaluated for sufficient contrast. For the same reason, it is a failure if no text
be evaluated for sufficient contrast. For the same reason, it is a failure if no foreground
color is specified when a background color is specified.
</p>

Expand Down
4 changes: 2 additions & 2 deletions techniques/aria/ARIA19.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
</section><section id="description"><h2>Description</h2>
<p>The purpose of this technique is to notify Assistive Technologies (AT) when an input error occurs. The <code class="att">aria-live</code> attribute makes it possible for an AT (such as a screen reader) to be notified when error messages are injected into a Live Region container. The content within the <code class="att">aria-live</code> region is automatically read by the AT, without the AT having to focus on the place where the text is displayed.
</p>
<p>There are also a number of <a href="https://www.w3.org/WAI/PF/aria-practices/#chobet">special case live region roles</a> which can be used instead of applying live region properties directly.</p>
<p>There are also a number of <a href="https://www.w3.org/TR/wai-aria-1.1/#live_region_roles">special case live region roles</a> which can be used instead of applying live region properties directly.</p>
</section><section id="examples"><h2>Examples</h2>
<section class="example">
<h3>Injecting error messages into a container with role=alert already present in the DOM</h3>
Expand Down Expand Up @@ -95,4 +95,4 @@ <h3>Injecting error messages into a container with role=alert already present in
</li>
</ul>

</section></body></html>
</section></body></html>