home.social

#androidaccessibility — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #androidaccessibility, aggregated by home.social.

  1. #Fedle is a daily word guessing game you can play simply by sending Fediverse direct messages.

    Although I'm not a native screen reader user, I decided to try to play with my eyes shut. I used Fedilab, a Fediverse client app, and TalkBack, the screen reader for Android. I was able to solve today's puzzle with just a few difficulties. (Continued) #TalkBack #AndroidAccessibility @Fedle

  2. #Fedle is a daily word guessing game you can play simply by sending Fediverse direct messages.

    Although I'm not a native screen reader user, I decided to try to play with my eyes shut. I used Fedilab, a Fediverse client app, and TalkBack, the screen reader for Android. I was able to solve today's puzzle with just a few difficulties. (Continued) #TalkBack #AndroidAccessibility @Fedle

  3. #Fedle is a daily word guessing game you can play simply by sending Fediverse direct messages.

    Although I'm not a native screen reader user, I decided to try to play with my eyes shut. I used Fedilab, a Fediverse client app, and TalkBack, the screen reader for Android. I was able to solve today's puzzle with just a few difficulties. (Continued) #TalkBack #AndroidAccessibility @Fedle

  4. #Fedle is a daily word guessing game you can play simply by sending Fediverse direct messages.

    Although I'm not a native screen reader user, I decided to try to play with my eyes shut. I used Fedilab, a Fediverse client app, and TalkBack, the screen reader for Android. I was able to solve today's puzzle with just a few difficulties. (Continued) #TalkBack #AndroidAccessibility @Fedle

  5. #Fedle is a daily word guessing game you can play simply by sending Fediverse direct messages.

    Although I'm not a native screen reader user, I decided to try to play with my eyes shut. I used Fedilab, a Fediverse client app, and TalkBack, the screen reader for Android. I was able to solve today's puzzle with just a few difficulties. (Continued) #TalkBack #AndroidAccessibility @Fedle

  6. I have a low vision student that uses android with large text. He doesn't use TalkBack.

    We used the system setting to enlage teh text to a comfortable size for him.

    For some reason, in the Gmail app the text is much larger than on the rest of the phone. Very large, about 8 letters can be displayed per line.

    In some emails the text is cut off.

    Pinching can only increase the text size, and doesn't reveal the truncated text.

    I cannot find a setting within the Gmail app to control the size of the text.

    Am I missing a setting?

    If there is no solution, what is a good mail app that handles the system text size setting better?

    Thanks,

    #AndroidAccessibility #LowVision #android #accessibility

  7. I'm having a very strange TalkBack issue with a new student.

    She has a Samsung A54. When I tried tuning TalkBack on it worked in a very strange manner. A single tap activated buttons. (Not a tap to select an then a single tap to activate). The first tap activates the button. Talkback also doesn't read text when you select it. It does read the text of the a button as you touch it, but as I mentioned the button is instantly activated, so we don't have a chance to know what the button is before it activates.

    I tried installing google's accessibility suit, it didn't make a difference.
    I made sure the activate with a single tap option is off.

    There are other accessibility option that are grayed out.

    Has anyone else seen such weird behavior andis there a way to get TalkBack to work normally?

    #AndroidAccessibility #TalkBack #blind
    @accessibleandroid

  8. Here's an accessibility tip for Fedilab, an Android app for Mastodon, Pixelfed, Friendica, and GoToSocial.

    There are two settings that hide the top bar and compose button when a timeline is scrolled down. This helps to make the UI less cluttered for sighted users. But it makes these controls unavailable to screen readers. (Continued in reply.)

    #Android #Accessibility #AndroidAccessibility #Fedilab

  9. Two years ago at #CSUN I learned about what became my favorite browser extension, BeeLine Reader. I've been a subscriber ever since.

    It's easy to set up on desktop, but has been some struggle to get working on Android. But this week I discovered it works with Microsoft's Edge Canary mobile browser, which has experimental support for extensions. Instructions are here: u.osu.edu/keck.60/2023/03/26/b

    #AndroidAccessibility #Accessibility #Readability #Legibility

  10. When listening to an ebook with TalkBack, if I get a regular notification, the ebook resumes after the notification.

    But if I get a charging notification, the reading does not resume. Sometimes when my phone is on the charger, it will announce the charging level at random times, and TalkBack just stops.

    Does anyone have any experience with disabling charging notifications or getting the screen reader to resume automatically?

    #TalkBack #Android #AndroidAccessibility #AndroidA11y

  11. When listening to an ebook with TalkBack, if I get a regular notification, the ebook resumes after the notification.

    But if I get a charging notification, the reading does not resume. Sometimes when my phone is on the charger, it will announce the charging level at random times, and TalkBack just stops.

    Does anyone have any experience with disabling charging notifications or getting the screen reader to resume automatically?

    #TalkBack #Android #AndroidAccessibility #AndroidA11y

  12. When listening to an ebook with TalkBack, if I get a regular notification, the ebook resumes after the notification.

    But if I get a charging notification, the reading does not resume. Sometimes when my phone is on the charger, it will announce the charging level at random times, and TalkBack just stops.

    Does anyone have any experience with disabling charging notifications or getting the screen reader to resume automatically?

    #TalkBack #Android #AndroidAccessibility #AndroidA11y

  13. When listening to an ebook with TalkBack, if I get a regular notification, the ebook resumes after the notification.

    But if I get a charging notification, the reading does not resume. Sometimes when my phone is on the charger, it will announce the charging level at random times, and TalkBack just stops.

    Does anyone have any experience with disabling charging notifications or getting the screen reader to resume automatically?

    #TalkBack #Android #AndroidAccessibility #AndroidA11y

  14. When listening to an ebook with TalkBack, if I get a regular notification, the ebook resumes after the notification.

    But if I get a charging notification, the reading does not resume. Sometimes when my phone is on the charger, it will announce the charging level at random times, and TalkBack just stops.

    Does anyone have any experience with disabling charging notifications or getting the screen reader to resume automatically?

    #TalkBack #Android #AndroidAccessibility #AndroidA11y

  15. The @thunderbird team just released the first beta of their email client for Android. I've filed two accessibility bugs on GitHub, and within hours one is addressed and will be in the next beta release (with a pleasant thank you note to boot).

    If you feel so inclined, please consider downloading the app and reporting accessibility problems. Especially if you're a native TalkBack user.

    #a11y #Accessibility #AndroidAccessibility #Android #TalkBack #ScreenReader #Thunderbird

  16. We’ve launched a comprehensive database to catalog TalkBack and Jieshuo (CSR) screen reader bugs affecting blind and low vision Android users. Our mission is to raise awareness of these issues and help developers address them more effectively and promptly. Join us in improving accessibility for all! Feel free to add your screen reader bugs to make the database more comprehensive. 🌍 accessibleandroid.com/bugs/ #Accessibility #TalkBack #Jieshuo #AndroidAccessibility

  17. 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