Almost all systems used today to view web content assume sRGB encoding. Unless it is known that another color space will be used to process and display the content, - authors should evaluate using sRGB colorspace. If using other color spaces, see Understanding Success Criterion 1.4.3. + authors should evaluate using sRGB colorspace. If using other color spaces, see Understanding Success Criterion 1.4.3 Contrast (Minimum).
If dithering occurs after delivery, then the source color value is used. For colors diff --git a/guidelines/sc/20/non-text-content.html b/guidelines/sc/20/non-text-content.html index bc59554336..ddf670b328 100644 --- a/guidelines/sc/20/non-text-content.html +++ b/guidelines/sc/20/non-text-content.html @@ -13,7 +13,7 @@
If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.) +
If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 Name, Role, Value for additional requirements for controls and content that accepts user input.)
This success criterion covers sections within writing, not user interface components. User interface components are covered under Success Criterion 4.1.2. +
This success criterion covers sections within writing, not user interface components. User interface components are covered under Success Criterion 4.1.2 Name, Role, Value.
diff --git a/guidelines/sc/20/timing-adjustable.html b/guidelines/sc/20/timing-adjustable.html index cb371fa19b..6c0c3f26c9 100644 --- a/guidelines/sc/20/timing-adjustable.html +++ b/guidelines/sc/20/timing-adjustable.html @@ -68,7 +68,7 @@This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion - should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action. + should be considered in conjunction with Success Criterion 3.2.1 On Focus, which puts limits on changes of content or context as a result of user action.
diff --git a/guidelines/terms/20/contrast-ratio.html b/guidelines/terms/20/contrast-ratio.html index 66a1d522e9..2a4a2cd7c8 100644 --- a/guidelines/terms/20/contrast-ratio.html +++ b/guidelines/terms/20/contrast-ratio.html @@ -20,9 +20,9 @@ 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. +
For the purpose of Success Criteria 1.4.3 Contrast (Minimum) and 1.4.6 Contrast (Enhanced), + 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.
Background color is the specified color of content over which the text is to be rendered diff --git a/guidelines/terms/20/relative-luminance.html b/guidelines/terms/20/relative-luminance.html index a071088136..a5c539db6b 100644 --- a/guidelines/terms/20/relative-luminance.html +++ b/guidelines/terms/20/relative-luminance.html @@ -45,7 +45,7 @@
Almost all systems used today to view web content assume sRGB encoding. Unless it is known that another color space will be used to process and display the content, - authors should evaluate using sRGB colorspace. If using other color spaces, see Understanding Success Criterion 1.4.3. + authors should evaluate using sRGB colorspace. If using other color spaces, see Understanding Success Criterion 1.4.3 Contrast (Minimum).
If dithering occurs after delivery, then the source color value is used. For colors