Re: Question about proper use of NSAccessibility APIs
Re: Question about proper use of NSAccessibility APIs
- Subject: Re: Question about proper use of NSAccessibility APIs
- From: Mike Engber <email@hidden>
- Date: Wed, 11 Jan 2006 10:12:33 -0800
The accessibilitySetOverrideValue:forAttribute: selector is new in
10.4. My application currently targets the 10.3.9 SDK. Is there
another way to programatically set the AXDescription/AXHelp
attributes?
Nothing easy. You'd have to subclass each of the widgets (cells,
controls, ...) in order override the corresponding Accessibility
Protocol methods. This is obviously a big obstacle to accessorizing
your application - which is why we provided
accessibilitySetOverrideValue:forAttribute: in 10.4.
Note that Voice Over only runs on 10.4 or later - so only setting
AXDescriptions when you run on 10.4 or later won't be an issue for
Voice Over. The AXDescription attribute was added because of Voice
Over. The standard apps (e.g. Mail, iChat, ...) don't implement
AXDescription prior to 10.4 either.
Also, I'm getting all kinds of errors and warnings for my
application using Accessibility Verifier. I don't know how to fix
these. One thing that I think would be helpful is if the
Accessibility documentation talked a bit about how to fix some of
these errors and warnings.
For example, I'm getting an error that says 'AXCheckBox - "Top",
Required attribute AXMaxValue is missing'. Why does a checkbox need
an AXMaxValue, and if it needs one, why doesn't interface builder
make it for me? How can I add this?
I don't know much about Accessibility Verifier. As you say, a max
value doesn't make sense for a check box. I don't know if this is a
bug in Accessibility Verifier or if just a misleading message.
-ME
_______________________________________________
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