Answered
I have two problems where although the table is correctly tagged in the tag tree, when listening to it it is reading incorrectly.
1. Reading decimal place that does not exist
e.g.
January 2009
5.60
6.20
6.60
Reading as five dot six hundred, six dot two handred
2. Reading across the columns.
e.g.
Administration 1,2,3
413
420
Reading as Adminstration one comma two comma three four hundred and thirteen thousand four hundred and twenty.
re: #1 - "five dot six hundred" vice "five dot six zero", yes?
I'm unable to duplicate this. created a 3 column, 1 header row, 2 data row table.
Data row #1: 5.60; 6.20; 6.60
Read Aloud speaks these as -
"five point six zero", "six point two zero", and "six point six zero"
Data row #2: 5.600; 6.200; 6.600
Read Aloud speaks these as -
"five point six zero zero", "six point two zero zero", "six point six zero zero"
re: #2 - Yes, Read Aloud does a "run-on read"; it does not effectively cope with word breaks.
Word breaks can, at times, be awkward; however my understanding is that AT applications (particularly the more contemporary releases) handle word breaks more effectively.
Think of Read Aloud as a litmus paper test. It gives you a general sense of things but is not a titration that identifies a specific value. An AT application would be needed for more exact determinations of the caliber of the tagged output PDF.
Don't forget to use Save As to the accessible text file. It can provide a better sense of where the word breaks are.
As can be seen below, each table cell's content is disrete which indicates a clean word break that can be recognized and utilized by an AT application. Read Aloud's run-on read does not alter this. Read Aloud is simply less sophisticated.
January 2009
February 2009
March 2009
5.60
6.20
6.60
5.600
6.200
6.600
Be well...