107
edits
Mac:Accessibility/UniversalAccess: Difference between revisions
Jump to navigation
Jump to search
add info about older APIs that ATs need to use (hidden in an apple release note)
mNo edit summary |
(add info about older APIs that ATs need to use (hidden in an apple release note)) |
||
| Line 31: | Line 31: | ||
The dictionary (hash table) can be filled with any custom information that the poster of the event wants all receivers to have. [http://developer.apple.com/documentation/Cocoa/Conceptual/Notifications/index.html Go here for more information about notifications in Cocoa]. | The dictionary (hash table) can be filled with any custom information that the poster of the event wants all receivers to have. [http://developer.apple.com/documentation/Cocoa/Conceptual/Notifications/index.html Go here for more information about notifications in Cocoa]. | ||
== AT APIs, and client APIs == | |||
Client applications that want to be made accessible, can do this simply by implementing the NSAccessibility protocol, all in Objective C. | |||
ATs will typically need to use some C APIs in conjunction with those defined in NSAccessibility. The C APIs let the AT get the root accessibility objet from a given pid, among other things. [http://developer.apple.com/releasenotes/Accessibility/AssistiveAPI.html See this older release note for more information.] | |||
== What UA is Missing == | == What UA is Missing == | ||