• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Should I remove NSTabViews from the hierarchy?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Should I remove NSTabViews from the hierarchy?


  • Subject: Should I remove NSTabViews from the hierarchy?
  • From: Ricky Sharp <email@hidden>
  • Date: Thu, 22 Feb 2007 17:54:48 -0600

My application has its own custom UI and all my controls/cells/etc are fully accessible.

Some screen layouts make use of one or more nested tabless tabviews for structure purposes. The hierarchy can thus be a bit deep in places and when doing things like GUI scripting, you have things such as:

set value of UI element "Maximum sum" of group 1 of group 1 of group 1 of window "Settings" to 15


I'm considering going down one of two paths:

(1) Add a category to NSTabView and implement accessibilityIsIgnored to return NO.
(2) Subclass NSTabView and provide my accessibility overrides against that class.


I'm currently leaning a bit towards (2) since it seems cleaner. Also, this could give me the flexibility in adding a 'flag' ivar as to whether or not to include the group in the hierarchy.

For example, the middle 'group 1' tabview happens to contain all controls that make up addition problem settings. Thus, I could drop some of the groups out and just include one to help organize thing a bit.

So, if dropping all, I would have:

set value of UI element "Maximum sum" of window "Settings" to 15

Or, if dropping all but one, I could have:

set value of UI element "Maximum sum" of group "Addition settings" of window "Settings" to 15.


To my knowledge, every UI element would have a unique title and thus no collisions would occur if referring by name. Thus, I really don't need any of the groups to disambiguate contained controls.



How have others dealt with the accessibility of tabless tabviews? Can you spot any pitfalls in the above approaches?


Thanks,


___________________________________________________________ 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


  • Follow-Ups:
    • Re: Should I remove NSTabViews from the hierarchy?
      • From: James Dempsey <email@hidden>
  • Prev by Date: Re: Debug vs Release Accessibility Issues
  • Next by Date: Re: Should I remove NSTabViews from the hierarchy?
  • Previous by thread: Re: Debug vs Release Accessibility Issues
  • Next by thread: Re: Should I remove NSTabViews from the hierarchy?
  • Index(es):
    • Date
    • Thread