| 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
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).
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
|