Questions about new roles, and "empty" attributes
Questions about new roles, and "empty" attributes
- Subject: Questions about new roles, and "empty" attributes
- From: Håkan Waara <email@hidden>
- Date: Fri, 22 Sep 2006 13:28:18 +0200
Hi all,
I'm implementing an abstract class that will handle accessibility in
our application. It is not subclassing NSView or any existing
implementations.
I have a few general questions:
* To make it easy, our base class is returning a static array of a
bunch of attributes we respond to.
Now, sometimes we're asked for an attribute we have no content for -
is it preferred then to return nil or @""? An example is the
AXDescriptionAttribute.
* We'll probably end up having to implement a few new roles. Mostly
they relate to things like web content (maybe a role for "diagram", a
role for "alert" (in the sense of an alert in a web app, etc)).
Now, will accessible providers choke when they see roles they cannot
recognize? Furthermore, is there some process we can go through to
make people aware of these new roles?
In general, both MSAA and ATK have a much wider range of roles that
can be used in different ways. Universal Access has a handful of very
specific roles that have been invented what seems to be ad-hoc for
Apple applications (stuff like all the attributes specific to
rulers). Of course, I'm handful that more roles will be added with time.
Thanks,
Håkan Waara _______________________________________________
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