Hi!
Try:
http://www.w3schools.com/jsref/dom_obj_document.asp
Now if you do download my Breaking News and insert this link in there
you can expand and save the link for other pages to get the DOM reference on
everything.
Now, you can get events such as what button you are on, or any
tag/element of a page if you so desire to make your own app to do so.
My Breaking News downloads the page and all of it's elements and knowing
how HTML is structured you can strip all the elements apart and use them.
The only ones that don't show up doing this are those that are made when the
page is loaded and all events that fire to make more page elements based on
events...
So, to do anything at that point you have to be at the web site to run
those nasty scripts.
In my Breaking News I get the default web site and any link is based on
that reference unless the link has a full path, then I don't touch it.
Yes, my app has some flaws, but there mostly dynamic flaws. I take all
the tags for display and make a name if needed or at least post the text on
one line and the link it refers to on the next line. But there are times
when formatting can reverse that order, so I also exposed the link page it
points to by displaying the last page in the name for the link to give a
better understanding where the link is pointing; which you can modify that
display.
I have not touched it since last fall but one of these days will look at
some dynamic stuff for it.
But, your lists are displayed in my Breaking News app, but do not place
a list label on it, but could.
All I do is list them vertically as the appear on the web page. I did
not split up table headings and such, I concentrated on links and link
labels that exist in tables and lists.
Even div commands and anything that is related to text and links are
displayed vertically, unless you want to place them in a list view instead
of a text page. Then you get the links in alphabetical order or as is, an
option you set in the list view mode...
So, I will work on dynamic pages but avoiding it so you don't have to
load a page and deal with pop-ups and spy scripts...
I hope you have downloaded Breaking News.
Bruce
Sent: Friday, March 18, 2016 5:58 PM
Subject: Re: Learning How To Dig Into A Web Page To Make It Accessible
That's it, Chip. Screen-readers all have essentially two modes of
operation: Windows and standard programs or anything that uses a browser
or the IE engine, e.g. CHM files. So scripting one or the other is like
tackling two different beasts, especially if you need to do anything
more than skim the contextual surface.
Tom
On 3/18/2016 4:20 PM, Chip Orange via Scripting wrote:
> 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/tom.kingston%40charter.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
>
_______________________________________________
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
