Re: Making children of StaticText accessible
Re: Making children of StaticText accessible
- Subject: Re: Making children of StaticText accessible
- From: Christiaan Hofman <email@hidden>
- Date: Tue, 22 Apr 2008 19:12:29 +0200
On 22 Apr 2008, at 6:54 PM, Mike Engber wrote:
Yes, hit testing by default will start with the deepest view. This
is because it utilizes NSView's hitTest method. To work around this
you'd could subclass of NSWindow and override the
accessibilityHitTest method.
I'd like to keep things in the view itself. It would also make it more
self contained.
Alternately, you could try overriding the NSView method, hitTest, in
your grouping view.
-ME
That doesn't sound like a good solution, it would probably completely
mess up mouse events.
I think I will go with my original idea to make my AXStaticText view
an AXGroup containing a proxy child with role AXStaticText referring
back to the original accessibility implementation. It's a bit messy,
but it works.
Christiaan
On Apr 22, 2008, at 8:11 AM, Christiaan Hofman wrote:
On 22 Apr 2008, at 12:39 AM, Mike Engber wrote:
On Apr 21, 2008, at 11:01 AM, Christiaan Hofman wrote:
As for the main text, it already implements full support for the
(parametrized) attributes for StaticText. This is also the reason
why I cannot change the role to Group, because I really don't
want to reimplement this (as this is a huge task, as you say).
You don't necessarily have to take this existing class and try to
remake it into a group. You could create an enclosing view (e.g. a
group) whose children are this existing class plus the children
you're adding.
This solution does not work either. VoiceOver still does not see
the children. It seems to me that VoiceOver starts hit testing in
the top view below the mouse, which is still the original view and
not the enclosing view. So it won't ask this superview for hit-
testing but rather the original view, and it won't find the children.
Christiaan
That doesn't sound like a great solution to me. But, if you're
absolutely determined to "force" assistive apps to pay attention
to your children it might be the only way to make it happen.
I think it's also likely that someone from the VoiceOver team
would have something (negative) to say about using a non-standard
accessibility hierarchy in order coerce as certain behavior from
VoiceOver.
-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