Re: Accessible custom controls
Re: Accessible custom controls
- Subject: Re: Accessible custom controls
- From: Eric Schlegel <email@hidden>
- Date: Fri, 6 Dec 2002 23:50:04 -0800
On Friday, December 6, 2002, at 11:41 PM, Eric Schlegel wrote:
On Friday, December 6, 2002, at 05:18 PM, Raymond Fischer wrote:
Sorry if this is a newbie question, but what is involved in making
custom controls accessible?
Carbon or Cocoa?
Actually, I'm assigning Carbon, since you asked a Carbon question
recently. Basically what's involved is implementing the Accessibility
Carbon events that are documented in CarbonEvents.h:
kEventAccessibleGetChildAtPoint = 1,
kEventAccessibleGetFocusedChild = 2,
kEventAccessibleGetAllAttributeNames = 21,
kEventAccessibleGetNamedAttribute = 22,
kEventAccessibleSetNamedAttribute = 23,
kEventAccessibleIsNamedAttributeSettable = 24,
kEventAccessibleGetAllActionNames = 41,
kEventAccessiblePerformNamedAction = 42,
kEventAccessibleGetNamedActionDescription = 44
You don't have to implement all of them right away; probably the most
important ones to allow accessibility clients to inspect your app are
GetChildAtPoint, GetFocusedChild, GetAllAttributeNames, and
GetNamedAttribute.
We don't yet have any sample control code that implement these carbon
events.
-eric
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.