I've been having a look to the built-in haptic feedback you can enable trough the KickBack setting on the Accesibility menu. It works like I expected on most of UI elements.
For those who are not aware of what haptic feedback is, it's very simple, just vibrate slighty as the user presses any button/key/field.
Well, my problem is about enabling that feaure on a WebView interface. I made sure to enable it by calling WebView.setHapticFeedbackEnabled(true), but it wouldn't work. I also tried using the native Android Web Browser, but the haptic feedback is not enabled on there either.
I was wondering if someone has some tip on how to manually set that feedback for the WebView, cause I've been having a look to the API, and can't get any idea.
PD: I'm developing for FroYo on a Nexus One with 2.2.1.
Regards!
This is currently not possible since the default WebView control is not accessible. This will be fixed in Android 3.0, according to this blog entry If you must get accessibility working for web content displayed in your app take a look at IDEAL Web Reader It's open source so you may be able to use some of their code or ideas in your own application.
Related
I'm having some trouble getting TalkBack to work with a web view (testing with a Nexus 9 on Android 5.1). I read that TalkBack support was added to web views around the release of Android JellyBean by checking a preference titled "Enhance Web Accessibility." I can't for the life of me find this preference in the system settings.
Focusing on the web view in our application simply reads "WebView" and provides no other options.
Was TalkBack support for web views removed in KitKat? If not, what am I missing here?
Am using Mobile accessibility Plugin to read my customized talkback
My app work fine with Android 4.4.4 . Am using aria-hidden=true to stop default talkback of Mobile accessibility. But with that attribute lollipop doesn't focus to the event and not all reading
Your question is a little unclear. But I can guarantee one thing, this has nothing to do with the "Enhanced Web Accessibility" option. This was an experimental accessibility setting in Android 4.1 - 4.2 and has since been deprecated. This is why you cannot find this setting. What "Enhanced Web Accessibility" did was add some visual elements to help users spot things like Links and such with nice outlines. It has nothing to do with basic TalkBack support for WebViews, which has been supported since TalkBack was released, though it has certainly improved since then, and is still improving.
Now, this doesn't really answer your question. Only removes one of the solutions you seem to have been concerned about investigating. As per your actual solution, your question is a little unclear what your actual problem is. It seems to me you have some sort of event firing in a custom WebView you have created, and this should cause TalkBack to read something out. I await further details to continue this answer, though I suspect that you have not set the WebView's accessibility delegate.
mWebView.setAccessibilityDelegate(new View.AccessibilityDelegate());
It must be set to setJavaScriptEnabled (false);
web components analysis appears to be view.view.
I am a student programmer and the topic my degree work is to finalize one of the input methods for touchscreen devices by visually impaired people (including the blind).
I want to make my application work correct with TalkBack. But I totally don't know, how to do it. I've found the package for accessibility, but it's not clear for me, how to it integrates with TB.
You can start with simple layout with ImageView and add android:contentDescription="your string" as a parameter in xml. Then turn on talkback and click on that image to see what happens.
Use android:contentDescription="Generic Image" in any View with any custom content.
Note: When using ViewGroup, should be careful of clicking through view.
Here is a example: https://github.com/dotrinhdev/AndroidTalkback
As an application developer, you don't need to specifically integrate your app with TalkBack. Instead, you should focus on providing correct data to the accessibility framework. This will ensure that your application works not only with TalkBack, but also with Braille and switch-based accessibility services.
See 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.
You may also want to watch the Google I/O 2012 talk Making Android Apps Accessible, which covers basic application accessibility.
I have a website that I've just created that has a jquery-ui slider bar link removed
The slider bar doesn't seems to work properly on my phone which is an android - it could affect other mobile browsers too.
Is there a way of fixing this?
Thanks
I've just had a look on my phone and it also doesn't work. However, I have noticed in the past that other JavaScript items (on other sites) also don't work, so I don't think it's a specific problem with your site.
In terms of a workaround, you could check the viewer's user agent and display a different selection method if they're on a phone.
I'm developing a web app for android phones and I'm curious if it is possible to initiate call to a user from web interface. So basically, I want to call someone when clicking on their phone number on the web page.
While testing on Samsung GT-I9103, I've noticed that it has this functionality: on a web page, when a user clicks on a number, screen for initiating phone call gets shown. So, there is a way to do what I want. But, this functionality doesn't exist on Sony Ericsson, what makes me believe this really depends on the manufacturer. Am I right?
Also, I've checked phonegap documentation (http://docs.phonegap.com/en/2.2.0/index.html), but can't find what I need.
So, is it possible to do this?
Thanks.
Yes, it is slightly functional through JavaScript, from what I have read.
Refer to:
http://developer.android.com/guide/webapps/webview.html
Section: Binding JavaScript code to Android code
Does anyone have any experience with making an Android app accessible when utilizing PhoneGap? At the very minimum we need to make our apps Section 508-compliant.
I have tried implementing some standard accessibility features (labels for textboxes, adding title attributes to divs, etc). However, when using TalkBack and Expore by Touch in Android, when my PhoneGap app is loaded it just says "WEB CONTENT" - and that's it. Nothing else about my app is spoken aloud.
When the same app runs in iOS with VoiceOver everything works quite well. It reads all of the "title" attributes just fine.
Yeah, I can reproduce that problem as well. It doesn't look like
TalkBack can read things inside the WebView. You should raise an issue
with them:
https://code.google.com/p/eyes-free/issues/list
I'm sure we'd be happy to work with them on it.