From: Christopher Dimech <dimech@gmx.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45626@debbugs.gnu.org
Subject: bug#45626: flyspell Accessibility Problem
Date: Sun, 10 Jan 2021 16:26:41 +0100 [thread overview]
Message-ID: <trinity-1e608403-f8e8-4a3e-a6a2-5a8ae6bb5d8f-1610292401239@3c-app-mailcom-bs09> (raw)
In-Reply-To: <87h7noq0n0.fsf@gnus.org>
> Sent: Monday, January 11, 2021 at 3:20 AM
> From: "Lars Ingebrigtsen" <larsi@gnus.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: 45626@debbugs.gnu.org
> Subject: Re: bug#45626: flyspell Accessibility Problem
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > After a round of Software Accessibility iterations with Protesilaos Stavrou
> > regarding the wavy underline provided by flyspell, it was determined that
> > the wavy line is too thin for colour contrast ratios to make any difference.
> >
> > One idea we came up with was to have the wavy line thicker. However, the usual
> > way ispell-word highlights the word is the way forward. Flyspell should use the
> > same approach highlight words as ispell-word does, eliminating the
> > wavy underline.
>
> I'm not quite sure I understand the request here -- this is about the
> `flyspell-incorrect' and `flyspell-duplicate' faces? Can't people just
> customise that to whatever they want?
Yes, but one cannot make the wavy line thicker. This means that changing
the colour of the wavy underline according to WCAG AAA Standard is not
sufficient for compliance.
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
next prev parent reply other threads:[~2021-01-10 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 14:49 bug#45626: flyspell Accessibility Problem Christopher Dimech
2021-01-10 15:20 ` Lars Ingebrigtsen
2021-01-10 15:26 ` Christopher Dimech [this message]
2021-01-10 15:29 ` Lars Ingebrigtsen
2021-01-10 16:20 ` Christopher Dimech
2021-01-11 15:37 ` Lars Ingebrigtsen
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=trinity-1e608403-f8e8-4a3e-a6a2-5a8ae6bb5d8f-1610292401239@3c-app-mailcom-bs09 \
--to=dimech@gmx.com \
--cc=45626@debbugs.gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.