I am implementing a viewpager which has multiple hints to a particular functionality. Now when I activate talkback feature it reads the content in the current view. I also want the talkback to say as "swipe left for more hints" how can I do that.
Implementing accessibility in viewpager android to have a "swipe next for more" kind of thing
2.8k views Asked by user1401232 At
1
There are 1 answers
Related Questions in ANDROID
- Java StreamSource from file in web application project
- XSL-FO Stylesheets & Xalan XSLTransformation Engine
- special characters replaced by question mark
- merge existing columns using CSS
- Debug set on False and not load styles and pictures
- Laravel 5.1 linking style sheet not working
- CSS-Selector with no style-definition changes outcome
- How to add a stylesheet into a WinForm WebBrowser in C#?
- IE equivalent to -webkit-appearance?
- Stylesheet breaking website
Related Questions in ACCESSIBILITY
- Java StreamSource from file in web application project
- XSL-FO Stylesheets & Xalan XSLTransformation Engine
- special characters replaced by question mark
- merge existing columns using CSS
- Debug set on False and not load styles and pictures
- Laravel 5.1 linking style sheet not working
- CSS-Selector with no style-definition changes outcome
- How to add a stylesheet into a WinForm WebBrowser in C#?
- IE equivalent to -webkit-appearance?
- Stylesheet breaking website
Related Questions in TALKBACK
- Java StreamSource from file in web application project
- XSL-FO Stylesheets & Xalan XSLTransformation Engine
- special characters replaced by question mark
- merge existing columns using CSS
- Debug set on False and not load styles and pictures
- Laravel 5.1 linking style sheet not working
- CSS-Selector with no style-definition changes outcome
- How to add a stylesheet into a WinForm WebBrowser in C#?
- IE equivalent to -webkit-appearance?
- Stylesheet breaking website
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Popular Tags
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Easy answer: Don't. This may be a sensible thing to say if the user is using TalkBack Gestures. But what if they're using an attached USB keyboard in conjunction with TalkBack? Is this really the ONLY way to reach those items. Probably not. And if it is, you're app may work great for TalkBack gestures, but is broken for switch access and keyboard access. TalkBack users know how to use TalkBack, switch users know how to use switches, etc. Use good, common design patterns in your layouts, and let users figure things out for themselves.
Let's explain this in a different way. Let's say you have a button. You have marked this thing up so it looks like a button. Do you have a big sign next to your button that says "HEY, CLICK YOUR MOUSE HERE TO ACTIVATE THIS BUTTON"... no of course not. Users know how to use buttons. Use reasonable design idioms, and users should understand how your UI works, independent of whether they are using TalkBack, Switches, Keyboards, etc. It is misleading, inappropriate, and actually LESS accessible to include TalkBack gesture specific instructions on how to perform actions.
See WCag 2.0 Guideline 4.1