Re: boot-time accessibility issues
Apple solved this problem back in 2006. That was when Mac OS Tiger 10.4
became available. What Apple did was to put a message asking for
language to be used on the screen for about 10 seconds I think. If that
message didn't get a keyboard response then VoiceOver got turned on
since Apple figured someone who couldn't see the screen then needed
VoiceOver turned on to do the installation.
On Mon, 2 Mar 2020, Samuel Thibault wrote:
> Date: Mon, 2 Mar 2020 10:57:18
> From: Samuel Thibault <sthibault@debian.org>
> To: Rich Morin <rdm@cfcl.com>, debian-boot@lists.debian.org,
> debian-accessibility@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Mon, 2 Mar 2020 15:57:33 +0000 (UTC)
> Resent-From: debian-accessibility@lists.debian.org
>
> Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit:
> > In another forum, I've been told that Orca is a rather heavyweight solution for providing boot-time speech generation. It was recommended that I consider Fenrir, instead.
>
> Fenrir is also quite heavy-weight, since it brings python. Brltty would
> be much less heavy-weight (but still bring e.g. libicu)
>
> > So, recasting my question, what would it take to make these changes to the default Debian installation?
> >
> > - include Fenrir, with some sort of key combination to activate it
>
> On the Linux console there is currently no way to activate a program
> through a key combination.
>
> What is the installation use case, actually? Is it again the raspi case?
> As mentioned previously the raspi team handles it, so it'd rather have
> to be discussed with them.
>
> > More generally, is there a better way to provide accessibility at boot time?
>
> The question is how to detect that it is needed. We can't just install
> and run a screen reader by default on all Debian systems, so something
> needs to trigger the screen reader startup.
>
> Samuel
>
>
--
Reply to: