How to encode Android for the visually impaired?

Question

Does Android support visually impaired users in the same way as HTML HTML tags to provide screen reader input on the Internet?

If so, what is the best practice for coding buttons and ImageViews, etc., so that they can be read using a screen reader?

Answer 1

I do not quite understand your question. An Internet browser or any applications that rely heavily on HTML rendering are not available. This quote is taken from this blog post .

You can enable accessibility features by choosing Settings → Availability and check the Availability box. Although the web browser and application browser are not yet “talking” using these enhancements, we are working on them for upcoming releases.

Android provides screen reader support for many applications, see this wiki page for a list of applications that are known to work well with Android using an open source and open source reader.

I can’t find general guidelines for creating affordable applications, but this LinkedIn group may be helpful. I do not have a LinkedIn account, although I do not know how active the group is.

Answer 2

The best resource I've found in the Android Accessibility API is code walkthrough: https://sites.google.com/site/gdevelopercodelabs/android/accessibility

Answer 3

For more information on creating an affordable application, see http://developer.android.com/guide/practices/design/accessibility.html .

The closest equivalent to HTML ALT is the contentDescription property — set in code or in XML.

If you are creating your own custom control, you need to do some more work to specify other details; More details at the link above.

Most importantly: when you're done, check out TalkBack, Google’s free Android firmware. (It is pre-installed on some Android models, but you can download it from the Android Market if you do not already have it.) You should be able to navigate all the interactive elements of your application using only the directional panel, and TalkBack should read the appropriate values ​​for all the elements how he does it. (He should pick up the Description content and read it here.)

One thing that you need to pay attention to is that, as I recall, the screen reader reads only those things that you can go to, so if you have training text on the page, it may not be read, therefore, you may need to make sure that the contentDescription for other controls is properly descriptive. Of course, consult TalkBack and make sure that you yourself (er, listen to yourself!) If what is being read makes sense.

(As noted in one of the other answers, although Android has an accessibility API, the Android browser does not actually support it (yet), so HTML pages, even correctly marked with HTML code, are not available on Android using the default browser. There are several third-party browsers that add accessibility to HTML, although, for example, the free IDEAL Web Reader application, which appears to wrap the Android HTML control and then adds voice confirmation on top of it, make their default browser fully accessible in some olee later versions ...)