Re: MacOS ScrollView accessibility
Re: MacOS ScrollView accessibility
- Subject: Re: MacOS ScrollView accessibility
- From: Patti Hoa <email@hidden>
- Date: Tue, 26 Sep 2017 12:37:49 -0700
Can you provide the following bits of information via AX Inspector that can
help us diagnose?
1) With the AX Inspector locked on the scroll area (NSScrollView), tell us what
the “Children” attribute returns. Maybe a screenshot of what the popover shows.
2) Assuming you have selected the TurboTax Mac application in the AX Inspector
toolbar target pop down menu, go to menubar Window—>Show Notification to
display the notification logs. Then press tab key to move keyboard focus from
one form to another. See if there’s notification/what notification fires with
each tab press.
3) Lock on one of the forms, see what is returned from the “Class” attribute.
The attribute is under Element section. Is this based off a NSControl, or a
completely custom object based off NSObject? If the latter, then you needs to
post NSAccessibilityFocusedChanged notification and implement Accessibility
UniqueID protocol. Look at NSAccessibility_Private.h for more info about this
protocol
> On Sep 18, 2017, at 1:49 PM, James Craig <email@hidden> wrote:
>
>
>
>> On Sep 17, 2017, at 5:52 PM, Drake, Ted <email@hidden
>> <mailto:email@hidden>> wrote:
>>
>> We have a consistent problem with scroll views not being accessible. For
>> example, a scroll view receives focus and is announced by VoiceOver as
>> “empty, scroll area”. I am not able to enter the scroll area to interact
>> with the child elements. It reminds me of an iOS component that has
>> isAccessibilityElement set incorrectly.
>>
>> We also have a scroll area that includes form elements that are available to
>> tabbing, but VoiceOver doesn’t announce anything when focus moves from one
>> element to another.
>>
>> I’ve looked for information on how to make sure scrollviews are accessible,
>> but I can’t find anything.
>>
>> For instance: https://developer.apple.com/documentation/appkit/nsscrollview
>> <https://developer.apple.com/documentation/appkit/nsscrollview>
>>
>> Here’s what I would like to know:
>>
>> Should we apply a label to the scroll area so the user knows what the
>> container represents? If so, do you use accessibilityLabel or
>> accessibilityHelp?
>
> I’d recommend accessibilityLabel.
>
>> How can we make sure the user can enter a scroll area and interact with the
>> child elements? Is this isAccessibilityElement? Accessibility Inspector says
>> children: empty array, Children in navigation order: empty array, contents:
>> empty array, and keyboard focused: false.
>
> Seems like a parent/child hierarchy mismatch. The child may “point” to its
> parent, but VoiceOver won’t be able to see it unless the parent node is
> “aware” of its children. This might be a problem in some shared code you are
> using across projects.
>
> To determine the solution in your case, it'd be best to get a reduced sample
> Xcode project that demonstrates the bug when built. Will you file a bug
> report and attach the test case project?
>
> Thanks,
> James
>
>
>> Thank you
>>
>> Ted Drake, Intuit Accessibility
>
> James Craig • Accessibility Design & Quality • email@hidden
> <mailto: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
_______________________________________________
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