Re: firefox for android not accessible

[re sending to list]

On 25 February 2011 19:21, Kenny Hitt <[email protected]> wrote:
> Hi.
> On Fri, Feb 25, 2011 at 01:55:56PM -0500, David Bolter wrote:
>>
>> Accessibility via extension is a way to move forward on
>> Firefox-for-Android accessibility in my opinion. It isn't the only
>> strategy we're considering.

Complete platform accessibility usable by any app and AT would be so
much better...

>> Kenny, I've been hoping for an Android accessibility roadmap from
>> Google, but I haven't seen one yet. I think the right way to move
>> forward is in collaboration with Google and I encourage us all to
>> think about ways to take positive steps forward.
>>
> I would agree.  The problem is google doesn't seem to be interested in working with others.

Being polite, Android is not open development. They kindly dump code
at certain points.

> Over the last year, I've seen developers as well as users try to move Android accessibility forward only to get ignored.  One of these people has produced an alternative screen reader as well as
> an accessible on screen keyboard.  Neither effort have been excepted by google.  Worse, this guy has filed several bugs that have been ignored.

Sigh!

> At this point, I don't know what else to do but try to get access to Android despite google.

That seems to be the only game Google want to play. Trouble is you'll
get to take the hit merging the next official release

>Sorry for the negative attitude in this post.
> I started out with a positive attitude toward Android, but the last year has been one disappointment after another.

You are not alone I know other users like @ppatel who just can't use
Android as it stands.

I also feel this is really important but can see a way forward.

Steve