Re: Minimum events and attributes to support to make a custom view accessible
Re: Minimum events and attributes to support to make a custom view accessible
- Subject: Re: Minimum events and attributes to support to make a custom view accessible
- From: David Niemeijer <email@hidden>
- Date: Wed, 15 Dec 2004 17:41:50 +0100
Hi Bill,
At 17:08 -0500 14/12/04, Bill Cheeseman wrote:
2004-12-14 4:34 PM, David Niemeijer at email@hidden wrote:
> http://developer.apple.com/releasenotes/Accessibility/AssistiveAPI.html
The document above is strictly for writing assistive applications, not for
making your application accessible. Keep the distinction in mind; it is
fundamental.
Yep, but most of the constants apply in both situations and it has a
nice table showing the different attributes with associated value
types and description.
The Cocoa NSAccessibility informal protocol. It contains information that
may help you even if you aren't writing a Cocoa app. There are actually two
documents:
/Developer/Documentation/Cocoa/Conceptual/accessibility/index.html and
/Developer/Documentation/Cocoa/Reference/ApplicationKit/ObjC_classic/Protoco
ls/NSAccessibility.html.
ok, thanks.
By the way, if you find cases where UI Browser is giving you less
information than UI Element Inspector, tell me about it. It shouldn't
happen.
It was an issue with my app (now fixed), UI B and UI Inspector were
giving the same result.
david.
_______________________________________________
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