Re: [orca-list] The SayAll user experience

["D. A. H." <dhunt freedommail co>]

These are great questions; I'll put my answers inline, as others have done.

On 11/11/2013 10:19 PM, Joanmarie Diggs wrote:
> 1. The primary purpose of SayAll is:
>     A. To present the exact same thing I would hear if I were manually
>        arrowing through the document. I just hate those arrow keys.
>     B. To present document text and only the document text. If I wanted
>        to hear context like heading levels and the number of items in a
>        list, I'd arrow through the document or use structural navigation.
>        Plus I really hate the pauses that result each time the voice
>        changes to present all caps, links, and stuff that is not on
>        screen.
>     C. Other (please explain in your answer)

Say-all is for reading large amounts of text, without having to press 
keys for each element, with the option of hearing structure, or not, 
depending on use case.  User should control whether and how structure is 
presented; For instance, when proofreading, structure must be indicated 
by the least-disruptive means, such as voice parameter changes or by the 
insertion of so-called "ear-cons" in the stream.  As I understand the 
way say-all now works, voice parameter changes are supposed to be 
possible but the result seems only to be long pauses when cursor is over 
a structural element, like a link.  Moreover, when user interrupts 
speech, the cursor should end up where speech was stopped, not be parked 
at the point where say-all started, as often happens now.
>     How strongly do you feel about your answer to question 1?
Strongly, but the current state of things is not a deal-breaker; I'm a 
long-time, exclusive Orca user.


> 2. The expected behavior of my braille display when using SayAll is:
>     A. To keep up at all times with the speech. I can read really fast.
>     B. To maintain a totally independent copy of the content being spoken
>        so I can scroll through the braille and read one part of the
>        document while another part is being spoken.
>     C. It's SayAll; not BrailleAll. As long as you update my display
>        when SayAll is interrupted or completed, I'm happy.

If I were a braille user, this is how I'd want say-all to handle my display.

>     D. Other (please explain inyour answer)
>
>     How strongly do you feel about your answer to question 2?
On a scale of 1-5,  maybe 3, subject to my not having a display.
>     How often do you use a refreshable braille display with Orca?

I don't have one.

> 3. The thing I like most about Orca's current SayAll behavior is.
>     (fill in the blank)
I'm glad it's here, and works reasonably well; say-all is something any 
screen review should have.  Especially when reading for pleasure, it's 
nice to start the reader, and take hands off keyboard while it's going. 
 Orca needs to get better at stopping the cursor as near as possible to 
where speech stops, as mentioned earlier and by others.
>     How strongly do you feel about your answer to question 3?
Very!

> 4. The thing I like least about Orca's current SayAll behavior is.
>     (fill in the blank)
Pauses on structural elements, inability to change presentation of said 
structure, trouble pausing and resuming speech.
>     How strongly do you feel about your answer to question 4?
Very strongly!