talkback

[Android]: TalkBack doesn't speak when AccessibilityEvent is triggered

▼魔方 西西 提交于 2020-01-25 06:12:48
问题 I'm creating a custom view (extending View class) and playing with Accessibility API to understand, how it works. Below is my code, where: I check for MotionEvent equal to ACTION_HOVER_ENTER and then inside it send AccessibilityEvent of type TYPE_VIEW_HOVER_ENTER . I'm catching my AccessibilityEvent in onPopulateAccessibilityEvent . Then I'm adding my custom text into event's text, which is added just fine. As a result, when I hover over my view, all is working fine (confirmed by my logs),

Move accessibility focus programmatically

雨燕双飞 提交于 2020-01-22 18:59:46
问题 Is it possible to move the accessibility focus (VoiceOver for iOS and Talkback for Android) to a defined widget when pressing a button? I've tried searching in the Semantics package but I can't find a way to obtain this. It would be enough also to make the screen reader restart the semantics tree from the beginning. I have a PageView with 3 pages and buttons to move back/forward using a PageController . I would like to move the focus to the beginning of the page when this changes using the

Test accessibility (talkback) for application

ぃ、小莉子 提交于 2020-01-13 10:46:21
问题 I am making my application accessibility compliant. for this providing correct data to the accessibility framework by giving android:contentDescription="your string" in xml. Also I have Seen the Android Developer guide on Making Applications Accessible for an overview of what steps you need to take to ensure your application works correctly with accessibility services. Now problem is testing these all in each and every screen taking more time. my app has 30 screens and each time to go to any

How to check if Talkback is active in JellyBean

谁说胖子不能爱 提交于 2020-01-11 03:16:07
问题 This question asked how to know if Android Talkback is active; that worked until Jelly Bean. Starting from Android 4.1, that steps no longer work, because the mentioned cursor is empty. Having this said, I want to ask is if there is a way to do the same checking in Jelly Bean. EDIT I tried to search for TalkBack code and I found it here. For checking if TalkBack is active, I am using the following code: Intent screenReaderIntent = new Intent("android.accessibilityservice.AccessibilityService"

Android TalkBack reading phone numbers in Webview incorrectly

こ雲淡風輕ζ 提交于 2020-01-05 05:26:08
问题 I'm having a minor headache with the TalkBack screen reader service when reading phone numbers in a WebView, and I can't seem to find a solution. This is a snippet of some html code that I am reading into the WebView: <li>Call <a href="tel:18007848669">1-800-QUIT-NOW(1-800-784-8669)</a> for phone support</li> The screen reader reads this as "Call one to eight hundred quit now one to eight hundred link". Is there a way to force it/signal to read it differently? I need it to be read in a more

How to change Android Talkback in case of App name

戏子无情 提交于 2020-01-01 08:45:25
问题 The App I am working on has a name which is mispronounced by the talkback. I am able to fix this within the app by changing the spelling. But if I change the spelling in the android:label in the manifest, it is misspelled on the app icon on the phone. Does anyone have a way around this? 回答1: There is no way to do this. The fix would be for the LaunchScreen to have the ability to read an alternative label, and place it in the content description for the textView that represents your

Testing Accessibility on Emulated Device (Marshmallow)

前提是你 提交于 2020-01-01 04:05:09
问题 I want to test the accessibility of my app in emulator (particularly Talkback ) but it seems that the option is missing in emulator. Here is the screen shot from the emulator in accessibility settings: There are two options "ClockBack" and "QueryBack" which I couldn't find on my phone with the same android version. Here is the screenshot of the accessibility setting of my phone: I searched to learn about "ClockBack" and "QueryBack" to see if they are replacement of Talkback in emulator but I

Android: How to eliminate spoken text from AccessibilityEvents when extending SeekBar?

三世轮回 提交于 2019-12-30 07:13:31
问题 My Android app contains a custom slider control based on the SeekBar , and I want to attach a custom text phrase to my control to explain its use for Accessibility. I have done this successfully using View.setContentDescription(text) , and TalkBack correctly speaks the phrase when I request focus on my slider control from Activity.onCreate . So far, so good. However, when I touch the control, which I believe sets the AccessibilityFocus on my Android API 16 test device, extra words are being

Android: How to eliminate spoken text from AccessibilityEvents when extending SeekBar?

可紊 提交于 2019-12-30 07:13:01
问题 My Android app contains a custom slider control based on the SeekBar , and I want to attach a custom text phrase to my control to explain its use for Accessibility. I have done this successfully using View.setContentDescription(text) , and TalkBack correctly speaks the phrase when I request focus on my slider control from Activity.onCreate . So far, so good. However, when I touch the control, which I believe sets the AccessibilityFocus on my Android API 16 test device, extra words are being

Android 2.3.3 touch by explore

爱⌒轻易说出口 提交于 2019-12-25 07:33:51
问题 I am developing app for blind community. I want to give an option for the user to explore the screen by scraping finger through the screen (exploring by touch). I am unable to find any api to build this functionality. I am trying to achieve this in android 2.3.3 (api level 10). I know in Android 4.1 talkback with 'touch by explore' functionality comes by default, but I want to give this feature to the users who are using below android 4.1 devices. Any ideas are appreciated. 回答1: You may want