GNU bug report logs - #55887
global-whitespace-mode and WCAG Accessibility Standards

Previous Next

Full log

View this message in rfc822 format

From: goncholden <goncholden <at> protonmail.com>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>
Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, 55887 <at> debbugs.gnu.org
Subject: bug#55887: global-whitespace-mode and WCAG Accessibility Standards
Date: Sat, 11 Jun 2022 19:48:37 +0000

------- Original Message -------
On Sunday, June 12th, 2022 at 1:13 AM, Basil L. Contovounesios <contovob <at> tcd.ie> wrote:


> goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" [2022-06-10 17:54 +0000] wrote:
>
> > ------- Original Message -------
> > On Friday, June 10th, 2022 at 9:58 PM, Lars Ingebrigtsen larsi <at> gnus.org wrote:
> >
> > > goncholden goncholden <at> protonmail.com writes:
> > >
> > > > I have been using global-whitespace-mode to highlight tabs and trailing spaces.
> > > >
> > > > Trailing spaces look good in red, but the colour used for highlighting
> > > > tabs does not look good when one is using a dark background. Can the
> > > > contrast ratio be changed so that it adheres to WCAG Standard used for
> > > > Colour Accessibility?
> > >
> > > The colours look fine to me:
> >
> > If you look at the contrast ratio, you will find that it is very low, a mere
> > 1.59. You should do some homework to ensure a contrast ratio of at least 4.5:1
> > exists between text and background behind the text.
> >
> > Because it looks good to you, it does not necessarily mean it is good.
> > Insisting that it looks good because it is good for you means that the project
> > does not care about accessibility. I cannot see it at all and the thing that
> > saved me was having the tab marks showing up. At a contrast of 3.5, I can see
> > it, confirming that the WCAG Standard in a very good standard to use.
>
>
> Have you tried using one of the Modus themes? They are bundled with
> Emacs since Emacs 28, or you can install them from GNU[-devel] ELPA:

Modus-Themes is a good start.  But it usually sets accessible colours to packages that have never been concerned with accessibility.  Things should work the other way round, with different levels of accessibility in the own design.  There are so many pacakages and customisations that one cannot expect Modus-Themes to take care of  all of them.  Am not saying that accessibility levels should be forced on all users.  But certainly that each package should include accessible modes.


> https://elpa.gnu.org/packages/modus-themes.html
> https://elpa.gnu.org/devel/modus-themes.html
>
> Quoth (info "(modus-themes) Overview"):
>
> The Modus themes are designed for accessible readability. They conform
> with the highest standard for color contrast between any given
> combination of background and foreground values. This corresponds to
> the WCAG AAA standard, which specifies a minimum rate of distance in
> relative luminance of 7:1.
>
> Modus Operandi (‘modus-operandi’) is a light theme, while Modus
> Vivendi (‘modus-vivendi’) is dark. Each theme’s color palette is
> designed to meet the needs of the numerous interfaces that are possible
> in the Emacs computing environment.
>
> For more, see https://protesilaos.com/emacs/modus-themes.
>
> > Rather than simply using grey, the thing to de is select colours from the colour
> > wheel (e.g triadic colours) so you can have an adequate colour vibrancy.
> > Because whilst you use a vibrant red for trailing spaces, whitespace-mode does
> > not continue with the colour vibrancy for highlighting the rest.
> >
> > > If you want a different colour, then change the colour of that face.
>
>
> HTH,
>
> --
> Basil

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.