I second this opinion big time. Most often, the author or company has no idea that the PDF is not accessible with screen readers, and the fix can be very easy on their part. Also, it is also likely that they are legally required to make all their PDFs accessible. The first part is notifying them, then they can do some research, fix it, and send it back to you. Best regards, Mark Mark Stimson, Ph.D. Accessibility Technology Specialist www.DocumentAccessibility.com www.AccessIngenuity.com <http://www.accessingenuity.com/> From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Adrian Spratt Sent: Saturday, July 18, 2009 3:39 AM To: jfw@xxxxxxxxxxxxx Subject: Re: JAWS Reading PDF Documents I don't know if this explanation applies here, but for JAWS to read a PDF document in the correct sequence, the file's creator must properly tag it. It isn't just a JAWS issue. Tagging also plays a role in how well OCR scans a PDF file for printing. I'm no expert in this area, but when all else fails, it might be worth contacting the file's creator to ask them to look into tagging. I did that recently with a large organization, and they both understood and agreed to fix the problem in future PDF files. ----- Original Message ----- From: Dave Carlson <mailto:dgcarlson@xxxxxxxxxxxxx> Sent: Saturday, July 18, 2009 2:21 AM Rick, Change the reading order in the accessibility menu. Dave ----- Original Message ----- From: Rick Miller <mailto:mil9@xxxxxxxxxxxxx> Sent: Friday, July 17, 2009 22:44 Whenever I try to read an article in PDF format, when I use the Say All command I find that columns are not separated and JAWS, rather than reading by column, reads the text straight through, which makes the reading of the article confusing. Is there a way you can get JAWS to read just individual columns when reading a document in PDF format? Rick Miller __________ NOD32 4257 (20090718) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com