@objectinspace At least take little comfort by the fact that you can beta-test the thing. Most of us, geo-restricted or G-restricted, Google style, have no access to betas despite all the talk and the facade of positivity.
@amir I get what you're saying. Not exactly working out for me in this case! I would have to leave the beta. More to the point, I don't believe they will do any more to fix it, so all I can do now is watch helplessly as crippling bugs make it into production despite my warnings. Not that this is my problem. But it sucks to see.
@amir Sorry I just saw this. That is a great list! Although I'm not sure how much Google can do at this point to clear up the situation with Samsung.
Also, I could be wrong but IIRC you can add checkboxes, edits, landmarks, whatever to the fake rotor from customize reading controls?
I don't really understand the thing about offline descriptions. Don't you need to download data with for Voiceover's also? I thought they operated on the same principles.
@amir NVM, just checked and in fact you cannot choose to move by button, checkbox, or field. That's quite a surprising and glaring omission actually. TalkBack knows how to do it, there are keyuboard shortcuts for them. Odd.
@objectinspace Yeah - very strange and equally problematic! Just hope US TalkBack beta testers can do something about it as, with Google, we're not apparently heard.
@amir@objectinspace You cannot join the beta for this without being in the trusted tester program afaik, I’ve been trying to figure out how to for ages.
@dhamlinmusic@objectinspace Well, it's doable only if you are in the USA, the UK, or at most one or 2 other countries. So residents of just 3 or 4 countries can beta-test TalkBack. This is really discriminatory, and equally offensive coming from Google.
@amir@objectinspace Yes, I’m in the US, this is now 3 comments on this thread where I asked how people even get into the beta for it because it's not actually a thing through normal channels. As far as I can tell you have to be in the trusted tester program which joining it itself is unclear as how to go about this, and the routes I have found have been inaccessible as well.
@objectinspace@amir I was worried about that being it…, That one broke with #TalkBack in every browser I tried including chrome and firefox, the select your country drop down would never accept the entry and allow me to continue…
@objectinspace And regarding offline image descriptions my point was that if both require offline data, how is it that VoiceOver's descriptions are much more accurate? If Apple can do it offline so accurately, Google can do the same thing if they want.
@ppatel@amir Yeah I am a little surprised how long it took for them to come up with that considering how long Chrome had autoalt! Still, glad it is here now.
@amir Gotcha. If I had to guess (and I am guessing) Google's model might just be behind Apple's. I'm not sure if they would work on improving that, or switch it to some stripped-down offline version of Gemini. Both seem pretty unlikely, TBH. In the short term, at least.
@objectinspace@amir If this is the android 15 beta it's still developer phase and actual release of Accessibility Suite 15.0 won’t be for at least another 5 months or so, also what’s strange is that #TalkBack is not an app on Pixel side so when it crashes is not the message you would get, what type of device were you running this on?
@objectinspace Oh, that's OK, I ran into an even worse bug, on a supposedly stable version of Talkback, where when I paired my braille display, after a few seconds, Talkback would crash so hard that only restarting the phone would fix it.
Add comment