Re: Custom table cells and NSAccessibilityExceptions
Re: Custom table cells and NSAccessibilityExceptions
- Subject: Re: Custom table cells and NSAccessibilityExceptions
- From: Bill Cheeseman <email@hidden>
- Date: Tue, 11 May 2010 17:20:24 -0400
On May 11, 2010, at 4:40 PM, Christiaan Hofman wrote:
> Are they all required? And what to do when some attributes don't have aren't meaningful or can't be supported in a particular case? For instance I have a situation where I want to represent a text, but I have no way to get the layout of the text, so I can't implement attributes like NSAccessibilityRangeForPositionParameterizedAttribute.
I think it is fair to say that your application's design should dictate what accessibility features you can or will support, rather than the other way around. Accessibility is what I think of as a "secondary" feature. Your primary responsibility is to design and write an application that performs whatever operations you have defined for it. Then, in order to make it easy for persons with disabilities to get as much value as anybody can get out of your application, you implement whatever accessibility features will let them perform the operations that your application is capable of performing.
Using accessibility, a person with disabilities should be enabled to do neither more nor less than any other person can do with your application. For example, if your application doesn't need or can't get layout information for anybody's use, then you shouldn't try to make layout information available for a person with disabilities. If you're concerned that somebody might be surprised by what your application can't do, document it.
I think this is the real reason why the "required" and "optional" lists in the newest accessibility document aren't complete. It's because they can't be complete. Apple has listed some "required" attributes for some kinds of UI elements because the nature of the element and the attributes makes clear that certain things are required. For example, every UI element must have a role, and every window must have a position and a size, because those attributes are part of those elements' Platonic idea. There is no such thing as a window without size or position. But in the case of other elements and attributes, it all depends on the application.
--
Bill Cheeseman - email@hidden
_______________________________________________
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