unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Thibaut Verron <thibaut.verron@gmail.com>,
	Heime <heimeborgia@protonmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	help-gnu-emacs@gnu.org
Subject: Re: Introducing face in comments for various modes
Date: Mon, 12 Dec 2022 17:07:26 +0100	[thread overview]
Message-ID: <trinity-00f5d9ac-ae29-40ba-b578-743bb6ca31d5-1670861246578@3c-app-mailcom-bs04> (raw)
In-Reply-To: <CAP_d_8XcWMqFNzvoyKeJ13jYhEpxCfm9Vd1zSKb0hZJ67DmOww@mail.gmail.com>



----- Christopher Dimech
Administrator General - Naiad Informatics - Gnu Project

Society has become too quick to pass judgement and declare someone
Persona Non-Grata, the most extreme form of censure a country can
bestow.

In a new era of destructive authoritarianism, I support Richard
Stallman.  Times of great crisis are also times of great
opportunity.  I call upon you to make this struggle yours as well !

https://stallmansupport.org/
https://www.fsf.org/     https://www.gnu.org


> Sent: Tuesday, December 13, 2022 at 3:22 AM
> From: "Yuri Khan" <yuri.v.khan@gmail.com>
> To: "Thibaut Verron" <thibaut.verron@gmail.com>
> Cc: "Heime" <heimeborgia@protonmail.com>, "Stefan Monnier" <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
> Subject: Re: Introducing face in comments for various modes
>
> On Mon, 12 Dec 2022 at 17:53, Thibaut Verron <thibaut.verron@gmail.com> wrote:
> 
> > > If you use "modus-vivendi" for org-mode, the colours are all almost white,
> > > a big problem particularly when you fold the org headings.
> >
> > I don't like dark backgrounds, but it seems perfectly readable to me.
> 
> Heime has a point. The complaint is not about *readability* of
> modus-vivendi’s colors against the background. It is about
> *distinction* between levels of Org headings, i.e. ability to
> distinguish a level 3 heading from a level 4 just by color.
> 
> This is a nontrivial thing to solve, by the way. It’s very easy to
> fall in the trap “WCAG level AAA prescribes a contrast ratio of at
> least 7:1; I’ll make my primary foreground and all my accent
> foreground colors exactly 7:1 against the background so all will be
> readable”. Yes, but this way they are all the same luminance, and by
> that token all very similar in some sense. A color-blind person might
> even not be able to distinguish hues and rely on luminance alone to
> tell colors apart.

Correct.  WCAG Level AAA works well for a foreground upon a background colour.
Thusly it is still quite a basic scheme.  When, in addition, one considers 
colour contrast requirements upon adjacent coloured letters, the WCAG Levels
are not enough to do this.  One has to optimise colour contrast on both foreground
with background, as well as contrast upon adjacent colours.  

Some work on this showed that you would not be able to completely satisfy WCAG Levels,
if you want to optimise colour contrast between adjacent letters too. 

Still, one can use a metric.  The whole point to understand is that the colours
are not set up at the discretion of the programmer.  You are limited only to certain
colour tones only.  Doing anything else would always result in a sub-optimal result.

The original modes-themes, even though they were a huge improvements compared to other
themes, were found to be sub-optimal.
 
> As far as I can tell, WCAG does not give any guidance as to
> distinction between foreground colors, except for “thou shalt not make
> the user rely solely on color”.
> 
>



  parent reply	other threads:[~2022-12-12 16:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-11 15:35 Introducing face in comments for various modes Heime
2022-12-11 17:40 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-12  2:24   ` Heime
2022-12-12  3:00     ` Heime
2022-12-12  8:49       ` Thibaut Verron
2022-12-12  9:21         ` Heime via Users list for the GNU Emacs text editor
2022-12-12  9:58           ` Thibaut Verron
2022-12-12 10:20             ` Heime
2022-12-12 10:50               ` Thibaut Verron
2022-12-12 11:55                 ` Heime
2022-12-12 12:17                   ` Thibaut Verron
2022-12-12 14:46                     ` Heime
2022-12-12 15:22                 ` Yuri Khan
2022-12-12 15:38                   ` Thibaut Verron
2022-12-12 15:55                   ` Christopher Dimech
2022-12-12 16:07                   ` Christopher Dimech [this message]
2022-12-12 17:44                   ` Stefan Monnier
2022-12-13  5:20                     ` Christopher Dimech
2022-12-12 15:22           ` Stefan Monnier
2022-12-13  7:52           ` Jean Louis
2022-12-13  8:04             ` Heime
2022-12-13  8:30               ` Heime
2022-12-13  9:35                 ` Thibaut Verron
2022-12-13  9:46                   ` Heime
2022-12-13 10:05                     ` Thibaut Verron
2022-12-13 10:24                       ` Christopher Dimech
2022-12-13 10:40                       ` Heime
2022-12-13 10:45                         ` Thibaut Verron
2022-12-13 10:49                           ` Heime
2022-12-13 15:00                           ` Heime
2022-12-13 12:37                     ` Jean Louis
2022-12-13 14:00                       ` Heime
2022-12-13 12:36                 ` Jean Louis
2022-12-13 13:46                   ` Heime
2022-12-13 12:35               ` Jean Louis
2022-12-13  8:17             ` Christopher Dimech
2022-12-13 19:19               ` Jean Louis
2022-12-12 15:20         ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-00f5d9ac-ae29-40ba-b578-743bb6ca31d5-1670861246578@3c-app-mailcom-bs04 \
    --to=dimech@gmx.com \
    --cc=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=thibaut.verron@gmail.com \
    --cc=yuri.v.khan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).