JAWS and Tables on Web Pages

  • From: "Tom Lange" <trlange@xxxxxxxxxxx>
  • To: <jfw@xxxxxxxxxxxxx>
  • Date: Tue, 27 Sep 2005 06:17:49 -0700

Hi,
Here's one for you all to have some fun with, especially you guys who like
to bet the horses.
A friend of mine is a JAWS user who occasionally likes to go to the
racetrack and bet on the races.  Rather than read the printed racing form,
he likes to look at it online at www.drf.com.  With the JAWS table reading
commands, this actually works pretty well.  But here's the rub.  He wants to
select the tables for the day's races, put them into a Microsoft Word
document, crank up the font size and print them for one of his pals. He also
wants to put a page break between each of the tables so that they all appear
on separate pages.

I tried playing with this yesterday and noticed a couple of things. When I
selected a table or two and put them into my document, everything was
arranged vertically; the table format was completely destroyed.  To get
around this, I told IE to let me edit the page in MS Word, then I saved the
result as a Word doc.  Then the problem that I ran into was that because of
the table arrangement, I couldn't insert page breaks in the proper places.

So, how can I use JAWS to select any part or all of a table, copy and paste
it into a document and retain the formatting? Or, in the case of the nested
table arrangement at drf.com, how can I insert page breaks between the
individual tables?

Just a little thing for you all to fiddle with in your spare time; it's not
an urgent matter by any means, but I am curious about this.
Cheers!
Tom


--
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to 
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw

If you have any concerns about the list, post received from the list, or the 
way the list is being run, do not post them to the list. Rather contact the 
list owner at jfw-admins@xxxxxxxxxxxxxx

Other related posts: