Re: NSTableView custom accessibility attribute
Re: NSTableView custom accessibility attribute
- Subject: Re: NSTableView custom accessibility attribute
- From: Mike Engber <email@hidden>
- Date: Tue, 30 Apr 2013 10:46:44 -0700
On Apr 30, 2013, at 10:04 AM, Dado Colussi <email@hidden> wrote:
>
> An AXGroup of static text would have no descriptions for the elements, right? I think that would be a problem, too.
>
This is entirely under your control. If you want to give your static text elements descriptions, you can. But, normally people don't do that. For static text, assistive apps would normally use their AXValue (which is the text string).
Note - I don't think any ui elements provide AXDescriptions automatically. It always requires some sort of programmer effort; either using IB, accessibilitySetOverrideValue, or just implementing the attribute directly in a custom class.
Your comment makes me think you might not be using AXDescriptions correctly. Usually, elements with AXValues or AXTitles don't need descriptions. A good example where a description would be needed is an icon button. It has no title (or it's the empty string), so you add a description. Another case could be a button where the title is misleading, like a natural logarithm button on a calculator, "ln", should probably be given the description "natural logarithm."
For purposes of automation, I could understand why you might always want to just look at just one attribute, AXDescription. But, that's not how assistive apps (should) work.
-ME
_______________________________________________
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