107
edits
Mac:Accessibility/UniversalAccess: Difference between revisions
no edit summary
(apple seems to have been inspired by me, yay! update to be a intro page to UA instead.) |
No edit summary |
||
| Line 11: | Line 11: | ||
In this way, one could think of UA kind of like a hash table. You ask for an attribute, and get an array, a string, a number, or any other value describing the data you asked for. | In this way, one could think of UA kind of like a hash table. You ask for an attribute, and get an array, a string, a number, or any other value describing the data you asked for. | ||
Users of the UA APIs can easily extend UA just by supporting a new attribute. Whenever someone asks for the value of it. | |||
The first thing an AT typically does, is to ask the [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Protocols/NSAccessibility_Protocol/Reference/Reference.html#//apple_ref/doc/uid/20000945-BCIIHIGG query widgets about the attributes they support]. It can then go on to see which of those that are "settable", i.e. changable by the user. For example, the value attribute of a textfield is settable. | The first thing an AT typically does, is to ask the [http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Protocols/NSAccessibility_Protocol/Reference/Reference.html#//apple_ref/doc/uid/20000945-BCIIHIGG query widgets about the attributes they support]. It can then go on to see which of those that are "settable", i.e. changable by the user. For example, the value attribute of a textfield is settable. | ||