I can't get correct behavior either. I have read the PDF whitepaper, and I tagged my styles in InDesign CC 2014 before exporting, then checked read order in Acrobat. It will read 1 line when I click on the line. but it refuses to read some lines, and other lines it stops before the end.
WTF, Adobe? This is a simple text document I have. Do you guys read this site?
I have had the same issue since upgrading my os to Mavericks, have since upgraded to Yosemite and it still doesn't work. I did have one file that it will read the first page but that is all. There is no reason for it, my files all read fine until I upgraded the OS.
Anyone out there have and answer? I have read lots of people who have the same problem!
I've done some research on this. According to an expert (un-named for reasons you can probably guess):
- it is not considered a full-function reader. It uses the system OS voices, which vary across platforms, and it is not very clever about figuring out the structure of a document, so it often reads in the wrong order. It cannot handle tables and any embedded images screw it up.
In other words, use JAWS or something.
I spent about 3 hours online yesterday with Adobe tech support. We figured out that the problem happens on both Windows and Mac OS, and it happens with files that Adobe built - so it is not just our files!! So they had no answer and "escaleted" the issue to a higher level of tech support. Maybe there is hope for an answer.
So does anyone know if a reader that will work on Mac OS and read the document as tagged with the photo descriptions and everything?
Did you check the following;
- does text to speech work in principle on your computer (for Mac, see System Preferences -> Dictation & Speech -> Text to speech; use the play button to test text to speech)? make sure to select a good voice, I believe the default voice on Mac OS X is "Alex" (which is fine). Close System Preferences (otherwise changes might not become active).
- open Text Edit, type some text, select the text, use "Edit -> Speech -> Start speaking" - do you hear the text being spoken by the voice configured in System Preferences?
- in Acrobat, go to "Preferences -> Reading", double check the setup for Readout Loud Options; recommended as a starter; set voice to default voice (Acrobat will pick it up from the system setup); make sure the volume is high (you can make it less loud later on)
- take any PDF that has text on it that when copied and then pasted into TextEdit shows up as meaningful text (there is the occasional PDF where text is not encoded propery, and pasting into TextEdit would show some gibberish); Important: Read aloud does not requrie that the text is tagged or even well tagged - it should work once there is properly encoded text; that said, for tagged PDF Red Aloud follows the order of the text content according to the tagging structure; nevertheless it is still just a sequential reading function, and does not try to be a screen reader or a really interactive text to speech tool, where one coudl jump around in the document or get additional info about stuff being spoken; anybody with serious needs would get better service from screen readers or similar tools (NVDA is free of charge! though only available on Windows)
- Sometimes Mac OS X and Acrobat behave in an unpredictable manner when it comes to text to speech; such problems tend to go away after a restart of the computer. I have no clue whetehr this gooes back to problems on Mac OS X or in Acrobat, or something else that might be interfering with either of the two.
- Disclaimer: I have no clue how this would work oin Windows.
If you followed the steps above, and it still doesn't work, please report back exactly what did not work.
Thank you for the suggestions. I have tried all of these things to no avail. Adobe supposedly escalated the issue to a higher level of tech support but of course I have not heard back from them.
Does anyone know of a reading application for the visually impaired for the Mac os???
Somebody took the time to describe in detail steps that might help. You fail to take the time to describe which of these steps did not help, and/or what the outcome of these steps was.
You take this forum for a service organisation, not for a community driven discusssion forum. That's OK, but do not expect any further assistance from people like me.
As I noted earlier, Read Out Loud just plain doesn't work, and my sources say Adobe is not in a hurry to fix this.
You need to google for another option. I've heard that many blind people use a thing called JAWS, but I have no experience with it.
I tried all of those steps earlier. None fixed the issue. Text to speech works in general. Adobe Read Out Loud does not, even when given a dead-simple PDF with exactly one paragraph of text, nothing fancy. While I agree that racn could have provided more detail, please consider the fact that Acrobat Read Out Loud is, to use the technical term, BROKE. As in doesn't fargin' work.
If you have a PDF where read aloud does work, please post it and we can see if it works on other machines.
On Mac OS X 10.8.5, in Safari 6.2.3 I printed this Adobe Forum HTML page (into which I am writing my reply in this very moment) to PDF (Print -> Save as PDF…), then opened it n Acrobat XI, activated Read aloud, asked Read aloud to "Read this page only" - and I am listening to my default voice Alex speaking the page to me.
Well, it works better than anything else I've seen. Specifically, it started reading "All Communities > Acrobat > etc and kept going until petesoltesz and the date/time. Then it SKIPPED down to read "99 views Categories... etc" then it went back up and read Pete's post: "I am using".... etc. and continued normal to the next post down, etc.
So, not quite perfect, but not bad. Safari 7.1.3, OS X 10.9.5, Acrobat 11.0.10.
More in a bit. I'm letting it read to the end.
So, it got to my first post, where it says "I can't get correct behavior..." and the voice got very choppy and not understandable. Then it stopped. I then hit pause and resume and it started again and worked OK for a bit. then the same problem on my next post. Pause/Resume, it reads the _next_ post (racn's) fine, but then stops. Pause/resume does NOT fix it this time.
I opened Word and created a simple file, containing:
Passengers will please refrain from flushing toilets on the train while standing in the station, I love you. Station Master’s awfully fussy, doesn’t like his station mussy. How do you like the way I part my hair?
I then saved it as a PDF using Word's save as PDF. Acrobat will not read a single word.
I also did a Print > Save as PDF; likewise, Acrobat would not read a word.
I re-opened the HTML page and Acrobat could read that, as before.
I tried about every path I could think of to get to PDF; Acrobat would not read any of them.
Olaf, want to give this simple text a try?
After trying a feew more documents, it seems the behavior of Read aloud in Acrobat XI is pretty erratic. For some documents, reading aloud works quite OK, for some it works for parts of a document, for some other documents it just remains silent.
So, yes, it looks like it is broken.
VoiceOver is the only screen reader for Mac, as far as I know, and it will read pdfs if you open them in Preview. It's built in to OS X so will work for Apple apps and any other app that supports Apple’s Accessibility APIs. Clearly Adobe hasn't bothered adding support – which, among other things, makes me question whether they are fully committed to supporting OS X.
Read Out Loud does not function properly on the Mac. This is a longstanding bug which Adobe appears completely uninterested in fixing. (They do mention that it may not be compatible with some OS's but don't specifically mention Mac.) Mostly it reads one page and then fails. After that, the only way to get it to read is to click each line of text. VoiceOver doesn't respect Acrobat tags, unfortunately, so artefacts are not ignored.
I have tried to troubleshoot this problem periodically since upgrading to Mavericks and starting to use Acrobat XI. My current workaround it to listen to documents I need to check on a Windows machine that has Acrobat Reader installed on it. The read out loud feature also works with Acrobat Pro XI on Windows as well if you have access to a Windows machine that has Acrobat Pro installed.
Pardon me olafdruemmer if my answer was not complete enough. Thank you again for your suggestions. I have tried EVERY ONE of them NONE of them corrected the problem. I didn't think I needed to relist every thing that did not work to respond to your post.
For everyone having this issue. I have an ongoing tech support file open with Adobe. So far I have supplied my files to them, they have given me files they created. Neither of us can get anything to read. We did get one file to read one page, not the entire document. Adobe has sent me several suggestions of preferences to change but none of them have gotten read. In my opinion they have a glitch with Mac OS that they are ignoring. I have wasted many hours online with Adobe to no avail.
If anyone does come up with a solution please pass it along so we can all end this frustration! Thank you!
2 people found this helpful
I don't have a solution per se, but I do think I might have isolated the problem and could provide a workaround. It appears that (on a Mac) characters that use the option key to generate them - such as en dashes (option-hyphen), ellipses (...), apostrophes, etc. - seem to break the Read Out Loud feature. If you change the en dash to a regular hyphen, the ellipsis to three periods, and the proper typographic apostrophe to a prime (i.e. turn off smart quotes), then Read Out Loud seems to work. I wish there were a fix for this. I don't like compromising proper typographic conventions to accommodate an accessible version.
Were you able to use Mac Adobe Reader read aloud before Upgrade to Mavericks? If so, what OS X version with what Adobe Reader version would likely work? I would be happy to load an older OS if it would help.
For what it is worth, I am trying to move from Windows 7 to Mac, and the Adobe Reader Read Aloud function is fine in Windows 7.
I've encountered something strange in my experience with the read aloud functionality. I'd like to think I know my way around the computer a little bit more than an average user, but I'm no where close to a computer programmer. I say this because I have found information online giving simple instructions to make the read aloud feature work, but as much as I try, the suggested solutions have never been able to work. What is strange in my situation is that Adobe acrobat reader DC thinks that it is reading the material, but it does not produce the audio. After becoming severely frustrated with this problem I asked my friend to let me install his copy of Adobe Acrobat XI Pro on my computer to see if was a problem with my computer and not the program. I then opened the same PDF file on Adobe Acrobat XI Pro and the read aloud function ran flawlessly. I'm not sure if they operate in the same manner when it comes to the read aloud function or if Adobe purposely limits the functionality of their free software, but I would think it would work in the same manner if it is advertised as such.
Has anyone else run into this problem?
This seems to be the case. I am having the same problem, getting Acrobat DC Pro to read even the simplest pdf. But find and replacing all instances of quotes, apostrophes, ligatures and dashes to basic characters makes an unreadable pdf readable.
Let me second I. Gryfe's suggestion about characters that use the option key.. I was given a complex doc with lots of text frames and lots of illustrations. It would not read aloud in either Acrobat Xi, Acrobat Pro DC, or Acrobat Reader. More precisely, it would read a selected line of text but would not read the page.
The page had a few lines with bullets, aka option-8, so I replaced those with plain old dashes are it will read the whole page. Victory!
I tried the insert-special character to insert a bullet; read aloud still failed. So, dashed are your friend....
I had noticed that it would not read even the one line if the one line had a bullet in it. So you can find "illegal" text, if you are patient, by going thru the doc and clicking on each line. If it reads, click the next one. If it doesn't read, you have fond a culprit. Tedious but it seems to work.
I'm using InDesign CC 2017.1 on Mac OS X