unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: 57424@debbugs.gnu.org
Subject: bug#57424: Perceptibility of display-fill-column-indicator-mode
Date: Fri, 26 Aug 2022 07:44:23 +0200	[thread overview]
Message-ID: <trinity-52bcee74-c263-46f0-bd3e-1cb7b5cf3fc4-1661492663115@3c-app-mailcom-bs07> (raw)

Have followed the customisation discussion about
display-fill-column-indicator-mode

Have consulted with Protesilaos Stavrou, author of
modus-themes.  I agree that the default indicator character is
too thin.  Changing the character to something wider does not
change things much.  A solution that works is that of setting a
background colour, rather than changing the foreground colour .

Cannot see any consideration of accessibility in its design, as
it looks that the plan had been to make the indicator faint and
almost imperceptible.  This strategy is the worst possible thing
one can do for the cohort of visually challenged people (remember
that perceptibility changes with age, meaning that developers
could be too young and inexperienced to understand
perceptibility considerations).

Protesilaos described how the default style of
display-fill-column-indicator-mode gets a dashed vertical line.
These dashes appear further apart and feel broken if the user (i)
has a font with a tall line height, (ii) increases the value of
line-spacing, (iii) has an increased height for constructs like
headings in Org.

The only way to ensure a contiguous vertical line is to
explicitly set the :height of the face to a small value.  This
brings out the perceptibility problem.

Studying carefully WCAG 2.1, Section 1.4.3 Contrast (Minimum),
the contrast ratio is also subject to change according to the
thinness of the characters.  For instance, With larger thicker
text, the contrast ratio of at least 4.5:1 can be modified to to
at least 3:1.

I see the requirement of a contiguous indicator line is mainly about
aesthetics.  But practical usability should be of higher concern.





             reply	other threads:[~2022-08-26  5:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  5:44 Christopher Dimech [this message]
2022-08-26  6:27 ` bug#57424: Perceptibility of display-fill-column-indicator-mode Protesilaos Stavrou
2022-08-26  6:43   ` Christopher Dimech
2022-08-26 10:50 ` Lars Ingebrigtsen
2022-08-26 10:55   ` Lars Ingebrigtsen
2022-08-26 11:29     ` Christopher Dimech

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-52bcee74-c263-46f0-bd3e-1cb7b5cf3fc4-1661492663115@3c-app-mailcom-bs07 \
    --to=dimech@gmx.com \
    --cc=57424@debbugs.gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).