Yes, thank you Russ. The conditions you mentioned were all considered when these screenshots <http://imgur.com/a/JaLPD> were created, with the exception of Deuteranomoly (reduced sensitivity to green) as the test results were nearly the same as the Protonomaly (reduced sensitivity to red) screenshots.
For good measure - Deuteranomoly Success Message <https://lh3.googleusercontent.com/-S7khv5eqY3c/UlYL2MaY7iI/AAAAAAAAEYM/WxBynj6ugVc/s1600/Screen+Shot+2013-10-09+at+10.06.07+PM.png> On Wednesday, October 9, 2013 8:40:55 PM UTC-4, Russell Keith-Magee wrote: > > > For the sake of completeness, it's worth pointing out two things: > > 1) "Color blindness" isn't a single medical condition. It's half a dozen > different conditions, all with different colour distortions, ranging from > mild colour spectrum distortion (Protanomaly, Deuteranomaly and > Tritanomaly), to complete absence of colour vision (Achromatopsia). > > 2) The existing design already accounts for this. It's a monochromatic > design (all messages in yellow) that uses icons to differentiate between > "error", "warning" and "info". The proposed designs are introducing colour, > but aren't removing the iconic elements. > > For me, the only question here is the specific choice of colour. The > existing design isn't heavily using colour to communicate significance of a > message. Introducing colour will be a UX win for those with colour vision; > if we pick a good set of colors, those with a mild colour sensory disorder > will still be able to distinguish error types based on colour. However, > even if you are completely monochromatic, the icons are still there, so a > visual cue exists. > > Yours, > Russ Magee %-) > > On Thu, Oct 10, 2013 at 6:52 AM, Ryan Allen <[email protected]<javascript:> > > wrote: > >> Recent commits to improve error messages, particularly for those with >> color blindness: >> >> <https://lh5.googleusercontent.com/-POpaaRuaL_k/UlXeFPcHBTI/AAAAAAAAEX0/HHcU6iNRXkc/s1600/Screen+Shot+2013-10-09+at+6.46.05+PM.png> >> >> >> <https://lh5.googleusercontent.com/-9UjKD0jm35M/UlXeIJxrr1I/AAAAAAAAEX8/Y0BUK0ukpHs/s1600/Screen+Shot+2013-10-09+at+6.46.31+PM.png> >> >> >> On Tuesday, October 8, 2013 2:46:08 PM UTC-4, Ryan Allen wrote: >>> >>> Here are comparisons for several different color blindness types: >>> http://imgur.com/a/**JaLPD <http://imgur.com/a/JaLPD> >>> >>> On Tuesday, October 8, 2013 3:16:32 AM UTC-4, HM wrote: >>>> >>>> Did you test the colors with a color-blind filter? Always a question to >>>> ask when red and green is given significance in any way. The new error red >>>> is better though, bigger contrast to the white. >>>> >>>> >>>> >>>> On 7 October 2013 22:44, Ryan Allen <[email protected]> wrote: >>>> >>>>> https://github.com/django/**django/pull/1715<https://github.com/django/django/pull/1715> >>>>> >>>>> Currently, all admin messages have a background color of light yellow, >>>>> whether they are success message, warning message, or error message. >>>>> Errors >>>>> are displayed with red (#F00) text. >>>>> >>>>> This pull request would give success messages a green background and >>>>> errors a light red with dark red border and text. >>>>> >>>>> Current alerts: http://imgur.com/a/**dIO6O <http://imgur.com/a/dIO6O> >>>>> Updated alerts: http://imgur.com/a/**fw54u <http://imgur.com/a/fw54u> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django developers" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to django-develop...@**googlegroups.com. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at >>>>> http://groups.google.com/**group/django-developers<http://groups.google.com/group/django-developers> >>>>> . >>>>> To view this discussion on the web visit https://groups.google.com/d/* >>>>> *msgid/django-developers/**2ab5f4ee-16df-4bf2-8d3e-** >>>>> 893885d51f39%40googlegroups.**com<https://groups.google.com/d/msgid/django-developers/2ab5f4ee-16df-4bf2-8d3e-893885d51f39%40googlegroups.com> >>>>> . >>>>> For more options, visit >>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/59c5ad77-ce65-4d51-8d3f-2a9253b6dd8c%40googlegroups.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0ce2f573-34b6-4937-8280-a5df0745392a%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
