- From: Michael A. Peters <mpeters@domblogger.net>
- Date: Thu, 30 Mar 2017 02:38:42 -0700
- To: w3c-wai-ig@w3.org
On 03/29/2017 01:55 PM, Duff Johnson wrote: > Hi Amanda, > >> I'm using NVDA and Windows 10 with Adobe reader. Can someone tell me >> why these things happen? >> >> I'm required to decide how many pages to display. If I choose "single >> page" I have to issue some command at the end of each page to keep >> reading. But if I choose "entire document", and the document is huge, >> Adobe reader crashes. Why should I need to worry about how much of >> anything is visible on the screen? Which setting just works without >> hassle? > > You didn’t say… but be sure you are using the latest version of Adobe Reader. > > The fact that you can only read what’s on the screen / on the page (PDF or HTML) isn’t an accessibility issue per se. I recognize that this isn’t much comfort to you. Yes, super-long PDF documents can present readability issues… but that problem is not PDF-specific. > >> Words blur together. > > This is due to poorly-tagged PDF files. > >> PDFs are full of these errors in my experience. How can I fix them? > > By complaining to the author that the files are poorly tagged, and are thus inaccessible. Is this a problem with specific software that creates PDF files? I create PDF files with LaTeX. Is there an easy way to make sure this running together of words in the PDF tags is not happening? I'm on Linux so I do not have access to accessibility software that requires Windows.
Received on Thursday, 30 March 2017 09:39:11 UTC