From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: "Simen Endsjø" <simendsjo@gmail.com>
Cc: 64987@debbugs.gnu.org, help-guix@gnu.org
Subject: bug#64987: Blind people unable to install Guix System
Date: Tue, 01 Aug 2023 18:29:25 +0800 [thread overview]
Message-ID: <87pm47ys1m.fsf@envs.net> (raw)
In-Reply-To: <87v8e0q7y9.fsf@gmail.com> ("Simen Endsjø"'s message of "Mon, 31 Jul 2023 19:57:08 +0200")
Simen Endsjø <simendsjo@gmail.com> writes:
> It was brought to my attention that blind people runs into problems installing
> Guix System, while Debian and Arch have solved this better.
>
> The problem is outlined by the user k.g.roberts, ref
> <https://im-in.space/@bubstance/110805249670354167>:
>
> The installer for Guix System 1.4.0 is basically the same as I remember it from
> a few years ago; boots almost immediately into an ncurses menu for locale
> selection and it takes another few screens to get to the option for a shell. No
> other assistive technologies built into the installer itself outside of what’s
> in the kernel, so a blind installation is doable over a remote connection after
> that point, but would likely be a hassle to get going without additional help
> from a sighted person.
>
> Dave Dude mention a solution, ref <https://4bear.com/@wx1g/110806497343739940>:
>
> They’d need to add a console screen reader, like Fenrir or ESpeakup to the
> installation image, then have something to type, on the boot command line, to
> start the reader. Debian has done this, on its installation images for a long
> time. Arch now does something like this, too. Thanks for looking into this!
>
> I’m not the right person to do something like this, just thought I should report
> it in case it’s easy to fix.
Hello, I CC this email to bug-guix to open an issue now.
Thank you for the report!
parent reply other threads:[~2023-08-01 10:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87v8e0q7y9.fsf@gmail.com>]
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=87pm47ys1m.fsf@envs.net \
--to=bug-guix@gnu.org \
--cc=64987@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=iyzsong@envs.net \
--cc=simendsjo@gmail.com \
/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).