RE: VOiceOver and 'end of text' announcement
RE: VOiceOver and 'end of text' announcement
- Subject: RE: VOiceOver and 'end of text' announcement
- From: Charlie Powell <email@hidden>
- Date: Thu, 20 Oct 2016 19:18:02 +0000
- Thread-topic: VOiceOver and 'end of text' announcement
Perhaps you've already done this, but also ensure that you've implemented any API related to line numbers, specifically:
1. accessibilityInsertionPointLineNumber
2. accessibilityLineForIndex
3. accessibilityRangeForLine
In my experience, you can get navigation to work for characters and words without this, but when navigating by line these APIs seem critical. While I can't say for certain it explains the behavior you're seeing, I know we've seen similar issues that are a result of bugs in our implementation of these methods.
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 :)
----------------------------------------------------------------------
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