Acrobat's Read Aloud is not a screen reader.
Repeat: it is NOT a screen reader.
It does not access and render the content (aka, voice it) per current PDF/UA-1 and WCAG 2.0 accessibility standards. It does not have the majority of user controls that real screen readers have. And it consistently mis-reads basic content.
Do not waste your time testing a document for screen reader accessibility with Acrobat's Read Aloud tool. It will give you false positives and false negatives.
Many of us in the professional accessibility world have asked Adobe to either fix Read Aloud and make it a full-featured, compliant tool, or remove it from Acrobat entirely.
Do your testing with a real screen reader:
And don't forget to test for enlargement with ZOOM text, keyboard accessibility, and reading order for other AT (assistive technologies).
Accessibility is for all disabilities, not just blindness.
As Bevi suggested, please use JAWS or NVDA for testing a document for screen reader accessibility.
Read Out Loud was never designed as a complete Accessibility Solution. Respective screen readers like JAWS/NVDA for Windows and VoiceOver for Mac are the best available screen reader solutions (primarily for vision disabilities). That's one of the reasons that Adobe started funding NVDA (through NVAccess) to address the goals of accessibility support for PDFs in Acrobat Reader.
It's better to invest in providing a first-class screen reader experience than to over-haul ROL and keep playing a catch-up game with established screen readers which are already doing a great job and have much better and deeper integrations with respective operating systems.
ROL can be used as a tool in cases of situational disabilities (driving a car, cooking, reading outside on a sunny day) or as a very basic entry level tool (not calling it a screen reader yet) for users who don't want to learn how screen readers work.