It's it just me, why on earth does the close app file save warning highlight the 'Don't Save' option in red? OK it's red, but my eye is naturally drawn hard towards it and many being a bit 'click happy' might select it - potentially losing work. What reverse logic is this mind-game!
Oh and it's not accessibility friendly, not everyone can see colour just tone.
How about highlight / bolden Save and potentially in green and ensure the Enter key saves instead? Update, I note the Enter key does default to save option, but that's not what my brain is telling me, it's saying the Don't Save is default!
I'm also not a big fan of this design. If the intent is to warn people that they may be about to close the document by accident, giving them a chance to cancel that action and continue working, the highlight should be placed in the "Cancel" button. Worst case scenario, nothing happens and the user can then try again to close and save the document.
Three buttons on dialogues are a mistake when it comes to binary decisions. In this case I can understand the need to quit without saving, but the most likely scenario is to save the file; that's where the highlight should go. The cancel button should be a × on the top of the window.
PS: I'm moving this over to the Feedback category as this is more fitting there.
In my eyes, red means bad. Therefore, you should NOT be clicking on the red, unless that's what you really want to do. As for the accessibility, it could be done in a slightly darker shade to help, as technically i think it passes some but fails other accessibility tests, but the shade's enough for my colourblind parent to be able to tell that it's different. Take that for what it may or may not be.
There's no way that will pass accessibility, let alone the 'happy clickers' brigade. Colour blindness affects Red significantly so a shade could mean 'click here' if you don't read it and take it in. It's exceptionally poor design. I agree with zenzen.
I'm not saying it's good or bad design, just that I understand what the logic of what they were going for is. Depending on what you're going for, this can technically pass certain accessibility standards:
This is primarily determined by the system theme. I would qualify this as Zorin Theme constructive feedback.
The theme determines the color that is set within the theme .css.
It also sets the appearance of destructive actions.
The theme does not set which actions are destructive, that is set by the application.
