Mac:Accessibility/UniversalAccess: Difference between revisions

add info about older APIs that ATs need to use (hidden in an apple release note)
(Fix typos and improve style)
(add info about older APIs that ATs need to use (hidden in an apple release note))
 
(One intermediate revision by the same user not shown)
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 ==
Line 46: Line 51:
Feel free to add and improve this introduction, or even copy it to another wiki.  
Feel free to add and improve this introduction, or even copy it to another wiki.  


--[[User:Hwaara|HakanW]] 05:10, 24 May 2006 (PDT)
--[[User:Hwaara|HakanW]]
107

edits