[css-color-adjust-1] Restore the commits I accidentally wiped in the 8103c85 commit, phew

Author: tabatkins

css-color-adjust-1/Overview.bs

@@ -3,11 +3,11 @@ Title: CSS Color Adjustment Module Level 1
 Shortname: css-color-adjust
 Level: 1
 Status: ED
-Work Status: exploring
+Work Status: refining
 Group: CSSWG
 TR: https://www.w3.org/TR/css-color-adjust-1/
 ED: https://drafts.csswg.org/css-color-adjust-1/
-Previous Version: https://www.w3.org/TR/2020/WD-css-color-adjust-1-20200402/
+Previous Version: https://www.w3.org/TR/2020/WD-css-color-adjust-1-20201109/
 Editor: Elika J. Etemad / fantasai, Invited Expert, http://fantasai.inkedblade.net/contact, w3cid 35400
 Editor: Rossen Atanassov, Microsoft, ratan@microsoft.com, w3cid 49885
 Editor: Rune Lillesveen, Google, futhark@google.com, w3cid 45291
@@ -130,7 +130,7 @@ Opting Into a Preferred Color Scheme: the 'color-scheme' property {#color-scheme
 	Name: color-scheme
 	Value: normal | [ light | dark | <<custom-ident>> ]+
 	Initial: normal
-	Applies to: all elements
+	Applies to: all elements and text
 	Inherited: yes
 	Computed Value: the keyword ''normal'', or an ordered list of specified color scheme keywords
 	Animation type: discrete
@@ -365,7 +365,7 @@ Forced Color Schemes {#forced}
 	intended to increase the readability of text through color contrast.
 	Individuals with limited vision
 	often find it more comfortable to read content
-	when there is a a particular type of contrast
+	when there is a particular type of contrast
 	between foreground and background colors.
 
 	Operating systems can provide built-in color themes,
@@ -414,7 +414,7 @@ Forced Color Schemes {#forced}
 	when '@media/forced-colors' is ''active'',
 	reducing effects such as shadows, fades, blurs, filters, gradients,
 	and image or pattern fills
-	that add complexity to discerning shape outlin
+	that add complexity to discerning shape outline
 -->
 
 Properties Affected by Forced Colors Mode {#forced-colors-properties}
@@ -438,10 +438,14 @@ Properties Affected by Forced Colors Mode {#forced-colors-properties}
 		<li>'scrollbar-color'
 		<li>'-webkit-tap-highlight-color'
 		<li>'background-color'
+		<li>'caret-color'
+		<li>'flood-color'
+		<li>'lighting-color'
+		<li>'stop-color'
 	</ul>
 
-	if its [=computed value=] would be a color other than a [=system color=],
-	it is instead forced to a [=system color=] as follows:
+	if its [=computed value=] is a color other than a [=system color=],
+	its [=used value=] is instead forced to a [=system color=] as follows:
 
 	* If the color value indicates a “fallback” color
 		(as in the ''color()'' function in [[CSS-COLOR-5]])
@@ -462,11 +466,34 @@ Properties Affected by Forced Colors Mode {#forced-colors-properties}
 		whenever all of the element’s affected properties
 		are likewise UA-determined.
 
+		<div class="note">
+			UAs need to be careful about inheritance when forcing colors.
+			For example,
+			suppose the UA’s button 'color' and 'background-color'
+			are the opposite of its canvas 'color' and 'background-color'.
+			Given markup such as
+
+			<xmp highlight=html>
+				<button>Push <em>this</em> button</button>
+			</xmp>
+
+			Normally, <{em}> will inherit from <{button}>,
+			ensuring its readability.
+			However in [=forced colors mode=],
+			the 'color' of both <{button}> and <{em}> will need to be forced.
+			It's easy to see that <{button}>’s color should be forced to the button color,
+			but <{em}> also needs to be forced to the button color;
+			if it were forced to the canvas 'color' like it is everywhere else in the document,
+			its text will be unreadable.
+		</div>
+
 	Additionally:
-	* 'box-shadow' and 'text-shadow' compute to to ''box-shadow/none''
+	* 'box-shadow' and 'text-shadow' compute to ''box-shadow/none''
 	* 'background-image' computes to ''background-image/none''
 		unless the original value contains a ''url()'' function
 	* 'color-scheme' computes to ''light dark''
+	* 'scrollbar-color' computed to ''scrollbar-color/auto''
+	* 'accent-color' computed to ''accent-color/auto''
 
 	UAs may further tweak these <a>forced colors mode</a> heuristics
 	to provide better user experience.
@@ -478,7 +505,7 @@ Opting Out of a Forced Color Scheme: the 'forced-color-adjust' property {#forced
 	Name: forced-color-adjust
 	Value: auto | none
 	Initial: auto
-	Applies to: all elements
+	Applies to: all elements and text
 	Inherited: yes
 	Animation type: not animatable
 	</pre>
@@ -602,11 +629,12 @@ Performance-based Color Adjustments: the 'color-adjust' property {#perf}
 			when distracted in a car.
 	</dl>
 
-Privacy and Security Considerations {#privsec}
+Privacy and Security Considerations {#priv-sec}
 ===================================
 
 	Applying user color preferences via [=color schemes=] or [=forced colors mode=]
-	expose the user's color preferences to the page,
+	exposes the user's color preferences to the page
+	via {{getComputedStyle()}},
 	which can increase fingerprinting surface.
 
 	Additionally, it may be possible for an embedded document
@@ -631,6 +659,15 @@ Acknowledgements {#acknowledgements}
 Changes {#changes}
 =======
 
+	Changes since the <a href="https://www.w3.org/TR/2020/WD-css-color-adjust-1-20201109/">9 NOvember 2020 Working Draft</a>:
+
+	* Added 'scrollbar-color', 'caret-color', 'flood-color', 'lighting-color', 'stop-color', and 'accent-color'
+			resets to [=forced colors mode=].
+			(<a href="https://github.com/w3c/csswg-drafts/issues/5778">Issue 5778</a>,
+			 <a href="https://github.com/w3c/csswg-drafts/issues/5873">Issue 5873</a>,
+			 <a href="https://github.com/w3c/csswg-drafts/issues/5987">Issue 5987</a>)
+
+
 	Changes since the <a href="https://www.w3.org/TR/2019/WD-css-color-adjust-1-20190523/">23 May 2019 Working Draft</a>:
 
 	<ul>