Hi Mark, walking the View tree with getLocationOnScreen() while retrieving element labels might be possible, and is a good idea in itself, but this is more the kind of thing that one would try for a generic accessibility layer, such as for a screen reader that works across all apps (currently limited by security restrictions), or as part of the OS. For a single app it may be too much work for what should be a temporary app-specific solution. Perhaps I am pessimistic, but my estimate is that it would take a significant effort that may run into unforeseen limitations along the road much like even my simple key remapping attempt turned into a time waster. I once looked at something similar to UI-tree walking to obtain icon names at the mouse pointer on the Microsoft Windows desktop, but there it was a royal pain and still did not quite yield the sought information. Unfortunately Google rarely discloses what they are up to, so one cannot know how much of the app-level accessibility patching and bridging will become obsolete in what time frame. For instance, I made my app's UI elements self-voicing before Google released TalkBack, but by now that effort is mostly obsolete. Basically all blind Android phone users and would-be users are now clamoring for something equivalent to the iPhone touch screen experience, but that requires changes to the OS, and we non-Google accessibility developers do not know if or when these are forthcoming.
Thanks The vOICe for Android http://www.seeingwithsound.com/android.htm On Dec 17, 1:00 pm, Mark Murphy <[email protected]> wrote: > On Fri, Dec 17, 2010 at 6:52 AM, blindfold <[email protected]> wrote: > > Thanks Mark. I can easily detect touch events by their coordinates, > > but not so easily identify what UI elements lie underneath - unless I > > define and layout each of these UI elements graphically myself in > > terms of screen coordinates. > > Walk the widgets in the layout and figure out who is on the screen at > your touch coordinates via getLocationOnScreen() (or maybe > getLocationInWindow())? I'm probably being a bit simplistic, but I > would think there should be some way to figure out what is underneath > the touch coordinate. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 > Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
