public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Juan Hernandez" <blindmagik@gmail.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: debian gripes, accessibility, and labels, was: Re: IntegratingSpeakup/ESpeakup into Debian boot process
Date: Thu, 9 Apr 2009 14:06:58 -0700	[thread overview]
Message-ID: <C9BFB944DA1E4776B17014EC0787C40A@belgarion> (raw)
In-Reply-To: <20090409062957.GA19592@debian-hp.lan>

In terms of disability labeling, I think visually impared is to vague.  I
like blind for totally blind people, and partial for people who have site.

But  I've always hated disabled, I like the term diffaabled.  Differently
abled.  Disabled emplies we can't do sometime, diffabled emplies we do it
differently.

Take care.

 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Daniel Dalton
Sent: Wednesday, April 08, 2009 11:30 PM
To: speakup@braille.uwo.ca
Subject: Re: debian gripes, accessibility, and labels, was: Re:
IntegratingSpeakup/ESpeakup into Debian boot process

On Wed, Apr 08, 2009 at 08:50:06PM -0700, Gregory Nowak wrote:
> On Thu, Apr 09, 2009 at 01:08:55PM +1000, Daniel Dalton wrote:
> > First, I don't think the term "handicapped" is a good one.
> 
> Interesting that we should get onto that topic. I personally am not 
> that hot on the term disabled, it always makes me think of a car by 
> the side of the road, with both blinkers flashing. I suppose we could

No neither am I... It's not exactly true, how is a blind person disabled...

> have a lively discussion for days on end, about how we should label 
> ourselves, or about how others should refer to us, and we'd probably 
> never reach a consensus.

We could, and I think your right! :) I personally think "vision impaired" is
fine.

Daniel.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Integrating Speakup/ESpeakup " Jason White
 ` Daniel Dalton
   ` Cheryl Homiak
     ` Daniel Dalton
 ` Samuel Thibault
   ` Samuel Thibault
 ` Gaijin
   ` Cheryl Homiak
     ` Jason White
   ` Daniel Dalton
     ` Samuel Thibault
       ` Daniel Dalton
         ` Chuck Hallenbeck
     ` Gaijin
       ` Samuel Thibault
       ` Gregory Nowak
       ` Integrating Speakup/ESpeakup into Debian boot process, part 2 Gregory Nowak
         ` Gaijin
           ` William Hubbs
             ` Gaijin
       ` Integrating Speakup/ESpeakup into Debian boot process Daniel Dalton
         ` debian gripes, accessibility, and labels, was: " Gregory Nowak
           ` Daniel Dalton
             ` Juan Hernandez [this message]
               ` debian gripes, accessibility, and labels, was: Re: IntegratingSpeakup/ESpeakup " Georgina Joyce
       ` Integrating Speakup/ESpeakup " Kerry Hoath
   ` Michael Whapples
     ` Samuel Thibault

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=C9BFB944DA1E4776B17014EC0787C40A@belgarion \
    --to=blindmagik@gmail.com \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).