Skip to main content
Participant
May 18, 2020
Question

Read Out Loud reading words as letters or acronyms

  • May 18, 2020
  • 4 replies
  • 6134 views

I'm having trouble creating an accessible PDF. Read Out Loud is working well except in one instance where it's reading a word as individual letters instead of as a word. I tried re-typing the word in Acrobat to no avail. The style is a Heading that is in all caps. However, the other Heading using this style is being read as a word. I tried turning off the "ALL CAPS" style in Word (where PDF originated from) and applying local "UPPERCASE" formatting. However, still the same problem in Acrobat. Any suggestions?

Thanks!

This topic has been closed for replies.

4 replies

a_C_student16379412
Inspiring
May 21, 2020

Bevi is dead on - as usual. Read Out Loud is not for accessibility testing (nor for anything else useful as far as I can tell). An alternative to JAWS or NVDA - which are great but have a learning curve - you may want to consider a screen-reader emulator like the one built into PAC 3 from Access for All - it is free and Google will easily find the download. 

Bevi Chagnon - PubCom.com
Legend
May 26, 2020
  • Acrobat's Read Out Loud (ROL) doesn't recognize the tag set in the PDF/UA-1 standard.
  • And it doesn't provide any of the user features that people find in real screen readers, such as JAWS and NVDA.
  • And it doesn't recognize form fields, so you can't fill out a form with it.
  • And depending upon how the original content creator created the source document in Word, PowerPoint, InDesign, etc., it will sometimes read horizontally across the columns of text, rather than follow the natural reading order of a multi-column page.
  • And ROL doesn't follow any reading order whatsoever, but per the PDF/UA-1 specification, it's supposed to follow the tag tree's reading order. Sometimes ROL reads the architectural/construction reading order, but then again, sometimes not.
  • It doesn't recognize language controls.
  • Or the metadata in the PDF, which should have language controls specified.
  • IIRC it didn't read out the Alt-text on graphics, links, or anything else that has Alt-text.
  • And doesn't announce lists.
  • Doesn't handle hyperlinks well, including regular URLs, emails, cross-refs, and any others.
  • Doesn't recognize a TOC and its individual TOCI (TOC items) and their hyperlinks.
  • And IIRC, it was developed before Unicode was standardized so it can choke on other than the basic ASCII character set.

I think it was added to Acrobat with Version 7...that would be in 2004, way before the PDF/UA standard was even being developed.

 

I doubt Adobe realizes how important a simple screen reader would be for society. I find it's recommended by social workers to those who have failing eyesight or reading dyslexias. But anyone would benefit from this who wants to just listen to a long tech document while doing chores, or working out, or while driving. It doesn't need to be fancy and compete with the big guns.

 

Just a simple, straightforward version that actually works to the PDF/UA standard (which Adobe creates, BTW).

 

But I don't see Adobe's head honchos approving the R&D budget for this. They're missing a great marketing opportunity.

 

 

|    Bevi Chagnon   |  Designer, Trainer, & Technologist for Accessible Documents ||    PubCom |    Classes & Books for Accessible InDesign, PDFs & MS Office |
JR Boulay
Community Expert
Community Expert
May 19, 2020

"Who's the "us" you're referring to?"

I guess he speaks to the hundreds of people who could read your message on this forum, and to the few who could answer your question.

😉

Acrobate du PDF, InDesigner et Photoshopographe
Adobe Employee
May 19, 2020

Hi,

I'm from the Accessibility Engineering Team from Adobe Acrobat and I'm here to assist you in solving the issues.

 

Further KS, I need to know the tags and content structure of those specific Heading to find the issue and help you in resolving it. We would be abel to help you only after we can see the file. Would it be possible for you to split and share only that specific page where the issue is being observed?

 

Thanks

Rachit

Bevi Chagnon - PubCom.com
Legend
May 19, 2020

Richit, you don't have an Adobe employee badge on forums, and I see you are relatively new on the forums. Mistook you for a troll, not that we've every had any on the forums before!

 

|    Bevi Chagnon   |  Designer, Trainer, & Technologist for Accessible Documents ||    PubCom |    Classes & Books for Accessible InDesign, PDFs & MS Office |
Bevi Chagnon - PubCom.com
Legend
May 19, 2020

Acrobat's built-in Read Out Loud utility is not a valid screen reader.

It is not compliant with any accessibility standards, including PDF/UA: it rarely process a document's information correctly, contains no user controls, and basically does nearly everything wrong.

Do not waste you time testing a PDF for  compliance with Read Out Loud. Use a valid, compliant screen reader such as JAWS or NVDA (which is free).

 

|    Bevi Chagnon   |  Designer, Trainer, & Technologist for Accessible Documents ||    PubCom |    Classes & Books for Accessible InDesign, PDFs & MS Office |
Adobe Employee
May 19, 2020

Hi,

Thanks for reporting the issue to us. Can you please share the pdf via a weblink so that we can investigate and provide a solution to your problem.

 

Thanks

Rachit

Participant
May 19, 2020

Hi Rachit,

Unfortunately, I can't. It's for a client and it's confidential, so I can't share the file. I can tell you that the uppercase word that Read Out Loud is getting correct is "PROGRAM," while the uppercase word it's reading as an acronym is "AWARDEES."

Thanks, KS