TRodick93, to android
@TRodick93@tweesecake.social avatar

So fellow #blind #Android folks. I'm not as impressed with my Google Pixel Watch as I thought I would be, and am contemplating switching to a Samsung one. How #accessible are they with #Talkback? I have a #Pixel phone, in case that matters. Thanks in advance!

accessibleandroid, to android
@accessibleandroid@mastodon.social avatar

This is a bit technical, but the following new Google-produced video is really interesting if you want more details about TalkBack 15, including better Braille support.
Updates to Android accessibility features and API: https://www.youtube.com/watch?v=qLCK0HO_tNQ&t=57s
#Android #Accessibility #TalkBack #Braille #AI

accessibleandroid, to android
@accessibleandroid@mastodon.social avatar

Following the latest updates and changes to WhatsApp, we have updated our accessibility notes to address the regression in usability with TalkBack. Please spread the word. https://accessibleandroid.com/app/whatsapp-messenger/ #Android #Accessibility #TalkBack

accessibleandroid, to accessibility
@accessibleandroid@mastodon.social avatar

GAAD 2024 and Google: 8 new accessibility updates across TalkBack, Lookout, Maps and more:
Gemini’s integration with TalkBack, Lookout's Find mode, Look to Speak, etc.:
https://blog.google/outreach-initiatives/accessibility/ai-accessibility-update-gaad-2024
#Accessibility #Google #GAAD #AI #TalkBack

dhamlinmusic, to mastoblind

Ok so so far 14.2 is fine, nothing really major broken, except they somehow fucked proofreading up so it cannot find spelling/grammar errors in general a bunch of the time. @mastoblind

ppatel, (edited ) to android
@ppatel@mstdn.social avatar

Re my last boost, looks like HID support for Braille displays via bluetooth is coming in Android 15. This should let devices like the Brailliant BI 20X, 40X, The Mantis, and the Humanware NLS EReaders connect to devices running Android 15 via bluetooth. Fantastic news.

Clarification: These devices can be connected to Android devices via USB cables right now. The new support is for HID over bluetooth, enabling us to use our displays wirelessly.

accessibleandroid, to android
@accessibleandroid@mastodon.social avatar
changeling, to Discord

@mastoblind Just discovered that in on with , it is possible to use the rotor to access actions on messages. This makes me a happy .

dhamlinmusic,

@changeling @mastoblind I mean the swipe actions were not on #TalkBack until last year, we had menu actions similar to rotor ones for ages and some of those worked in discord for a while now, mostly things like opening the server options from server list to mark as read and such. They have rebuilt the mobile apps 3x in 2 years so not surprised about the delay.

objectinspace, (edited ) to random

