Consider changing meter suboptimum value to have Mark system color background in hcm appearance:auto
Categories
(Core :: Widget, enhancement, P3)
Tracking
()
People
(Reporter: aja, Unassigned)
References
(Blocks 1 open bug)
Details
Followup to bug 1698336.
Would give better semantics for sub-optimum value of meter element.
Optimum value already set to Highlight system color.
|
||
Comment 1•3 years ago
|
||
This could get some input from Morgan / other a11y folks :)
|
||
Comment 2•3 years ago
|
||
Is the goal here to differentiate between optimum and sub-optimum in HCM (since currently they're both highlight color?)
That sounds like a good idea to me. Is there a particular property of mark color that makes you inclined to use it for this (or do we already adjust this color somehow for HCM?)
|
Reporter | |
Comment 3•3 years ago
|
||
Yes, to differentiate between optimum and sub-optimum.
There's an example in spec showing Mark as Yellow, and MarkText as black...but they are system colors, so can vary per OS/theme settings.
In the case where an OS doesn't supply a color, I'd suggest fallback to something more like orange,
which would probably have better visibility in light HCM themes.
|
|
Reporter | |
Updated•3 years ago
|
|
|
||
Comment 4•3 years ago
•
|
||
(In reply to Bill Goldstein [:aja] (UTC-6) from comment #3)
Yes, to differentiate between optimum and sub-optimum.
There's an example in spec showing Mark as Yellow, and MarkText as black...but they are system colors, so can vary per OS/theme settings.
In the case where an OS doesn't supply a color, I'd suggest fallback to something more like orange,
which would probably have better visibility in light HCM themes.
Great! I think that's the right thing to do, thanks for the explanation! :) In terms of a fall-back, it might make more sense to use a value that /is/ specified by the client, given some users use HCM customization for other reasons, ie. to generate photo-sensitive themes, that we may disrupt with a static choice. Also, if we pick a fixed color we run the risk of having the user select the same thing for their foreground/background, which might make this component inaccessible
Description
•