Re: [orca-list] Orca should report locations of web elements

[Andy Borka <sonfire11 gmail com>]

Hi Joanie,


From the small amount of testing I have done so far, this feature is a 
dream come true! The nice bit is that Orca now presents the 
size/location of any element, even if it isn't a web element. I will do 
some testing for the remainder of this week with my own test website and 
program. As a side note, Impress is now more accessible than yesterday 
because of this new feature. This is a long time coming... Thanks for 
the hard work.


On 1/7/19 3:50 PM, Joanmarie Diggs wrote:
> Hey Andy.
>
> Sorry for the delay. Holidays followed by catching up on bigger issues.
>
> I committed a change to master to present the size and position
> information. If you are using flat review, it will provide it for the
> current flat review item; otherwise it will present it for the
> currently-focused item.
>
> Note that contrary to your recommendation, I did not split this up into
> two separate commands. There's just not that much information to be
> presented. Especially not in brief *message* verbosity level (which is
> not the same as the general speech verbosity level). Since the size
> numbers are more likely to be smaller (at least in some use cases), I
> put them first so that if what you care about is location, at least
> you'll hear it without too much delay.
>
> I hope that what I have committed addresses your needs. Please test and
> let me know.
>
> Thanks!
> --joanie
>
> On 11/2/18 6:10 PM, sonfire11 gmail com wrote:
> > Hi,
> >
> > To make things simple, Orca can report like the following:
> > For verbose verbosity level,
> > Location: 200 from left, 300 from top
> > Size: 400 wide, 700 tall.
> >
> > For brief verbosity level,
> > Location: 300, 200
> > Size: 400, 700
> >
> > I might recommend breaking the reporting of element location and element size into different keyboard shortcuts. If I 
> > am trying to check the alignment/position of an element, I don't always want to hear its size in the event I already 
> > know it. The same goes for location. If I am experimenting with the size of an element, I may not need to hear its 
> > location every time I change the width or height. To give input on the second part of the question, I don't normally 
> > see css provide locations of elements outside the range of the current viewport. For example, I never see width: 7000; 
> > height: 5000, or top: 10000, left: 20000. In the event the element does scroll off the page, then everything is 
> > relative to the viewport's content margins. For example, If a link "about" is found at the bottom of a page, 
> > but the user had to scroll to find it, then the top/left Orca reports is according to the top/left corner of the 
> > viewport window. In general, it is the user's problem to figure out if content ran off the viewport area. Given this, 
> > the user should have some way of seeing what content is in the viewable area of the browser window. I know moving the 
> > system cursor scrolls the page. However, I don't know if the flat review shortcuts scroll page content, or report what 
> > is on the visible screen. Let me know if you need to work through other issues on this.
> > -----Original Message-----
> > From: Joanmarie Diggs <jdiggs igalia com>
> > Sent: Friday, November 2, 2018 11:11 AM
> > To: Andy Borka <sonfire11 gmail com>
> > Cc: orca-list <orca-list gnome org>
> > Subject: Re: [orca-list] Orca should report locations of web elements
> >
> > Hey Andy.
> >
> > I started working on this, but have some questions. First one is what should Orca say? Would "x pixels from 
> > left edge. y pixels from top edge.
> > Width: 123. Height: 456" work? Or did you have something else in mind?
> >
> > Another issue that occurs to me is that if you have scrolled the page content, you might get a value other 
> > than what you expect. In other words, if you press Page Down, on a long page and then ask for the 
> > coordinates, you're going to get a different value than if you pressed
> > Ctrl+Home on that same page and then asked for the coordinates. Is it
> > the end user's responsibility to know how the page is scrolled and take that into account when getting the 
> > numbers from Orca?
> >
> > Thanks!
> > --joanie
> >
> > On 10/16/18 3:22 PM, Andy Borka via orca-list wrote:
> > > Hi,
> > >
> > >
> > > It is critical that a web developer know where he or she places html
> > > elements on a page. Therefore, I am requesting a feature that can tell
> > > me the pixel coordinates of a particular element such as text, a link,
> > > headings, paragraphs, lists/list items, and so on. It would also be
> > > nice if Orca can tell me the physical size of each element in pixels.
> > > What do you think?
> > >
> > > JAWS/NVDA already does this, so I know it is possible.
> > >
> > >
> > > _______________________________________________
> > > 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
> > > Log bugs and feature requests at http://bugzilla.gnome.org