Blind people unable to install Guix System

  • Open
  • quality assurance status badge
Details
2 participants
  • ???
  • Ludovic Courtès
Owner
unassigned
Submitted by
???
Severity
important
?
(name . Simen Endsjø)(address . simendsjo@gmail.com)
87pm47ys1m.fsf@envs.net
Simen Endsjø <simendsjo@gmail.com> writes:

Toggle quote (24 lines)
> 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!
L
L
Ludovic Courtès wrote on 15 Aug 2023 23:39
control message for bug #64987
(address . control@debbugs.gnu.org)
87il9g6l4i.fsf@gnu.org
severity 64987 important
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 64987@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 64987
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch