I have my speech set to read words as opposed to characters. That works fine for me with braille translation. However, when set to six dot braille, it reads by characters as well as words no matter what the setting. Sounds like the whole system is buggy to me, not to mention how slow and sluggish Grade 2 braille has been since the inception of braille on the iPhone.
VoiceOver Not Echoing Characters When Using Contracted Braille in Braille Screen Input Mode
When entering text using Braille Screen Input and input mode is set to Contracted, VoiceOver does not echo the characters typed—even if typing feedback is set to echo characters. This creates a situation in which the user would have no way of knowing what dots were entered until the word has been translated, thereby making Contracted braille input less efficient because there is a greater possibility for mistakes to be made if the user has no feedback as to what is being typed.
Bug First Encountered
Device(s) bug has been encountered on
How often the bug occurs
Disable Contracted input by doing a three-finger flick to the right or by going to Settings> General> Accessibility> VoiceOver> Braille> Braille Screen Input and selecting 6-dot Braille.
When I use braille with my iPhone 5s on iOS 8.3, I am experiencing that when I use contracted braille, instead of saying The last letter, it says the dots of the last character. When I am trying to type into this form using braille, I'm using uncontracted braille, and it's saying the last character, rather than the word, when I type a space.
I think this is a feature, if a poor one, rather than a bug. Because contracted braille cells can often be multiple characters depending on what comes after them. For instance, say I type dots 2, 3, 6. Should VoiceOver echo ‘his’ or ‘open quote’? Of course, it depends if the next character I type is a space or not. So to get around this ambiguity, VoiceOver does not echo characters in contracted mode. When deleting, however, you'll notice VoiceOver identifies the character by giving the dot numbers, rather than the character name. Perhaps it could do that when typing as well.
When typing # or @ in some apps, like Twitter, any Twitter client, Facebook, or Sharing to these services from other apps will cause Braille Screen Input to crash. This has been noticed and reported in every version of iOS 10 public betas.