A user in the mailing list had a feature request and another user expanded upon it as follows:

This user is looking for a feature that existed in the old Chromevox which allowed a user to set the behavior of the arrow keys in respect to the cursor. Visually, the cursor lies in between letters. A user can tell where he or she is and what action the command they press will perform by looking to see where the cursor is. On Mac operating system and in Chromevox Classic with the box checked, screen readers behave differently when announcing which letters the cursor is in between. The screen reader would announce letters, and the arrow keys would announce the position of the cursor depending on which direction the user moved. The easiest thing to do would be to provide an example I think: 
1. Create a blank line or document and write the word dog. 
2. Navigate to the beginning of the line. 
3. Press right arrow. Notice that the first letter announced after pressing right arrow is dog. Chromevox is announcing the character ahead of the cursor. 
4. Press left arrow to move backward, and notice that the letter d is announced. Again, Chromevox reads what is ahead of the cursor. 

What is proposed, what the behavior in Mac OS is, and what the option in Chromevox Classic used to be goes something like this: 
1. From the beginning of the line, press right arrow. Observe that the first letter is announced, the letter D. Chromevox is announcing the letter behind the cursor, but this depends on which way the user is navigating. 
2. Press right arrow again, and notice that the letter o is announced. Pressing backspace would erase the letter o, Chromevox is announcing the character behind the cursor. 
3. Pressing left arrow to move backwards announces the same letter again. In this case, the letter o. However, because I pressed left arrow, the position of the cursor relative to what is uttered by the screen reader changes. Now, the character uttered is ahead of, to the right of the cursor. As I arrow left and right, the screen reader would announce the same exact letter, however the position of the cursor would change. 

Now that I have explained this, I have to say that most users are very much used to the way that Windows and Linux handle cursor movement. As a technology trainer, I find that the way the cursor works on the Mac is very difficult to teach to clients who don’t grasp concepts like this easily. I would be willing to bet that my explanation on what this feature is probably is vague and unclear, and may be difficult to understand for some. I do not think this is a feature worth adding, and I don’t think that Chromevox should go down the road of adding features just to add features just because other screen readers work slightly differently. Just my personal opinion. 

Just as an aside, Google Docs also works with the cursor mode described that is used on the Mac with Braille mode disabled. The only reason to add this feature that I could see would be to not make it confusing for users that get used to Google Docs without Braille support, although Google recommends the use of Braille support even without a display present, so this may be a non-issue.