13639 2011-08-03 20:51:17 +0000 CSS2 System Colors Should Be Recognized 2016-02-26 23:39:13 +0000 1 1 1 Unclassified HTML WG HTML a11y Task Force unspecified Other All RESOLVED WONTFIX a11y, a11ytf P2 normal --- 1 janina chaals chaals cooper dbaron eoconnor faulkner.steve laura.lee.carlson lwatson mike public-html-a11y public-html-admin public-html-wg-issue-tracking robin dave.null oldest_to_newest 52247 0 janina 2011-08-03 20:51:17 +0000 The HTML spec, http://www.w3.org/TR/2011/WD-html5-20110525/common-microsyntaxes.html#colors, should explicitly provide for support of CSS2 System Colors when users require them. This is a long standing accessibility concern, e.g. see: http://lists.w3.org/Archives/Member/w3c-wai-pf/2009AprJun/0155.html http://www.w3.org/2009/04/15-pf-minutes.html#action05] http://lists.w3.org/Archives/Member/w3c-wai-pf/2008JulSep/0484.html http://lists.w3.org/Archives/Member/w3c-wai-pf/2008JulSep/0404.html 52249 1 dbaron 2011-08-03 20:59:03 +0000 I'm against doing this for the reasons described in: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-May/026449.html Further, specification of colors in HTML rather than CSS is a legacy feature; CSS is the recommended way of specifying colors, and I don't think we should go adding additional capabilities to this feature that exists only for compatibility with old content. 52254 2 annevk 2011-08-03 21:15:37 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: <http://dev.w3.org/html5/decision-policy/decision-policy.html>. Status: Rejected Change Description: no spec change Rationale: Simple colors are used by <input type=color> for which system colors do not make sense. The other type of colors supported is a legacy feature as comment 1 points out and authors cannot use it anymore. They have to use CSS, which supports system colors. 53695 3 mike 2011-08-04 05:16:26 +0000 mass-move component to LC1 81922 4 robin 2013-01-22 11:17:05 +0000 Michal, can you please include comments when reopening? It's difficult to track changes otherwise. 81923 5 faulkner.steve 2013-01-22 11:23:04 +0000 (In reply to comment #4) > Michael, can you please include comments when reopening? It's difficult to > track changes otherwise. Discussed at last weeks a11y taskforce meet http://www.w3.org/2013/01/17-html-a11y-minutes.html#item03 re-opened (to keep track) and kicked back to PF to review and discuss with CSS WG 81924 6 robin 2013-01-22 11:27:16 +0000 (In reply to comment #5) > (In reply to comment #4) > > Michael, can you please include comments when reopening? It's difficult to > > track changes otherwise. > > Discussed at last weeks a11y taskforce meet > http://www.w3.org/2013/01/17-html-a11y-minutes.html#item03 > > re-opened (to keep track) and kicked back to PF to review and discuss with > CSS WG Oops, just saw my Michal -> Michael typo — sorry! Thanks Steve. Just for the record: I don't mind bugs being reopened, but it really helps if there's a comment indicating why. Otherwise it's just confusing to use. 125281 7 chaals 2016-02-26 23:39:13 +0000 Some subset of system colours are implemented, but some others are deliberately implemented as something else. The colours themselves have been deprecated, in part to stop people from using them to produce phishing attacks. It seems unlikely that these will get more complete implementation any time soon, and even documenting the behaviour in detail seems counter-productive.