Re: Enabling scrolling (when the scroll area is a child of a list)
Re: Enabling scrolling (when the scroll area is a child of a list)
- Subject: Re: Enabling scrolling (when the scroll area is a child of a list)
- From: Jonathan Giles <email@hidden>
- Date: Wed, 19 Mar 2014 16:37:15 +1300
- Organization: Oracle
Jonathan,
Thanks for the reply. I decided not to follow up immediately in case
there was someone with a differing opinion, but it seems like there is
no other feedback. Thanks very much for giving your insights into the
scroll functionality.
I will go back to my team and see what their thoughts are. To me it
seems like it would be a big shame to not provide the correct (expected)
accessibility hierarchy to Mac OS, but if there are few people using it
then perhaps that is an option (rather than mangling our code to meet
the only way I know to enable this functionality.
Thanks,
Jonathan Giles
On 14/03/2014 2:45 p.m., Jonathan C. Cohn wrote:
> As a fairly advanced voice over user, I've never found a reason to use this going feature of voice over. Therefore, I do not believe he need concern yourself too much with this other functionality seems to be working. I hope I'm not mistaken. Thanks,
> Jonathan
>
> Sent from my iPhone
>
>> On Mar 13, 2014, at 9:30 PM, Jonathan Giles <email@hidden> wrote:
>>
>> Hi all,
>>
>> I'm a newcomer to this list, the world of accessibility, and to the
>> world of Mac, so please excuse any foibles :-)
>>
>> I'm working on a project to enable accessibility in a UI toolkit, and
>> have come across a situation I don't know how best to handle. In our
>> toolkit, for historical reasons, we have our list/tree/table/etc
>> components contain a scrollpane, rather than the perhaps more common
>> approach of having a scrollpane contain the list/tree/table.
>>
>> Based on the best of my sleuthing ability, it seems to me that the mac
>> voice over software will only allow for scrolling (VO+Shift+S, then
>> up/down) if the AXScrollArea wraps the list, etc. I was able to prove
>> this by hacking our accessibility code, such that the accessibility
>> hierarchy in these ui components reports the parent / children
>> relationship as Mac OS expects it, but that becomes mucky _really_ fast.
>> It isn't an option to change the hierarchy of our ui components either,
>> unfortunately.
>>
>> I was wondering if you accessibility experts had any better advice on
>> how to enable scrolling in this situation? There is a very high
>> likelihood that I have overlooked something obvious, and I would really
>> appreciate it if you could tell me what it is :-)
>>
>> Thanks,
>> Jonathan Giles
>> _______________________________________________
>> 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
_______________________________________________
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