Apple

On May 18, 2016, at 12:50 PM, Andres Gonzalez <email@hidden> wrote:

Hello Chris: how is accessibilityCustomElements different from accessibilityElements? They both seem to be called by VO. Thanks.

—Andres.

On May 16, 2016, at 4:02 AM, Chris Fleizach <email@hidden> wrote:

I think you could do

@interface MyTextView : UITextView

@end

@implementation MyTextView

- (BOOL)isAccessibilityElement

{

return NO;

}

- (UIAccessibilityTraits)accessibilityTraits

{

return UIAccessibilityTraitNone;

}

- (NSArray *)accessibilityCustomElements

{

// Create fake UIAccessibilityElements to represent each paragraph

return _fakeElements

}

@end

And you should get the behavior you want

On May 14, 2016, at 3:07 AM, Vincenzo Rubano <email@hidden> wrote:

Hi Boris,

thanks for your reply. The links are already accessible through the rotor since I’m populating the text view from an NSAttributed string.

While accessing links through the rotor wouldn’t be such a deal, I'm mostly concerned with paragraphs. Suppose I am reading a text with 20 paragraphs and I am at paragraph number 18. Then a phone call arrives and VoiceOver stops reading. After my phone call ends I’d like to start reading again from paragraph 18, not from the beginning; and currently there’s no way to achieve this goal by using VoiceOver within a non editable text view. Here’s the reason why I want to expose everything as separate objects.

In addition to this, if the user wants to read everything at once he can always do that by scrolling down with two fingers, having the advantage of understanding when a paragraph ends and a new one starts through VoiceOver sounds.

Vincenzo Rubano

NVApple Team

https://www.nvapple.it/about-us

Il giorno 14 mag 2016, alle ore 11:15, Boris Dušek <email@hidden> ha scritto:

Hi Vincenco,

for links, you can try if this tip is applicable and feasible in your usecase: http://lists.apple.com/archives/accessibility-dev/2015/Sep/msg00009.html . It would not add links as separate elements in the normal swiping-left and right VoiceOver order, but they would become accessible through the rotor “Links” item (which I consider a less obtrusive and more efficient than presenting links as separate objects where VoiceOver always reads only one segment of text, be it a link or text between links / text beginning/end; though such less efficient experience is better for beginners who don’t know how to use rotor - everything has its trade-offs).

Kind regards,

—
Boris Dušek

A11Y LTD.

https://accessibility.expert

On May 14, 2016, at 11:01 AM, Vincenzo Rubano <email@hidden> wrote:

Hi all,

in my application I have a UITextView that displays some text. The text view is not editable. The displayed text contains multiple paragraphs and occasionally a few links here and there.

Is there a way to expose the text view content to VoiceOver as separate objects just like the WKWebView does?

I need to implement this to offer a better user experience to VoiceOver users and I’d prefer not to use a WKWebView since I’d have to mess up with the layout in code, something I don’t like at all.

Cheers

Vincenzo Rubano.

NVApple Team

https://www.nvapple.it/about-us

_______________________________________________
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