Re: VOiceOver and 'end of text' announcement
Re: VOiceOver and 'end of text' announcement
- Subject: Re: VOiceOver and 'end of text' announcement
- From: Vincenzo Rubano <email@hidden>
- Date: Fri, 21 Oct 2016 11:52:34 +0200
On 20 oct 2016, at 21:18, Charlie Powell <email@hidden> wrote:
>
> While we're on the subject, and if anyone from Apple is watching/listening, please consider changing the accessibility text APIs for Mac. Dealing with scalar NSRanges can make things incredibly difficult, particularly when it comes to things like this. In my opinion, something akin to the abstract UITextRange that has the notion of text granularity is a far better design. It would also allow an app to more easily share implementation for text controls between Mac and iOS :)
>
And while you are at it, please start offering support for more text attributes (i.e. headings and advanced formatting attributes), make VoiceOver use them efficiently (i.e. allow to navigate a text by headings) and squeeze existing bugs. Also, please fix accessibility of tables in NSTextView! Just to name the first 3 things that came to mind that have been in needing of attention for a long time and none took care of.
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 20 Oct 2016 15:54:36 +0100
> From: Tim Burgess <email@hidden>
> To: Apple <email@hidden>
> Subject: VOiceOver and 'end of text' announcement
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=utf-8
>
> Hi,
>
> I’m working on making an NSView accessible using the text area role. I’ve implemented accessibilityNumberOfCharacters, accessibilityValue, accessibilityStringForRange, accessibilitySelectedText, etc.. However, VoiceOver sometimes announces ‘end of text’ as I arrow down through text, despite the fact that the end of the content has not been reached. This can also happen sometimes at the end of lines. Additionally, logging the ranges being used when VO calls accessibilityStringForRange sometimes shows ranges that supposedly start after the last character of the content, or extend beyond the end of the content.
>
> In order to help debug this, can I ask how VO determines what is the ‘end of text’. I assume that it relies solely on accessibilityNumberOfCharacters, but is this the whole story?
>
> Best wishes.
>
> Tim Burgess
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Accessibility-dev mailing list
> email@hidden
>
> End of Accessibility-dev Digest, Vol 13, Issue 100
> **************************************************
>
> _______________________________________________
> 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