public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] accessibility, speakup, speech synthesis & /sys
Date: Tue, 14 Jul 2009 08:44:59 -0400	[thread overview]
Message-ID: <20090714124459.GA5034@const.linuxsymposium.org> (raw)
In-Reply-To: <20090714095243.GE2076@elf.ucw.cz>

Pavel Machek, le Tue 14 Jul 2009 11:52:43 +0200, a écrit :
> > > > > If the word is so long that you have to write number of its letters
> > > > > inside... then you are using wrong word.
> > > > 
> > > > Unfortunately that's the word.  If the very notion of accessibility was
> > > > realized by mankind earlier maybe we'd have had a shorter word for it.
> > > 
> > > "speech" would seem good enough substitute.
> > 
> > For the speech case. Then you could have braille, speech recognition,
> > etc.
> 
> Well, but maybe braile and speech recognition _don't_ belong together? 

They are often used together.

> > > > I'd actually say it's particularly not adequate.  Try to feed your dmesg
> > > > to a speech synthesizer and try to understand it.
> > > 
> > > Do you really expect blind people to do kernel hacking?
> > 
> > They do.  Why shouldn't they be able to?
> ...

Yes, "..."

I'm amazed that you could think that blind people shouldn't do kernel
hacking?  Why shouldn't they?  Actually they could be even better at
it that sighted people, precisely because kernel stuff is mostly about
stuff that you can't see.

> > > > > You know... "normal" consoles (such as vt) do fail sometimes, too.
> > > > 
> > > > Yes, and in such case sighted and blind users are on equal basis.  In
> > > > that case there is no need for a particular support for blind people.
> > > 
> > > You know, we do not translate kernel messages into other languages,
> > > either. So maybe we should make sure that Linux machines can be used
> > > without reading dmesg, and just do it from initrd?
> > 
> > People can learn english. Blind people can't learn seeing.
> 
> I guess for such case, serial console to machine with running system
> (with speech synthesis/braille/etc) is the way to go. Anything else
> just will not work early enough.

Yes, and so in such extreme case there is no need for particular
support.  But the "initrd is hosed" case is not so rare.

Samuel

  reply	other threads:[~2009-07-14 12:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 22:04 [RFC] accessibility, speakup, speech synthesis & /sys Samuel Thibault
2009-06-30  4:18 ` Greg KH
2009-06-30 13:08   ` Samuel Thibault
2009-06-30 15:34     ` Greg KH
2009-06-30 20:01       ` Samuel Thibault
2009-06-30  6:34 ` Pavel Machek
2009-07-01 22:19   ` Samuel Thibault
2009-07-08  9:35     ` Pavel Machek
2009-07-08  9:42       ` Samuel Thibault
2009-07-12 10:31         ` Pavel Machek
2009-07-12 14:57           ` Samuel Thibault
2009-07-14  9:52             ` Pavel Machek
2009-07-14 12:44               ` Samuel Thibault [this message]
2009-07-19 21:27                 ` Pavel Machek

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090714124459.GA5034@const.linuxsymposium.org \
    --to=samuel.thibault@ens-lyon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox