I am converting a PDF file to a word file with OmniPage 16 Professional. Enbedded into this file are several tables. A few of the tables are gray shaded and perform well with JAWS, a popular screen reader for the blind. However there are several tablesin which the beginning and end of the table are shaded pink. These particular tables are not accessible by the screen reader. My assumption is that the pink area means it is a text box but when I use format/text box styles/text box:convert to frame/control Q, I lose all the data and the pink shaded remains devoid of text. What are my options here to provide accessiblilty? Any ideas of things I could try? This text is for a young man's college course and we are desperate.
Hello DBD DBDAZE wrote: > I am converting a PDF file to a word file with OmniPage 16 Professional. > Enbedded into this file are several tables. A few of the tables are gray > shaded and perform well with JAWS, a popular screen reader for the blind. > However there are several tablesin which the beginning and end of the table > are shaded pink. These particular tables are not accessible by the screen > reader. My assumption is that the pink area means it is a text box but when > I use format/text box styles/text box:convert to frame/control Q, I lose all > the data and the pink shaded remains devoid of text. What are my options > here to provide accessiblilty? Any ideas of things I could try? This text > is for a young man's college course and we are desperate. I'm not sure I understand your workflow: creating accessible files (DOC *or* PDF) is an art in itself -- why start with an OCR-ed sample to begin with? 0.2¢ Robert -- /"\ ASCII Ribbon Campaign | MSFT | \ / | MVP | Scientific Reports X Against HTML | for | with Word? / \ in e-mail & news | Word | http://www.masteringword.eu/
