Hi Rick,
The problem with Windoweyes is the events triggered and to trigger and
you have to make an Active X Com of the object. Getting the windows object,
and having the latest version of the browser and things can be done, but
Firefox does not allow Active X, Com objects...
So, NVDA, that free software reads everything for they approached it
differently but you can set things in your WE environment by turning on what
you want to read on a browse line and such. It is a work in progress at the
moment. Rod and I are looking into it.
Now my Breaking News app, I know HTML and when you download the web page
by
using the hotkeys, Ctrl-down-arrow, I look at the web page as the default
URL.
Knowing the default URL and any links inside the page that does not
start with the default, it is assumed that you must add at the beginning
what is missing and that works 99% of the time.
What does not work are inside references at the moment, which use link
names and you see the # sign that goes no where but inside the page itself.
I also use 3 different functions to strip tags off depending on what
type of tag it is and I do it sequentially down the page.
What I have not done is block off in columns what is done in tables with
columns, for I assume left to right and top to bottom.
There are some tags like time and date, they have to be digested using
the info inside to make them readable, and Copyright tags and such which
also require a format and all those types of HTML tags I do the display
myself of what it is asking for...and provided inside the tag.
Now, as some I am sure have found out, some links have there labels
after them instead of before. That is happening when they want fancy stuff
there and the reason why I post inside the Link=# the actual file it is
pointing to so you know which phrase it is pointing to. I just do a reverse
search and display from the last / in the link...something simple to do.
The Link=# is a way of being able to use a hotkey on it, for it says
link= then assumes a number is after it, which is meaningless for the
viewer, because it is the dictionary key and makes sure what is stored in
the dictionary is unique and the label after it is also meaningless for it
only displays what the page is pointing to when it arrives there; the
dictionary key/# has the full path inside of it.
Now when inside the editbox, or text box showing the page I make it read
only so you can use the enter/return key for going directly to the page and
the standard hotkeys for all of my app: Ctrl-down-arrow for downloading the
web/link into the text box, or Alt-down-arrow to display the page as a list
of links. Now, I have allowed you to turn on and off the read only so you
can actually enter or paste in a path of your own, then turn off edit and
use the hotkeys on it.
IF the display is link= or src= href= and it will be used as a link and
the hotkeys will work for all 3 formats, but the link= has to have a
dictionary entry for it...
When displaying them as a list you can set it for a simple or
Detailed/expanded view list...
So, my program, app, Breaking News, just allows you to download and read
the page in a text box, or display the page as a list. You can even expand
the link=# to also display the entire path, thus allowing you to save the
entire text box as a file to have full use of the page saved using the
links. If saving as an email file then they will be usable links.
I do not at the moment do any Java Script functions but could, for I
strip out all scripts so they don't get displayed, nor run. So, in the
future that can be easily done, as long as, it has the proper link
reference, for nothing works without the proper base link for the page since
all, or most links, reference sub pages of the top level web page.
As I have said in the past, I will be making this app more useful,
allowing controls and such work, reference the script it points to, based on
the name inside of it's tag...
But, your first posting, NVDA does do it all, so all issues mentioned
are related to flaws, or just opening up settings, to read other stuff. As I
had mentioned to Rod, if everything was turned on it could get very noisy
reading a web page. So, the settings are there for someone to write the app
to use them; which I think was the GW Micro original intent, giving basic
settings and you to upgrade yourself...
So, will now spend my free time upgrading my app and help Rod, for we
are working together on this...
Happy Programming,
Bruce
Sent: Monday, March 21, 2016 5:40 AM
Subject: RE: Learning How To Dig Into A Web Page To Make It Accessible
Hi Chip:
I am not sure but I don’t think a vbScript using this model will allow for
interaction with a web page.
I am guessing Bruce just fires up a process to execute a url or somehow
navigates to it and executes the link, I don’t know how or even if that can
be done though I have used processes to do allot of things like that
including fire up links but never interacted directly with a web page other
than using a browser control in a vb.net project I once created.
I think I remember there being methods in the UIA model that allow for
interacting with a web page if the UIA methods are activated by the
programmer or the browser - I forget how all that works.
But my guess is that you will need a new set of tools outside vbScript if
you want to really work with web pages and browsers for more than just
reading the html and speaking things like being able to click a link or
button or a listitem and all that jazz to make pages accessible.
Perhaps Aaron will chime in with some tool suggestions if you folks are
serious about setting WindowEyes up for scripting and making web pages
accessible and not just reading the dom elements.
Rick USA
-----Original Message-----
From: Scripting
[mailto:scripting-bounces+ofbgmail=mi.rr....@lists.window-eyes.com] On
Behalf Of Chip Orange via Scripting
Sent: Friday, March 18, 2016 4:21 PM
To: 'Joseph LaFauci' <joel...@iquest.net>; 'Window-Eyes Scripting List'
<scripting@lists.window-eyes.com>
Subject: RE: Learning How To Dig Into A Web Page To Make It Accessible
Hi Joe,
Are you familiar with HTML?
The only example script which I've ever seen, which was written to improve
the accessibility of a web page, was written by an author who was familiar
with xml/html.
It used the .NativeObjectModel property to get to the IE document object
model so that it could examine the html elements of a page, once it had
determined that the page in question was the one for which further info was
being saught. It then worked its way down through frames and tables and TD
elements to find the one containing the information being desired, it
extracted the information, and spoke it.
This was designed to give the user some needed information very quickly for
an employment situation. I've not seen an example of any scripting which
tried to manipulate the page to change focus, activate controls, etc.
If you're familiar enough with the IE DOM perhaps you know if this can be
done through it (I would think so), but I don't know enough to be of much
help. I have only a slight reading ability with xml and html, and as I
understand things, you'd have to be able to accomplish whatever you need via
the IE DOM; I don't think the WE scripting object gives you much in the way
of page contents or manipulation abilities.
Sorry I can't be of more help, but if you're expertese does lie in the
xml/html arina, then perhaps you can move forward.
Good luck,
Chip
Chip Orange
Florida Public Service Commission
Computer Systems Analyst
850-413-6314
-----Original Message-----
From: Scripting
[mailto:scripting-bounces+corange=psc.state.fl...@lists.window-eyes.com] On
Behalf Of Joseph LaFauci via Scripting
Sent: Tuesday, March 15, 2016 9:53 PM
To: Window-Eyes Scripting
Subject: Learning How To Dig Into A Web Page To Make It Accessible
Greetings everyone!
Can anyone suggest a place to start in learning about the browse objects and
other necessary info in order to be able to figure out how to make a
stubborn web page more accessible?
I have a particular one which has three (sort of) menu drop-downs but they
show up as lists and are not clickable in any way. I am not even able to
route the mouse pointer to them. Actually, I have succeeded in routing to
the items once or twice but it is certainly not consistent.
If a sighted person clicks one of the list items for me, the menu expands
and the resulting menu items are clickable.
My goal is to accurately get the mouse to the desired list item and click it
so the menus can be accessed.
I am working with the web page designers to make it accessible, but in the
interim (how ever long that may be), I thought I’d try to tackle it with
scripting. So far that is quite a challenge for me as I haven’t done much
with web pages in scripts.
One of these days I will have to take a script class for Window-Eyes.
Meanwhile, I wish we had a really good scripting book.
Does anyone have any ideas?
Thanks.
Joe
Joseph LaFauci
Web: http://www.joeleah.com
Blog: http://www.understandingscripture.com
Feed: http://feeds.feedburner.com/wantedinhellnamedinheaven
Twitter: http://www.twitter.com/ka9opl
Skype: ka9opl
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com/attachments/20160315/d576f78c/attachment.htm>
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/corange%40psc.state.fl.us.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/ofbgmail%40mi.rr.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/lab4me%40fltg.net.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
