Re: Should I remove NSTabViews from the hierarchy?
Re: Should I remove NSTabViews from the hierarchy?
- Subject: Re: Should I remove NSTabViews from the hierarchy?
- From: Ricky Sharp <email@hidden>
- Date: Thu, 22 Feb 2007 18:47:58 -0600
On Feb 22, 2007, at 6:34 PM, James Dempsey wrote:
Is the scriptability of the application an important piece of
functionality for your users - or perhaps you are using UI
Scripting more for automated testing of the app?
Scripting would be rarely used. I will have some customers that my
be interesting in UI scripting on occasion (e.g. set up similar
preferences for a group of students)
Note that an assistive app can register for a value changed
notification when the contents of the tab change - so, an assistive
app could be relying on that notification to realize that it needs
to refresh the children of the tab view.
Didn't think about that one. In all cases where I use tabless
tabviews, there is a corresponding "visual" control that can be
manipulated to select a tab. For example, I have a set of four
mutually-exclusive buttons (+, -, x, /) that drive what set of
controls is displayed (addition settings, etc.)
If I remove the tabviews, they could still register for notifications
from the corresponding control. That may be confusing though. Also,
the corresponding control doesn't contain any children, so I could
see a problem there (i.e. what children would they need to refresh if
the parent view (tabview) isn't there).
Each assistive app can determine what it wishes to report. For
instance, VoiceOver does not generally speak groups to the user, or
focus on them. However, again, an assistive app could be perfectly
aware the element is there, just not dealing with it.
UI Scripting is, of course, a pretty direct mapping of the
accessibility hierarchy which leads you to the 'group 1 of group 1
of..." scripts. As a rule, and in this case, I wouldn't sacrifice
the general accessibility of the app to try to make for less
verbose UI Scripting.
Thanks James, this really helps out a lot. I'll keep the deep
hierarchy as-is. I suppose I could always add an attribute (e.g.
title) at some point to the groups so that they can be referred to
either by index or name.
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden