• 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
questions about iPhone accessibility dev
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

questions about iPhone accessibility dev


  • Subject: questions about iPhone accessibility dev
  • From: Stephen Hockema <email@hidden>
  • Date: Tue, 11 Aug 2009 14:00:08 -0400

Hi,

I am a newbie with respect to developing for accessibility and have been trying to "retrofit" some of my iPhone apps to make them more accessible. Sorry if these questions are mis-targeted.

Things have gone smoothly for the most part, except for a few bumps. In particular, I have several questions that I was hoping I might answers to here. They are as follows:

1) Is there a programmatic way (i.e., via an api call) to find out if VoiceOver is turned on? I would like to be able to know this because I have many "transient" events (things that pop up onto the screen briefly and then subsequently disappear again) in one of my apps, and I'd like to delay the disappearance if VoiceOver is on. Short of detecting the VoiceOver state, are there other "best practices" for dealing with UI transients?

2) I am struggling with when to use the 2 notifications (UIAccessibilityLayoutChangedNotification and UIAccessibilityScreenChangedNotification). First, since I don't have a 3GS to test on (and Accessibility Inspector seems to ignore these), I'd like to know what VoiceOver does with these. Second, I'm assuming that certain UI events (e.g., when a UIAlertView pops up) trigger these "by default" such that I don't have to explicitly call them. But I don't now which ones. Is there any documentation on this?

3) I ran into a problem using UIBarButtonItems in UIToolbars (about which I filed a bug report, others apparently have too: these seem to have been left out of the accessibility framework by accident). I'm wondering if people have found good work-arounds for this problem for this for the time being. I've tried several things, none of which work or work well (especially with "custom" buttons). The best thing I've come up with is to make my own UIToolbar, which is pretty hacky.


Thanks in advance for any information you can provide!

  Steve

_______________________________________________
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


  • Prev by Date: Re: If any of the AXUIElement function fail, is memory for their result holders cleaned up?
  • Next by Date: plugin accessibility
  • Previous by thread: Re: If any of the AXUIElement function fail, is memory for their result holders cleaned up?
  • Next by thread: plugin accessibility
  • Index(es):
    • Date
    • Thread