Re: boot-time accessibility issues
If dummy was used for monitor type, the screen reader could come up
talking without any monitor attached. Many linux distros including
debian can get a monitor turned on and off during operation and don't
let a screen reader know now we have a working monitor and now we don't
have a working monitor. I'm thinking along these lines to attempt to
make installations bulletproof. On the debian-user list earlier someone
had a monitor that required firmware to run it and debian wouldn't
install without that firmware. I'm not sure with that radeon monitor if
vga normal could have been run on boot to eliminate the firmware
complaint.
On Thu, 5 Mar 2020, Rich Morin wrote:
> Date: Thu, 5 Mar 2020 03:53:30
> From: Rich Morin <r.d.morin@gmail.com>
> To: debian-boot@lists.debian.org
> Cc: debian-accessibility@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Thu, 5 Mar 2020 09:15:43 +0000 (UTC)
> Resent-From: debian-accessibility@lists.debian.org
>
> Thanks to everyone for considering these questions, offering suggestions, etc. Here are some comments and clarifications.
>
> I don't know all the ins and outs of preseeding, etc. So, I'll talk about use cases. I'm mostly looking for a way to make freshly installed systems (e.g., PC, RasPi) accessible in two situations:
>
> - The user plugs in a keyboard and a pair of headphones.
> - The user SSHs in from another machine on the LAN.
>
> In the first situation, the machine has to have some sort of screen reader, so that the user can hear their commands and the responses. In the second situation, the user can fall back on the screen reader in the other machine.
> In either case, the user can now install whatever additional packages they want (e.g., by means of a meta-package).
>
> John Doe said:
>
> > ... Having the standard image accessible means that all derivatives inherit the support: all kinds of network/cd images, Debian blends, derivative distributions, etc.
>
> I'm in violent agreement with this. The more (kinds of) systems we can make accessible at boot time, the more impact the changes will have.
>
> FWIW, the RasPi folks are already making some strong moves in the direction of accessibility. For example, the "Orca screen reader" section in a recent blog seems quite promising:
>
> A new Raspbian update
> https://www.raspberrypi.org/blog/a-new-raspbian-update
>
> -r
>
>
--
Reply to: