Re: Creating Accessibility Elements for Links in UITextView
Re: Creating Accessibility Elements for Links in UITextView
- Subject: Re: Creating Accessibility Elements for Links in UITextView
- From: Kenny Carruthers <email@hidden>
- Date: Tue, 24 Nov 2015 19:22:21 +0700
Thanks for the follow-up Boris.
Now my question is whether VoiceOver should be recognizing links within a UILabel or do I have to use a UITextiView? I have an NSAttributedString that, from what I can tell, has an NSLinkAttributeName correctly set. When I set the attributedText text property of a UILabel, the UILabel is automatically drawing the link part in blue and underlines, thus I think it's safe to assume that the attribute is properly set.
However, VoiceOver does not recognize the link and the rotor control does not offer a "Links" option when the UILabel is highlighted. Unlike UITextView, which has specific support for link detection, UILabel doesn't appear to have any. I can manually add touch support myself, but I'm curious if I have to do anything to get VoiceOver to recognize them.
(I do see that it works properly in Settings - General - Siri and in iMessage, but I can't tell if those apps are using standard UILabel's or some other control.)
Thank you,
Kenny
> On Nov 24, 2015, at 7:12 PM, Boris Dusek <email@hidden> wrote:
>
> Hello Kenny,
>
>>> You can see an example in setting > general > Siri
>
> also another example is the Messages app: if you get a text (or iMessage) containing links in their text (e.g. phone numbers and URIs (webpage and email addresses) automatically recognized by the Messages app), you can then work with the links too in the fashion you described below:
>
>> Very interesting. I wasn't aware of the rotor control. Are there guidelines for how best to allow VoiceOver users to interact with "inline" links? Is the expected experience once where the label itself is the initial VoiceOver element and, when read back, links are read as "link". If the user wants to access the link, then they have to use the rotor and switch to "Links" mode?
>
> yes, that’s the way one would use such an element with links inside. You get the whole label read as a single element as usual, learning about links (by the virtue of them being announced as “link”), which you would then, if needed, access explicitly “on-demand” using the “Links” rotor (usually for the purposes of activation).
>
> Best regards,
> Boris
>
> —
> Boris Dušek
> A11Y LTD.
> http://accessibility.expert
_______________________________________________
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