Find answers to all your questions in the most relevant forums
Discussion lists dealing with users, technologies, and all things between.
Discover groups and organizations for all user needs
Relevant events in the fields of accessibility and inclusive design
Connect developers and testers to build better applications
This listing is a compilation of both questions asked in-site and questions related to accessibility themes gathered from different sources (stackoverflow, UX Stack Exchange).
I have a view that has a long press action handler. I use the content description to set the message Talkback speaks when the view gets focus.
I try to fill a EditText field by using a accessibility service like DashLane or some other apps which are using accessibility service.
I have the latest version of Talkback and its announcing "My Top level Text Heading". Android native behaviour is adding "Heading" for my top level elements.
My last question about the same topic was not clear enough and was put on hold by c
My users will be using TalkBack enabled or some other Accessible Service.
After I open my app, it jumps to the accessibility settings.
I am trying to read every item inside a ListView of any application by using AccessibilityInfo class.
I'm using the new TextInputLayout provided by Android.support to do floating label.
I recently included the RatingBar view into a layout and realized it is not compatible with Talkback (it is not accessible).
If you see an error or omission or if you have any other comments, please let us know