From 28d540bf5816130863aa4102876892eb557afb9a Mon Sep 17 00:00:00 2001 From: JAWS-test <52748763+JAWS-test@users.noreply.github.com> Date: Wed, 11 Sep 2019 05:02:01 +0200 Subject: [PATCH 1/4] Outdated link Solves https://github.com/w3c/wcag/issues/893 --- techniques/aria/ARIA19.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/techniques/aria/ARIA19.html b/techniques/aria/ARIA19.html index dc14771408..9dc27cc6a3 100644 --- a/techniques/aria/ARIA19.html +++ b/techniques/aria/ARIA19.html @@ -3,7 +3,7 @@

Description

The purpose of this technique is to notify Assistive Technologies (AT) when an input error occurs. The aria-live 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 aria-live region is automatically read by the AT, without the AT having to focus on the place where the text is displayed.

-

There are also a number of special case live region roles which can be used instead of applying live region properties directly.

+

There are also a number of special case live region roles which can be used instead of applying live region properties directly.

Examples

Injecting error messages into a container with role=alert already present in the DOM

@@ -95,4 +95,4 @@

Injecting error messages into a container with role=alert already present in -

\ No newline at end of file +
From 75d880aaddd8fbe8d422be08be42e3236715f628 Mon Sep 17 00:00:00 2001 From: JAWS-test <52748763+JAWS-test@users.noreply.github.com> Date: Fri, 4 Oct 2019 10:04:18 +0200 Subject: [PATCH 2/4] Update contrast-ratio.html --- guidelines/terms/20/contrast-ratio.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/guidelines/terms/20/contrast-ratio.html b/guidelines/terms/20/contrast-ratio.html index eee5a807ce..c52a117c1d 100644 --- a/guidelines/terms/20/contrast-ratio.html +++ b/guidelines/terms/20/contrast-ratio.html @@ -15,20 +15,20 @@

Contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1).

-

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 +

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.

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.

-

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 +

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.

From fe776f40c4db87d619d8976e9d9bcda549e980df Mon Sep 17 00:00:00 2001 From: JAWS-test <52748763+JAWS-test@users.noreply.github.com> Date: Wed, 23 Oct 2019 07:26:32 +0200 Subject: [PATCH 3/4] Update on-input.html --- understanding/20/on-input.html | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/understanding/20/on-input.html b/understanding/20/on-input.html index 41f5a1c08c..457675624d 100644 --- a/understanding/20/on-input.html +++ b/understanding/20/on-input.html @@ -42,8 +42,23 @@

Intent of On Input

+
+ +

If the user interface component is not fully operable with the keyboard due to the change of context, + this would be a violation of SC 2.1.1. +

+ +
- +
+ +

A change of context should only be made if this makes further operation of the application easier. + If the change of context makes the operation difficult for impaired people, it is recommended to avoid the context change. +

+ +
+ +

Benefits of On Input

From 316e785211541c906732fdbbfb190b1a42e84888 Mon Sep 17 00:00:00 2001 From: JAWS-test <52748763+JAWS-test@users.noreply.github.com> Date: Wed, 23 Oct 2019 08:40:29 +0200 Subject: [PATCH 4/4] Revert "Update on-input.html" This reverts commit fe776f40c4db87d619d8976e9d9bcda549e980df. --- understanding/20/on-input.html | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/understanding/20/on-input.html b/understanding/20/on-input.html index 457675624d..41f5a1c08c 100644 --- a/understanding/20/on-input.html +++ b/understanding/20/on-input.html @@ -42,23 +42,8 @@

Intent of On Input

-
- -

If the user interface component is not fully operable with the keyboard due to the change of context, - this would be a violation of SC 2.1.1. -

- -
-
- -

A change of context should only be made if this makes further operation of the application easier. - If the change of context makes the operation difficult for impaired people, it is recommended to avoid the context change. -

- -
- -
+

Benefits of On Input