RE: android app development

  • From: "Ken Perry" <whistler@xxxxxxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Thu, 16 Dec 2010 20:59:08 -0500

See I think your 
missing something.  I am not complaining about the IPhone per say.  I am
complaining about Apple.  They have not yet got Braille right on the Mac
book pro I use every day.  How do you suppose they are going to get it right
on an IPhone or a Mac if they refuse to put computer Braille on it.  Believe
me I am in touch with them and they are in no hurry.  Without computer
Braille you have what you have now and its crap.

Would you be ranting about a computer that could print to 5000 different
printers but Oh sorry you can only use one font and only half the
punctuation?  Hell no but you're ok with this?

Ken
ken

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Littlefield,
Tyler
Sent: Thursday, December 16, 2010 4:45 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: android app development

And how long did it take apple to decide to support the braille 
displays? so because apple took forever after people joined the IOrgi 
and android wasn't right up there with them, it's bad?
On 12/16/2010 2:41 PM, Alex Hall wrote:
> I know it is not ideal right now. However:
> 1. This is the first iteration of braille input and output in iOS, and
> the first release of anything is never perfect. At least grade 2
> output is good, the touch cursor works for editing, and so on.
> 2. You can just get a case with a bluetooth (qwerty) keyboard that
> flips out for when you do not want to use the braille.
> 3. At least braille output is there, making it very convenient to look
> up information when it is too noisy to hear the speech, and you can
> even turn off speech and still use braille.
> Sure there are bugs, but I am saying that it is a great deal better
> than Android, and Google did not seem to even make an effort with the
> 2.3 release...
>
> On 12/16/10, Ken Perry<whistler@xxxxxxxxxxxxx>  wrote:
>>    As for the Braille displays on the IPhone it might support them but
just
>> try to type a web address let me explain how you have to do it because of
>> the stupid way Apple did Braille.
>>
>> Type w three times wait almost 2 seconds sometimes then type low d if you
>> don't wait you will get double d.  then type google. Wait till it catches
p
>> sometimes its fast sometimes it is not type low d again make sure it
catches
>> up or you will get double d.  They did not support computer Braille so
you
>> have to do these stupid work arounds to be able to type.  I would rather
get
>> a tooth pulled with no anesthetic.  So my nice RB18 stays put away and I
>> type on the screen slowly.  Really slow.ly.  With my G2 though I can msn
>> rocket fast and I can even search even though the web browser is iffy
with
>> ideal it is getting better.  I can tell you that in the long run apple
will
>> not hold a candle to Android.
>>
>> Ken
>>
>> -----Original Message-----
>> From: programmingblind-bounce@xxxxxxxxxxxxx
>> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Alex Hall
>> Sent: Thursday, December 16, 2010 2:56 PM
>> To: programmingblind@xxxxxxxxxxxxx
>> Subject: Re: android app development
>>
>> No, I have not used it much, but I have read many reviews, including
>> the recent article about the lack of built in accessibility frameworks
>> all but halting development of better screen readers which could, for
>> example, provide use of the touch screen for standard UI elements.
>> While Android's accessibility may not be Narrator, my point was that
>> it is far behind where Apple is, and the most recent version of
>> Android did nothing to change that, whereas the most recent version of
>> iOS added wireless braille support for just about every
>> bluetooth-enabled display I can think of.
>>
>> On 12/16/10, Littlefield, Tyler<tyler@xxxxxxxxxxxxx>  wrote:
>>> You've apparently not used android much. I know people that use it for
>>> quite a lot, and it does more than narrator does.
>>> On 12/16/2010 11:38 AM, Alex Midence wrote:
>>>> So ironic.  Downright sad, if you ask me.
>>>>
>>>> "In the house of the blacksmith, they use a wooden knife."--Old Latin
>>>> American saying.
>>>>
>>>> "Mechanics' children have broken cars ..."  "... A doctor's family
>>>> never gets cured."--Old proverbs from elsewhere
>>>>
>>>> Alex M
>>>>
>>>> -----Original Message-----
>>>> From: programmingblind-bounce@xxxxxxxxxxxxx
>>>> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Alex Hall
>>>> Sent: Thursday, December 16, 2010 10:30 AM
>>>> To: programmingblind@xxxxxxxxxxxxx
>>>> Subject: Re: iOS development?
>>>> <snip>
>>>> Android has the equivalent of Microsoft Narrator, whereas iOS has
>>>> JAWS, complete with wireless braille display support (which is quite
>>>> good, especially as it is the first braille support for iOS).
>>>> __________
>>>> View the list's information and change your settings at
>>>> //www.freelists.org/list/programmingblind
>>>>
>>>>
>>>
>>> --
>>>
>>> Thanks,
>>> Ty
>>>
>>> __________
>>> View the list's information and change your settings at
>>> //www.freelists.org/list/programmingblind
>>>
>>>
>>
>> --
>> Have a great day,
>> Alex (msg sent from GMail website)
>> mehgcap@xxxxxxxxx; http://www.facebook.com/mehgcap
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
>> __________
>> View the list's information and change your settings at
>> //www.freelists.org/list/programmingblind
>>
>>
>


-- 

Thanks,
Ty

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

Other related posts: