From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Cuirass accessibility
Date: Sat, 15 May 2021 15:13:45 +0000 [thread overview]
Message-ID: <M-p5QU-jftKy4hlMXc0IkPV56ppI8yW77hab7phtqn963Gl1vSmdekTnZPfJpTSchxcH43_Ktd2gzKvdqsrF3LCr2Kga2np226ETA43DiXE=@protonmail.com> (raw)
In-Reply-To: <87pmxuzc4o.fsf@gnu.org>
On Thursday, May 13, 2021 7:07 PM, Mathieu Othacehe <othacehe@gnu.org> wrote:
> Hello,
>
> As part of the Cuirass NLNet grant[1], the website at
> https://ci.guix.gnu.org has been audited by the Accessibility
> Foundation[2].
That's nice.
> I have made the report public here[3]. Although I have already applied a
> bunch of accessibility related fixes, there's still some work left. The
> report if full of interesting teachings, and if some people want to join
> me, they are more than welcome :).
Not offering to help right now, but just wanted to comment that I've audited a couple of websites before for accessibility using the WCAG-EM 1.0 (although I'm not an expert), and I've found that while website developers tend to improve accessibility based on the results, websites lose part of that accessibility again when their maintenance change hands or depend on new people that are not familiar with accessibility.
Personally, I also tend to forget some best practices with time...
Maybe, with Guix websites, READMEs could state clearly developers are aiming for Level AA conformance, and suggest contributors to check for common accessibility problems (and even HTML/CSS/FEED validity) when they make structural or style changes.
next prev parent reply other threads:[~2021-05-15 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 19:07 Cuirass accessibility Mathieu Othacehe
2021-05-15 15:13 ` Luis Felipe [this message]
2021-05-15 16:50 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='M-p5QU-jftKy4hlMXc0IkPV56ppI8yW77hab7phtqn963Gl1vSmdekTnZPfJpTSchxcH43_Ktd2gzKvdqsrF3LCr2Kga2np226ETA43DiXE=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=othacehe@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/guix.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).