All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Miata <mrmazda@earthlink.net>
To: util-linux@vger.kernel.org
Subject: tty[1-6]: colors a negative accessibility/usability trend
Date: Thu, 12 Feb 2015 04:45:18 -0500	[thread overview]
Message-ID: <54DC762E.2090404@earthlink.net> (raw)

Red, blue and green in particular produce poor contrast on the black
background of a typical framebuffer screen. As these screens are configured
as functional twins of those modes we find outselves in at rescue time, it
amounts to an unfortunate and unnecessary accessibility/usability obstacle
that is IMO is a subset of a larger general problem found under the moniker
A11Y[1].

A very good, very recent article discusses the mindset that leads to default
settings that thwart use by the disadvantaged[2], however slight that
impediment may be.

With util-linux >= 2.25 we can turn colors off via

	# touch /etc/terminal-colors.d/disable [3]

for some commands, but far too few. It should apply to all, including many
outside the purview of util-linux, and more importantly, do so by default.

It should be up to those who wish a legibility reduction to discover how to
and apply the reduction, not the other way around as it is now. It is much
more difficult for those who cannot handle low contrast to improve it than
for those who find it too high to reduce it, a variation on the chicken/egg
paradigm.

If we can get all components of util-linux to adhere to maximizing
legibility, it would have the potential serve as an important springboard for
other projects to do the same, and maybe even spill onto the web.

[1] http://a11yproject.com/
[2] http://alistapart.com/article/reframing-accessibility-for-the-web
[3] http://karelzak.blogspot.de/2014/04/terminal-colorsd.html
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

             reply	other threads:[~2015-02-12  9:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  9:45 Felix Miata [this message]
2015-02-12 11:04 ` tty[1-6]: colors a negative accessibility/usability trend Pádraig Brady
2015-02-13  3:21   ` Dale R. Worley
2015-02-13  9:21     ` Karel Zak
2015-02-13 10:33       ` Sami Kerola
2015-02-13 11:25         ` Karel Zak
2015-02-15 11:12           ` Mike Frysinger
2015-02-16  9:10             ` Karel Zak
2015-02-16  9:35               ` Mike Frysinger
2015-02-16  9:47                 ` Karel Zak
2015-02-16 10:32                   ` Samuel Thibault
2015-02-16 13:49                     ` Karel Zak
2015-02-27 13:48                     ` Karel Zak
2015-03-01 13:32                       ` Pádraig Brady
2015-03-01 15:14                         ` Peter Cordes
2015-03-02  8:59                         ` Karel Zak
2015-03-02  9:31                           ` Samuel Thibault
2015-03-02 11:03                             ` Karel Zak
2015-02-15 17:38         ` Dale R. Worley
2015-02-16  9:18           ` Karel Zak
2015-02-13 17:55       ` Bruce Dubbs
2015-02-12 13:21 ` Karel Zak
2015-02-12 13:56   ` Samuel Thibault
2015-02-12 14:38     ` Karel Zak
2015-02-12 15:25     ` Edward d'Auvergne

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

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

  git send-email \
    --in-reply-to=54DC762E.2090404@earthlink.net \
    --to=mrmazda@earthlink.net \
    --cc=util-linux@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.