Re: Index information on iOS
Re: Index information on iOS
- Subject: Re: Index information on iOS
- From: Clare Kasemset <email@hidden>
- Date: Mon, 19 Feb 2018 10:29:53 +0900
> On Feb 18, 2018, at 2:04, Paul Adam <email@hidden> wrote:
>
> Is UIAccessibilityTraitTabBar used to make a custom tab control speak like a
> segmented control?
It makes a custom tab control speak the same way we speak tab bars, with index
info.
>
> Do I have to apply it to a container view for buttons?
Yes, and then accessibility elements within the container view are considered
the tab buttons.
> I can't just put it on a button right? It does not appear to do anything.
Are you seeing that it does nothing when set on a button, or on a container
view?
>
> I don't see any documentation on UIAccessibilityTraitTabBar.
>
> Thanks!
>
>> On Feb 12, 2018, at 5:51 AM, Clare Kasemset <email@hidden
>> <mailto:email@hidden>> wrote:
>>
>> If your control is a custom tab bar, you can use the
>> UIAccessibilityTraitTabBar trait as well, and that will speak index
>> information for you.
>>
>>> On Feb 12, 2018, at 10:53, Paul Adam <email@hidden
>>> <mailto:email@hidden>> wrote:
>>>
>>> The All and Missed buttons are segments inside the UISegmentedController.
>>> So it's one control with the number of segments you want. I'm using it as a
>>> Good Example for Tabs in a11y demos because it handles the selected state
>>> and the index like a tablist and aria-selected.
>>>
>>> There's no Accessibility traits, it's just the standard control that
>>> provides all the features for free. Button trait, selected, trait, and
>>> index of segments is included for free with the control.
>>>
>>> Hope this helps!
>>>
>>>
>>> Paul J. Adam
>>>
>>>> On Feb 11, 2018, at 7:23 PM, Jamal Mazrui <email@hidden
>>>> <mailto:email@hidden>> wrote:
>>>>
>>>> Thanks, Paul. Can you also tell me whether any particular
>>>> accessibilityTraits have been applied in that example? I reviewed the
>>>> documentation you referenced and am trying to understand whether the
>>>> segmented control is a container for the All and Missed buttons, whether
>>>> the components of the control are automatically considered buttons by
>>>> VoiceOver, or whether traits were applied to give them a button role.
>>>>
>>>>
>>>> Jamal
>>>>
>>>>
>>>> On 2/11/2018 2:59 PM, Paul Adam wrote:
>>>>> Hey Jamal, you can use a UISegmentedControl to get the "2 of 3" behavior.
>>>>> https://developer.apple.com/documentation/uikit/uisegmentedcontrol
>>>>> <https://developer.apple.com/documentation/uikit/uisegmentedcontrol>
>>>>>
>>>>> The All and Missed buttons are a UISegmentedControl.
>>>>>
>>>>> There may be some other way to do it in swift code that others might
>>>>> know?
>>>>>
>>>>> Paul J. Adam
>>>>>
>>>>>> On Feb 11, 2018, at 4:14 PM, Jamal Mazrui <email@hidden
>>>>>> <mailto:email@hidden>> wrote:
>>>>>>
>>>>>> How should controls be coded on iOS so that VoiceOver speaks index
>>>>>> information?
>>>>>>
>>>>>>
>>>>>> As an example, consider the built-in Phone app. When the Recent tab is
>>>>>> selected, there are two buttons, All and Missed, presenting choices as
>>>>>> to whether all calls should be shown or only missed ones. When the All
>>>>>> button has accessibility focus, its identification by VoiceOver ends
>>>>>> with the phrase "1 of 2". For the Missed button, VoiceOver says "2 of
>>>>>> 2".
>>>>>>
>>>>>>
>>>>>> Such index information is useful in multiple ways: indicating that the
>>>>>> buttons are part of a group of choices, conveying the size of the group,
>>>>>> and informing the user about the current position in the group. Just
>>>>>> placing buttons consecutively in an app, however, does not seem to
>>>>>> result in index information. What else is needed?
>>>>>>
>>>>>>
>>>>>> Jamal
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>> Accessibility-dev mailing list (email@hidden
>>>>>> <mailto:email@hidden>)
>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>
>>>>>>
>>>>>> This email sent to email@hidden <mailto:email@hidden>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Accessibility-dev mailing list (email@hidden
>>> <mailto:email@hidden>)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>>
>>> This email sent to 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