mmorciegov / android-wifi-tether

Automatically exported from code.google.com/p/android-wifi-tether
7 stars 3 forks source link

Improve accessibility #384

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I'm a blind screen reader user and developer wishing to use this app, and am 
running into a few issues that make this less accessible and more difficult to 
use.

1. The start/stop tethering controls aren't focusable via the keyboard. I can 
hit them, but this involves poking the screen at pseudo-random, and sometimes I 
press the wrong button.

2. Many other controls and details are also unfocusable.

I would submit a patch myself, but the build process looks a bit more 
complicated than for most Android projects. If build instructions are 
available, though, then feel free to point me to them and I'll try working on 
patches. I'm running under Ubuntu Lucid now so probably have most of the tools 
needed to build the app. But it may be easier to fix these issues yourself than 
to help me set up a build environment. Here's how:

1. Make the various control/display elements android:focusable="true".

2. The start/stop tethering widgets appear to be plain images. Making these 
ImageButtons would solve their focusability issues I'd think, but if you don't 
wish to do this, then simply set android:contentDescription to "Click to 
start/stop tethering." This assigns a textual description to your images that 
won't show up on the screen and clutter your interface.

3. It may be necessary to call requestFocus() on one default widget. So, for 
instance, the "start tethering" button might make a good default focus when the 
activity is started and tethering is off.

4. You seem to have an image for radio status. In addition to making this 
focusable, if it is intended to convey information, call the 
setContentDescription() method on the image to set a description in keeping 
with what the image should convey. So, for instance, if you use an image to 
convey that the radio is disconnected, set it to something like "Radio: 
disconnected". That and making it focusable is all that is needed to make this 
control accessible--just a few lines of code.

Thanks. Let me know if you have any further questions or wish me to test any 
builds.

Original issue reported on code.google.com by ndari...@gmail.com on 12 Jun 2010 at 2:38

GoogleCodeExporter commented 9 years ago
Thank you for your suggestions. I'm currently pretty busy with other stuff but 
I'm planning to make these changes in the near future.

Will keep you up-to-date.

Thanks.

Original comment by harald....@gmail.com on 21 Jun 2010 at 5:03