I've been musing about a comment Samuel Thibault made a while back:
> On Mar 2, 2020, at 07:57, Samuel Thibault wrote:
>
> Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit:
>> ... More generally, is there a better way to provide accessibility at boot
>> time
The idea of detecting the presence (or absence) of a blind-related device seems
worth pursuing, even if there are some issues to be resolved.
For example, following Jude's notion of checking for a monitor, maybe Avahi and
SSH could be enabled whenever a monitor isn't found. For that matter, ena
Jude DaShiell said:
> If dummy was used for monitor type, the screen reader could come up talking
> without any monitor attached. ...
I can think of a couple of issues with this approach. First, there are various
reasons for leaving a monitor off a system. For example, if a RasPi is being
us
> On Mar 5, 2020, at 03:30, Samuel Thibault wrote:
>
> One thing I am missing in your description is: how is the system getting
> installed in your use case? Is it installed by the blind user himself,
> or by somebody else?
Ideally, the system hardware and software could be installed and config
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) acce
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. So, recasting my question, what would it take to make these
changes to the default Debian installation?
- include Fenrir,
velopment teams, but
it seems logical to start at the headwaters (Debian), then move downstream.
> On Feb 24, 2020, at 14:41, Samuel Thibault wrote:
>
> Rich Morin, le lun. 24 févr. 2020 08:22:06 -0800, a ecrit:
>> The first notion has to do with the initial accessibility of the sy
7 matches
Mail list logo
