Re: firefox for android not accessible

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.
> 
> 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.
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.
The accessibility api hasn't had any changes since it's first release in Android 1.6.  Other google programmers ignore the existing accessibility apis.
I've watched more than one google app become less accessible with new releases.  It's to the point where I'm afraid to update google apps because I'm afraid I'll loose access to more features.

At this point, I don't know what else to do but try to get access to Android despite google.  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.

          Kenny