deleted_by_author

  • Loading...
  • dhamlinmusic,

    @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?

    dhamlinmusic,

    @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…

    spaciath, to random
    @spaciath@dragonscave.space avatar

    What is the world of HID Braille displays and Android? Will they ever work?

    dhamlinmusic,

    @spaciath Most work via USB, brands like HIMS, Focus, and Orbit work in general because they retain a backup bluetooth protocol, Humanware and Helptech do not offer any backup method for working with devices that cannot use HID wired or wireless which is actually not hard and could be done with an update. The bluetooth HID support for android is out of the #TalkBack teams hands but people could pester #google about this to try and get the people who should be on this to get on it. @mastoblind

    evilcookies98, to random
    @evilcookies98@dragonscave.space avatar

    Does anybody use Google docs? Since I'm cutting apple off, I am no longer going to have access to the program. I used to write everything, and I need a new one pronto

    dhamlinmusic,

    @evilcookies98 Ok so for both word and docs do not use the #android apps, they are both beyond inaccessible with #TalkBack, you can use the browser versions however, and for a lot of things I use this.

    https://play.google.com/store/apps/details?id=com.atomczak.notepat

    accessibleandroid, to accessibility
    @accessibleandroid@mastodon.social avatar

    Updates regarding the Google Gemini app:

    1. Google seems to be fixing the Send button not appearing for TalkBack users. It seems to be server-side as some TalkBack users do have the Send buttons and some don't.
    2. While the app itself is available only on the US Play Store, its global rollout has started and, via side-loading, people can use it in many countries.
    evilcookies98, to random
    @evilcookies98@dragonscave.space avatar

    This is a test to see if Mr. Keyboard and Mr. Phone will really play together. If you can read this, they do.

    dhamlinmusic,

    @evilcookies98 Yep, also read through the #talkback keyboard commands.

    weirdwriter, to webdev

    Short PSA to #WebDev do not, do not, enable #Accessibility overlays! I was just on a website where the AccessiBe toolbar actually made text completely disappear and turn plain text paragraphs into a DIV, somehow, and a hidden element. I'm telling you, seek out an accessibility ready theme instead. #Wordpress has hundreds, and Shopify has them now too. You. Are. Wasting. Your. Money. On these toolbars. #Internet

    dhamlinmusic,

    @weirdwriter National Braille Press moved their store to shopify, it's actually unusable with #talkback.

    dhamlinmusic, to accessibility
    accessibleandroid, to android
    @accessibleandroid@mastodon.social avatar

    New article on Accessible Android: Sorry Google, but Geo-Restricting TalkBack’s Beta Testing Is Not the Right Decision https://accessibleandroid.com/sorry-google-but-geo-restricting-talkbacks-beta-testing-is-not-the-right-decision/

    JustGrist, to android
    @JustGrist@disabled.social avatar

    Hello, fellow people. Somebody asked me about resources for learning how to use on . I am not an android user and I have no idea about any of that. I am looking for guides, tutorials, videos, anything like that. any resources that anybody can offer are appreciated.

    jsoref_using_a_screen_reader, to android

    @Tusky the ability to get to the add account widget isn't available for #Android #TalkBack users

    jsoref_using_a_screen_reader,

    @Tusky the widget reachable in #TalkBack after the available profiles is "Edit profile", it skips right over the disclosure row.

    [Screenshot of 🦣 Tusky running on a Google Pixel 6a] [Menu on the left side of the screen covering content area:] Josh Soref (w/screen read…

    dotsonapage, to random

    Morning Mastodoners! Up playing with my teensy Jelly Star Android phone, which arrived earlier this week and which my wonderful friends Glenn and Megan helped me set up last night. So far my first foray into Android's been an interesting, surprising, and occasionally frustrating experience. And yes, if the name Jelly Star has you thinking of at least one Spongebob character every time you hear it, be assured you're not the only one.

    dotsonapage,

    I'd never used extensively before yesterday, and while typing and some of the gestures are taking some getting used to, I love all the sound effects and haptic feedback. I'm sure I'll be spending a lot of time on @accessibleandroid 's site over the next few weeks. users, got any newbie tips or app suggestions for me?

    meatbag, to android

    Hey, I've talked before about the major thing slowing down Android screen readers: double taps! Just to recap: when you tap the screen, the screen reader waits for some time, just to see if you'll tap again to register a double tap. Only after that time does it register a single tap and tell you what's under your finger. This makes tapping slow! And in normal navigation, it's fine. But in typing, it slows us down a lot! Not only because we have to wait for a fraction of a second for it to register a single tap instead of a double tap, but we also can't touch type so fast because then it will start registering double taps!
    The fix for that is really easy. Just make screen readers ignore the double-tap logic in the keyboard area when the keyboard is up (if you selected any typing mode other than double-tap typing). Because it doesn't need to handle double taps in that area; you just put your finger, and it instantly registers a single tap and tells you what's under your finger. When you lift, it types. That would be great, and I'm very sure it's easy to implement (Oh, how I wish I knew enough Java and Android API to implement that into TalkBack...)
    Because Android itself is not slow at all! In fact, it's instant for all I can notice. And you can test that, even with your screen reader (just so you can notice the reader is artificially slowing itself down).
    First, focus on an item. Now, double-tap. But you need to make your second tap pretty late, just before the timer ends but not much before it, nor after it. You will notice the double tap registers right after your second tap, instantly if you get the timing right, and this is frustrating. The screen reader is intentionally slowing itself down, without giving us an option to change the preset timer or implementing the easy fix for the keyboard to make touch typing possible and fast!
    #Android #AndroidAccessibility #ScreenReader #UserExperience #AccessibilityIssues #Accessibility #Talkback

    devinprater, to android

    TalkBack update 14.1:

    You can now have images described, check spelling in Braille, have Braille automatically scroll at a set interval, and ... that's about all I got before Windows Subsystem for Android broke.

    #android #TalkBack #braille #AI #google

    accessibleandroid, to android
    @accessibleandroid@mastodon.social avatar

    New article on Accessible android: Opinion: Why Samsung/Google TalkBack Separation is Nothing but a Headache https://accessibleandroid.com/opinion-why-samsung-google-talkback-separation-is-nothing-but-a-headache/ #Android #TalkBack

    dankeck, to accessibility

    Did you know that Fedilab, a Fediverse client for Android, has a translation button? It works on post content and also image alt text!

    This example image comes from the German Aerospace Center at @dlr_next .

    @Fedilab #Fedilab #AltText #AlternativeText #a11y #Accessibility #Translation #Translate #Language #Mastodon #Pleroma #Friendica #Pixelfed #Android #AndroidA11y #TalkBack #ScreenReader

  • All
  • Subscribed
  • Moderated
  • Favorites
  • provamag3
  • InstantRegret
  • mdbf
  • ethstaker
  • magazineikmin
  • GTA5RPClips
  • rosin
  • thenastyranch
  • Youngstown
  • osvaldo12
  • slotface
  • khanakhh
  • kavyap
  • DreamBathrooms
  • JUstTest
  • Durango
  • everett
  • cisconetworking
  • Leos
  • normalnudes
  • cubers
  • modclub
  • ngwrru68w68
  • tacticalgear
  • megavids
  • anitta
  • tester
  • lostlight
  • All magazines