I have a text-view next to a seekbar. The seekbar is accessible and announces its current value. The text-view also shows this value. For accessibility, I'd like to make the text-view not accessibility-focusable, since the seekbar already is (no use in stating the same thing twice).
However, when adding *android:accessibilityFocusable="no"* to the layout xml, I get this error: *No resource identifier found for attribute 'accessibilityFocusable' in package 'android' page_slider_layout.xml /KnfbBlio/res/layout line 37 Android AAPT Problem*
The project build target is 4.1 (api level 16). The targetSdk in the AndroidManifest.xml is set to 16 as well.
There's no accessibilityFocusable attribute in the documentation, at
least based on a simple search. I don't see anything quite like it in
the list of XML attributes for View. Where did you find this?
On Tue, Jul 31, 2012 at 10:59 AM, Streets Of Boston
> I have a text-view next to a seekbar. The seekbar is accessible and
> announces its current value. The text-view also shows this value.
> For accessibility, I'd like to make the text-view not
> accessibility-focusable, since the seekbar already is (no use in stating the
> same thing twice).
> However, when adding android:accessibilityFocusable="no" to the layout xml,
> I get this error:
> No resource identifier found for attribute 'accessibilityFocusable' in
> package 'android' page_slider_layout.xml /KnfbBlio/res/layout line 37
> Android AAPT Problem
> The project build target is 4.1 (api level 16).
> The targetSdk in the AndroidManifest.xml is set to 16 as well.
> Any idea what the problem could be?
> Thanks!
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
> There's no accessibilityFocusable attribute in the documentation, at > least based on a simple search. I don't see anything quite like it in > the list of XML attributes for View. Where did you find this?
> On Tue, Jul 31, 2012 at 10:59 AM, Streets Of Boston > wrote: > > Hi,
> > I have a text-view next to a seekbar. The seekbar is accessible and > > announces its current value. The text-view also shows this value. > > For accessibility, I'd like to make the text-view not > > accessibility-focusable, since the seekbar already is (no use in stating > the > > same thing twice).
> > However, when adding android:accessibilityFocusable="no" to the layout > xml, > > I get this error: > > No resource identifier found for attribute 'accessibilityFocusable' in > > package 'android' page_slider_layout.xml /KnfbBlio/res/layout line 37 > > Android AAPT Problem
> > The project build target is 4.1 (api level 16). > > The targetSdk in the AndroidManifest.xml is set to 16 as well.
> > Any idea what the problem could be?
> > Thanks!
> > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to android-developers@googlegroups.com > > To unsubscribe from this group, send email to > > android-developers+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en
I've been trying to update our app to the latest and greatest in JellyBean accessibility. This is one issue I encountered.
I've also been trying to implement some AccesibilityDelegate and AccessibilityNodeProvider implementations of our own custom views to establish a virtual view hierarchy, but without any success. Even the samples (ApiDemos) for accessibility can't handle the accessibility-focus events well (hover events seem to work somewhat better). I wish there were some proper examples - that work! - of how to make a fully accessible (also on JellyBean) custom view with a custom virtual view hierarchy. Do you know of any?
On Tuesday, July 31, 2012 12:45:16 PM UTC-4, Mark Murphy (a Commons Guy) wrote:
> On Tue, Jul 31, 2012 at 12:31 PM, Streets Of Boston > wrote: > > If this is not the way to do it, how would one prevent accessibility > focus > > to a particular control?
On Tue, Jul 31, 2012 at 1:54 PM, Streets Of Boston
<flyingdutc...@gmail.com> wrote:
> I've also been trying to implement some AccesibilityDelegate and
> AccessibilityNodeProvider implementations of our own custom views to
> establish a virtual view hierarchy, but without any success. Even the
> samples (ApiDemos) for accessibility can't handle the accessibility-focus
> events well (hover events seem to work somewhat better). I wish there were
> some proper examples - that work! - of how to make a fully accessible (also
> on JellyBean) custom view with a custom virtual view hierarchy. Do you know
> of any?
On Tuesday, July 31, 2012 12:54:25 PM UTC-5, Streets Of Boston wrote:
> Thank you Mark.
> I've been trying to update our app to the latest and greatest in JellyBean > accessibility. This is one issue I encountered.
> I've also been trying to implement some AccesibilityDelegate > and AccessibilityNodeProvider implementations of our own custom views to > establish a virtual view hierarchy, but without any success. Even the > samples (ApiDemos) for accessibility can't handle the accessibility-focus > events well (hover events seem to work somewhat better). I wish there were > some proper examples - that work! - of how to make a fully accessible (also > on JellyBean) custom view with a custom virtual view hierarchy. Do you > know of any?
> On Tuesday, July 31, 2012 12:45:16 PM UTC-4, Mark Murphy (a Commons Guy) > wrote:
>> On Tue, Jul 31, 2012 at 12:31 PM, Streets Of Boston >> wrote: >> > If this is not the way to do it, how would one prevent accessibility >> focus >> > to a particular control?
If you put your device in Accessibility mode (and on ICS enable 'touch to explore'), then simply touching the screen and moving your finger on the screen will generate hover events instead of move events. Touching the screen with two fingers will generate move events, or double-tapping will generate a single click.
This is for use for people with visual impairments, allowing them to explore the by touching the screen without actually activating the items under their fingers. A second tap or the use of two fingers will activate actions or move stuff around.
On Tuesday, July 31, 2012 3:23:13 PM UTC-4, bob wrote:
> What do you mean "hover events seem to work somewhat better"? What's a > hover event on a touchscreen?
> On Tuesday, July 31, 2012 12:54:25 PM UTC-5, Streets Of Boston wrote:
>> Thank you Mark.
>> I've been trying to update our app to the latest and greatest in >> JellyBean accessibility. This is one issue I encountered.
>> I've also been trying to implement some AccesibilityDelegate >> and AccessibilityNodeProvider implementations of our own custom views to >> establish a virtual view hierarchy, but without any success. Even the >> samples (ApiDemos) for accessibility can't handle the accessibility-focus >> events well (hover events seem to work somewhat better). I wish there were >> some proper examples - that work! - of how to make a fully accessible (also >> on JellyBean) custom view with a custom virtual view hierarchy. Do you >> know of any?
>> On Tuesday, July 31, 2012 12:45:16 PM UTC-4, Mark Murphy (a Commons Guy) >> wrote:
>>> On Tue, Jul 31, 2012 at 12:31 PM, Streets Of Boston >>> wrote: >>> > If this is not the way to do it, how would one prevent accessibility >>> focus >>> > to a particular control?
This is an internal attribute that you can't use. Unfortunately ADT
doesn't properly ignore those when it reads the framework attributes
and offers it to you.
I don't know of any other options for you. Sorry.
On Tue, Jul 31, 2012 at 7:59 AM, Streets Of Boston
> I have a text-view next to a seekbar. The seekbar is accessible and
> announces its current value. The text-view also shows this value.
> For accessibility, I'd like to make the text-view not
> accessibility-focusable, since the seekbar already is (no use in stating the
> same thing twice).
> However, when adding android:accessibilityFocusable="no" to the layout xml,
> I get this error:
> No resource identifier found for attribute 'accessibilityFocusable' in
> package 'android' page_slider_layout.xml /KnfbBlio/res/layout line 37
> Android AAPT Problem
> The project build target is 4.1 (api level 16).
> The targetSdk in the AndroidManifest.xml is set to 16 as well.
> Any idea what the problem could be?
> Thanks!
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
