Re: Popovers on iPad, enhancing/fixing something in text fields
Re: Popovers on iPad, enhancing/fixing something in text fields
- Subject: Re: Popovers on iPad, enhancing/fixing something in text fields
- From: Marco Zehe <email@hidden>
- Date: Mon, 07 Sep 2015 17:57:28 +0200
Thanks, Chris!
Wow, I didn't know you could do that! Very handy! Are there other such nice tricks one can do? I mean, I already learned from your WWDC 2012 session on iOS accessibility that you can do things like set AccessibilityLabel on an NSString, but setting traits on these text ranges is new to me. :)
Marco
This signature should probably be changed some time
> Am 06.09.2015 um 22:59 schrieb Chris Fleizach <email@hidden>:
>
> It sounds like these text segments are close enough to links to probably get the behavior you want
>
> If you implement attributedText on the text field and then set the attribute range like
>
> [text addAttribute:@(UIAccessibilityTraitLink) value:@YES forRange:..]
>
> then the text field should expose the links rotor.
>
> You can see this in action in Settings > Privacy > Location services.. There’s a link in a block of text that can be accessed that way
>
>> On Sep 6, 2015, at 12:07 PM, Victor Tsaran <email@hidden> wrote:
>>
>> I assume they can at least try since they are already doing some custom processing on the text field. Let's say they are exposing the clickable area of the text field as an object of sorts.
>> To be honest though, I am very much speculating here without knowing the internal details.
>> If the above is not possible, I guess they could introduce additional accessible elements for VoiceOver users.
>>
>>
>>> On Sep 6, 2015, at 11:23 AM, Marco Zehe <email@hidden> wrote:
>>>
>>> Hi Victor!
>>>
>>> Thanks, will definitely try that IsViewModal approach for 1!
>>>
>>> As for 2: The text is part of editable text, a standard multiline text field. Can traits be applied to certain text snippets in such text fields?
>>>
>>> Marco
>>>
>>>
>>> Von meinem iPad gesendet
>>>
>>>> Am 06.09.2015 um 20:18 schrieb Victor Tsaran <email@hidden>:
>>>>
>>>> Hey Margo!
>>>> For 1, I think, isViewModal applied on a custom popover view should do the trick. For 2, they will can try the clickable text with the link trait. This will expose it as links in the rotor.
>>>>
>>>>
>>>> Sent from a device
>>>>
>>>>
>>>>> On Sep 6, 2015, at 2:37 AM, Marco Zehe <email@hidden> wrote:
>>>>>
>>>>> Hi all!
>>>>>
>>>>> I am currently helping an ISV to make their writing app for iPad more VoiceOver accessible. Aside from the usual suspects (unlabeled buttons en masse), there are two problems I'd like to help them with, which I didn't find obvious solutions to in either the documentation or WWDC videos.
>>>>>
>>>>> 1. The first problem is in custom popovers. These are not exclusively visible, and furthermore, they aren't recognized by VoiceOver as popovers. They simply are views that get inserted into the other view hierarchy and can be swiped to, and swiped out of into surrounding elements. What's the best way to make these accessible?
>>>>>
>>>>> 2. The second problem is in some parts of the text field. There is specially marked text which a sighted non-VoiceOver user can just double-tap and get a said popover with more properties to edit. I've tried to navigate to this text with the VoiceOver rotor commands (this works), but triple-tapping the screen to simulate a non-VoiceOver double-tap does not work. Only a double-tap is recognized, so VoiceOver just again focuses the text field, which already has focus anyway.
>>>>>
>>>>> What are the options here? I suppose there is no way to hook special menu items into the "Edit" rotor selection? Like some edit fields have bold, italic etc. options, and others don't? What could be done to make this accessible so VoiceOver users can either triple-tap correctly, or have some other means of accessing the info behind these special text sections?
>>>>>
>>>>> Thanks for any advice!
>>>>>
>>>>> Again, this all is for iOS.
>>>>>
>>>>> Marco
>>>>>
>>>>> Von meinem iPad gesendet
>>>>> _______________________________________________
>>>>> 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
>
_______________________________________________
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