And I'll honestly be the first to admit that my information comes from handling my friend's somewhat out-of-date phone plus some googling. I don't keep up with what's going on, day to day, and I'd probably bash my head against the wall if I signed up for another high-traffic mailing list about anything, so I'm honestly out of the loop, but this friend I mension, he is fairly in the loop, and he is still rather skeptical of the Google approach to accessibility.
Also, as I mensioned in an earlier message, the fact that Google didn't take the time to make their Apple APps accessible speaks to me about their priorities in the matter. Accessibility was, at one point, a relatively hidden concept that gave the deaf some captions and the lightly visually deficient high contrast display settings. That there are two mainstream companies which include accessibility, by default, in their devices and operating systems is an amazing and wonderful trend. Obviously, Microsoft is on the old trail, as inaccessible as a silent film, but when I compare the hastles of getting mobile Speak on my old Windows Mobile phones, great devices, really, but when I compare the hastles then with what we can do now, I'm very impressed. I don't mean to complain about Google, even if I come down on them harshly. I think that they are making strides in accessibility, and Apple are also taking large steps. The only think that makes me go for Apple is the particular form and priority of accessibility. Either a newer Android phone running Jellybean or an iDevice would be a good choice. It's up to the chooser to make that choice. Honestly, in closing, I feel that this topic, while helpful and interesting, has gotten a bit long and is running in circles. The simple truth is that we've said, I think, all that can be said. I'm not a moderator, but I would ask that, unless there is pertinent information to give or a particular resolution we've helped someone reach, that there be few additional threads under this topic. It is, after all, only related to the purpose of this list in an indirect fashion at this point, though the original intent was quite reasonable and laudible. Signed: Dakotah Rickard On 1/11/13, Rynhardt Kruger <[email protected]> wrote: > Since version 4.1 android's accessibility api is quite up to standard. > Unaccessible apps are mostly do to image buttons without descriptions or > custom components, the same problems as ios. Android's greatest problem is > that people think of it as it was before 4.0. > On 11 Jan 2013 20:09, "Dakotah Rickard" <[email protected]> wrote: > >> I think that one of the biggest problems that I've heard about, but >> not experienced, is that the Android Accessibility app is less >> flexible in what it works with than is Voiceover. What I mean is that >> I don't know how many Google Store apps will work with the >> accessibility suite, because I've never used it, but that could be an >> issue. What's the use of being able to develop apps or find plenty of >> good ones if you can't use any of them with your accessibility suite? >> >> Signed: >> Dakotah Rickard >> >> On 1/7/13, Thomas Ward <[email protected]> wrote: >> > Hi Ben, >> > >> > Either you are mistaken about the cost or you guys in the U.K. are >> > getting seriously ripped off, but Talkback is a free and open source >> > app. As I said in a prior post my wife has it on her Galaxy S3, and >> > someone at Verison demonstrated a couple newer Android phones with >> > Jellybean on them and in neither case would I have to pay for >> > Talkback. Its a free download from Google if it doesn't come on your >> > phone already. So I think you guys in the U.K. are seriously getting >> > screwed if you are getting charged for Talkback. :D >> > >> > >> > >> > On 1/7/13, Ben <[email protected]> wrote: >> >> I have to say I disagree about talkback tom. I looked into this a >> >> while >> >> back and over here at least it seems you have to shell out an extra >> >> 150 >> >> dollars just for talkback... >> >> >> > >> > --- >> > Gamers mailing list __ [email protected] >> > If you want to leave the list, send E-mail to >> > [email protected]. >> > You can make changes or update your subscription via the web, at >> > http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. >> > All messages are archived and can be searched and read at >> > http://www.mail-archive.com/[email protected]. >> > If you have any questions or concerns regarding the management of the >> list, >> > please send E-mail to [email protected]. >> > >> >> --- >> Gamers mailing list __ [email protected] >> If you want to leave the list, send E-mail to >> [email protected]. >> You can make changes or update your subscription via the web, at >> http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. >> All messages are archived and can be searched and read at >> http://www.mail-archive.com/[email protected]. >> If you have any questions or concerns regarding the management of the >> list, >> please send E-mail to [email protected]. >> > --- > Gamers mailing list __ [email protected] > If you want to leave the list, send E-mail to > [email protected]. > You can make changes or update your subscription via the web, at > http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. > All messages are archived and can be searched and read at > http://www.mail-archive.com/[email protected]. > If you have any questions or concerns regarding the management of the list, > please send E-mail to [email protected]. > --- Gamers mailing list __ [email protected] If you want to leave the list, send E-mail to [email protected]. You can make changes or update your subscription via the web, at http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/[email protected]. If you have any questions or concerns regarding the management of the list, please send E-mail to [email protected].
