Thanks for checking this out!
We have been getting very positive feedback from early adopters in the
Android blind user community. It is very exciting (and scary).
On 05/11/2012 09:13 AM, Martijn wrote:
I don't believe it is a major performance issue. It also depends what
you mean by "turned on". Accessibility has been linked at build time
almost since we started working on native fennec.
The addition in Nightly is one check during startup to see if Android
accessibility is enabled, if it is, it goes in to special accessibility
mode and sends out platform accessibility events. If it is not enabled
than there should be no extra performance cost since nothing extra is done.
> Btw, I tried getting this to work on my Galaxy Nexus and on the Galaxy SII.
> On the Galaxy SII it doesn't seem to work at all.
> On the Galaxy Nexus, I get to hear some clicking and other weird
> sounds when browsing/scrolling, but I don't get to get text to be
> Is that expected?
The speech is driven by pressing the arrow keys on the dpad.
> What is a d-pad?
The d-pad is the directional controller (or trackball) that some devices
have. If the device has a keyboard, the arrow keys could be used as the
d-pad. Since the Galaxy Nexus and GS2 don't have physical keypads, you
need to use the virtual one that is provided with the eyes-free
keyboard, look for it in the store (or read marco's post above). It is a
silly solution, I know but it is what a11y looks like in Android
pre-ICS. ICS phones have more accessibility features, but we don't
support them yet.