-----Original Message-----
From: main@jfw.groups.io <main@jfw.groups.io> On Behalf Of Bill White
Sent: Saturday, August 6, 2022 12:52 PM
To: main@jfw.groups.io
Subject: Re: preforming a right click
I understood what he was trying to say, too, but Brian is the guy who is always calling someone out. I just wanted to point out that Brian makes human mistakes, too, even though it is usually he that is calling someone else out for their mistakes.
Bill White
billwhite92701@...
-----Original Message-----
From: main@jfw.groups.io [mailto:main@jfw.groups.io] On Behalf Of Gene Warner
Sent: Saturday, August 6, 2022 10:48 AM
To: main@jfw.groups.io
Subject: Re: preforming a right click
I noticed that mistake too, but didn't want to call him out for it because I understood what he was saying.
Gene...
On 8/6/2022 1:44 PM, Bill White wrote:
Brian wrote:
Believe me, it took me forever to wrap my head around the fact that
screen readers really are not "reading the screen" in any meaningful
sense of that phrase. They load what is shown on the screen into a
virtual cursor and everything is happening on the material loaded there.
The screen is not loaded into a Virtual Cursor. It is loaded into a
Virtual Buffer, which is completely different from a Cursor. A cursor
is an indicator. A buffer is a data storage area.
Bill White
billwhite92701@... <mailto:billwhite92701@...>
*From:*main@jfw.groups.io [mailto:main@jfw.groups.io] *On Behalf Of
*Brian Vogel
*Sent:* Saturday, August 6, 2022 10:28 AM
*To:* main@jfw.groups.io
*Subject:* Re: preforming a right click
On Sat, Aug 6, 2022 at 01:21 PM, Gene Warner wrote:
It would have really been nice if they could have done without all
these different cursors
-
There really are only two that are "active" at any given time, the
virtual cursor and the PC cursor.
And the virtual cursor is either going to be the JAWS Cursor, if
you're doing pretty much everything via keyboard, or the Touch Cursor.
Those are both "situational overlays" for the virtual cursor and only
the virtual cursor.
Believe me, it took me forever to wrap my head around the fact that
screen readers really are not "reading the screen" in any meaningful
sense of that phrase. They load what is shown on the screen into a
virtual cursor and everything is happening on the material loaded
there. And for someone who can see, the virtual cursor can get very
confusing if a web page is coded sloppily such that the visual
presentation is beautifully organized but how that loads into the
virtual cursor is not. Good HTML coding makes visual presentation and
virtual cursor ordering largely congruent. But crappy HTML coding can
have the ordering of what gets loaded into the virtual cursor not have
anything at all to do with how visual presentation lays things out.
When a screen reader user starts at the top of a page, and a few short
navigation commands later is buried in the middle or at the end, not
following the visual flow, it's a nightmare (and not just for the
sighted assistant, because that visual flow is important to how the
data is ordered for someone who can see it, so it should be ordered
similarly for someone who can't, but it isn't).
--
Brian *-*Windows 10, 64-Bit, Version 21H2, Build 19044
**Here is a test to find out whether your mission in life is complete.
If you’re alive, it isn’t.***
* ~ Lauren Bacall