I might agree with this, but I think I have a bad understanding of what flat review is supposed to do.
I had thought that, for example, the key for reading the current
line, in my case number pad five, would read where my cursor is.
The other number pad keys would read in their various directions,
much as with Speakup.
What I've found is that sometimes the keys work as I expected, as
when I read this message, but often they do not. If I try using
the current line key in the original message, it reads "inbox,"
the subject, and two more things that I forget. Using the other
number pad keys does not bring me to the message body. On the
website radio.macinmind.com, where I just tested, flat review
sometimes read what I thought it would and sometimes not, and I
haven't yet figured out when it does which.
I've had this problem for a long time, but I didn't mention it that I remember, so that's on me. It mattered most to me when I wanted to read around where I was without having to move the arrow keys, so that getting out of flat review would bring me right back to where I was. Anyway, since I recall no complaints of this sort during the time I've been on this list, I thought it was time now to ask what I'm getting wrong. Then, maybe I can think better about what people are discussing here.
Thanks for any information or perspectives.
Al
Hi,
There are definitely times when reviewing the screen is necessary. I therefore propose that the user can switch between reviewing the current object, and reviewing the screen. My suggestion is that the user can toggle between these two review modes with the key currently used for entering flat review, as flat review is automatically entered when a review key is pressed.
Regards,
Rynhardt
On Sun, 13 Jun 2021, 15:39 Kyle via orca-list, <orca-list gnome org> wrote:
When I'm trying to review the screen using flat review, most of the time
it is because I need to find a certain spot and simulate a mouse click
or I need to spell a word where my caret is, usually when browsing, but
also when I find a button, an element in a drop-down box or another
similar item that I need to be able to spell. I tend to care more about
what is on the screen in the current window at this point than what is
in the current object. I rather like the idea of "current" keys not
using flat review unless flat review is toggled on either by using flat
review navigation or by explicitly toggling flat review on. But a whole
new layer of complexity that is object navigation must be available only
to users who know what they are doing and explicitly want this behavior.
The last time I needed NVDA for anything, I found it fairly easy to use
overall, but there were two things about it that made me want to throw
my computer out the window. Those two things were the browsing virtual
buffer and the rather convoluted hierarchical object navigation that is
nothing at all like what someone looking at the screen would see, and
caused me much pain just trying to get around my screen in places where
tab focus and other keyboard focus things didn't work as well as they
could have. Is flat review perfect? by no means. But the behavior and
performance of flat review must be improved wherever possible. It must
not be shoved aside for something as esoteric to the end user as object
navigation.
~Kyle
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
_______________________________________________ orca-list mailing list orca-list gnome org https://mail.gnome.org/mailman/listinfo/orca-list Orca wiki: https://wiki.gnome.org/Projects/Orca Orca documentation: https://help.gnome.org/users/orca/stable/ GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html