unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Accessibility in Guix
Date: Sat, 13 Jul 2019 12:53:09 +0200	[thread overview]
Message-ID: <20190713125219.22995108@sybil.lepiller.eu> (raw)

Hi Guix!

I think in order to reach out to more people, accessiblity is an
important topic. I've talked with Irina during the Perl and Guile days,
and fixed orca (it didn't work because of failures when loading
pyatspi).

In order to make our system accessible from the start, we obviously
need an accessible installer. With Irina and later with Jean-Phillipe
from Hypra, I collected a list of items we should have in the installer
for blind and visually impaired people:

- A way to activate accessibility options from the start of the system
  (it doesn't need to be on by default if we make sure to document it
  in the manual). For instance, it could be the first item in the first
  menu, or a keyboard shortcut.
- Screen reader technologies: there are a few accessibility
  technologies for that. Since the installer is on a tty, we could use
  brltty that is able to talk to braille output, and we could use
  speakup, a kernel module that is able to read a tty and use voice
  synthesis hardware and software.
- We should have an option to build a system with accessibility
  features, probably via a menu to select the kind of accessibility
  feature one needs (it should be a gnome system, with orca running).

We should probably talk to youpi from Debian, since he worked on the
accessibility features of the Debian installer.

             reply	other threads:[~2019-07-13 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13 10:53 Julien Lepiller [this message]
2019-07-14  8:53 ` Accessibility in Guix Ricardo Wurmus

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=20190713125219.22995108@sybil.lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@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).