search

agwells / dotdash-keyboard-android

The world's most popular open source Morse code keyboard for Android! (probably)
GNU General Public License v3.0
32 stars 4 forks source link

Accessibility request #11

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi developer,
I do not want to present any issues, I have an accessibility request for the 
blind users of Android platform.
I tried to contact you via the e-mail address available on Google Play, but the 
message could not be successfully send to you. Your domain gave it back.
I prepared the message with detailed instructions ,so can you please send me 
the correct e-mail address?
plchterminator@gmail.com
Thanks so much for your answer.
Matej Plch

Original issue reported on code.google.com by plchterm...@gmail.com on 5 Jul 2012 at 9:46

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi Matej,

Sorry for taking so long to get back to you! I've read the email you attached 
to your comment. I'll check out the accessibility API and see what I can do. I 
don't have access to a physical Ice Cream sandwich device at present, but I can 
run Ice Cream sandwich in an emulator as part of the Android developer's kit.

It's interesting that the screen reader only showed you three keys, because 
there are actually five keys on the main screen of the keyboard. It sounds like 
it's only reading the bottom three, which are Caps Lock, Space, and Delete; and 
it's not reading the dot and dash at all, which are in the upper row of the 
keyboard. I wonder if this is because their label is a single punctuation mark 
(a period, and a hyphen), or whether it's because I'm using non-standard 
keycodes for them.

It's also worth noting Dot Dash has a known issue with Ice Cream Sandwich, 
which is that the Cheat Sheet screen doesn't display properly. It's supposed to 
pop up a Morse code cheat sheet if you swipe upwards from the keyboard; this 
functionality doesn't work in Ice Cream sandwich. I may need to rewrite the 
cheat sheet to read properly in a screen reader anyhow, though.

Original comment by aaronwells on 2 Sep 2012 at 11:50