]
Liz Clayton commented on DROOLS-3393:
-------------------------------------
p.s. [~kkufova] [~bdellasc] Please advise also if you think the error state needs a
redundant cue of some sort (icon, bolded cell border...), rather than relying on color
alone. Thanks!
Please review scenario error cell text for legibility/accessibility.
---------------------------------------------------------------------
Key: DROOLS-3393
URL:
https://issues.jboss.org/browse/DROOLS-3393
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Liz Clayton
Assignee: Klara Kufova
Priority: Major
Labels: ScenarioSimulation, UX, UXTeam
Attachments: Screen Shot 2018-11-30 at 11.59.32 AM.png, Screen Shot 2018-11-30 at
12.05.50 PM.png, Screenshot from 2018-11-30 17-11-43.png
[~kkufova] [~bdellasc]
I noticed that the error text is a little "fuzzy" looking, the edges aren't
very sharp and I was concerned that it might not be legible. I asked Danielle about the
specs for it and it's the same size just bolded.
I did an online accessibility text using the following tool, with our current hex values:
https://webaim.org/resources/contrastchecker/. It failed for level 3 compliance, but
I'm not sure we need to shoot for that or not? I tried the darker PatternFly red color
"#8b0000" and it passed at all levels, even at smaller sizes.
I'm wondering if we could use the darker red, in the non-bolded font? And if so,
perhaps the text would be a little bit more legible.
Just wanted to ask about this, please let me know what you think.