RE: Issues with PDFs

Amanda,

Ctrl page up and ctrl page down moves by page when you are not in continuous mode. Ctrl shift g jumps to  a page. Cannot recall the command for table of contents which should be self documented when navigating the menus.


Sean Murphy
Accessibility Software engineer 
seanmmur@cisco.com
Tel: +61 2 8446 7751 Cisco Systems, Inc.
The Forum 201 Pacific Highway
ST LEONARDS
2065
Australia
cisco.com 
 
 Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.


-----Original Message-----
From: Amanda Lacy [mailto:lacy925@gmail.com] 
Sent: Thursday, 30 March 2017 8:19 AM
To: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Cc: Duff Johnson <duff@duff-johnson.com>; w3c-wai-ig <w3c-wai-ig@w3.org>
Subject: Re: Issues with PDFs

Changing it to left-to-right reading order seems to have solved two of my current problems. Words have spaces between them and the cursor seems to stay where I leave it. Thanks!

And by "random access" I meant the ability to jump around to a given page, chapter, etc.

On 3/29/17, Sean Murphy (seanmmur) <seanmmur@cisco.com> wrote:
> Thanks for the reason why text join together. If you change the 
> reading mode to left to right, addresses this issue I have found in 
> the past. It does change the layout of course.
>
> In prior releases of Adobe reader did not loose the place when using Jaws.
> If I get the time, I might check.
>
> Sean Murphy
> Accessibility Software engineer
> seanmmur@cisco.com
> Tel: +61 2 8446 7751 Cisco Systems, Inc.
> The Forum 201 Pacific Highway
> ST LEONARDS
> 2065
> Australia
> cisco.com 
>
>  Think before you print.
> This email may contain confidential and privileged material for the 
> sole use of the intended recipient. Any review, use, distribution or 
> disclosure by others is strictly prohibited. If you are not the 
> intended recipient (or authorized to receive for the recipient), 
> please contact the sender by reply email and delete all copies of this message.
>
>
> -----Original Message-----
> From: Duff Johnson [mailto:duff@duff-johnson.com]
> Sent: Thursday, 30 March 2017 7:56 AM
> To: Amanda Lacy <lacy925@gmail.com>
> Cc: w3c-wai-ig <w3c-wai-ig@w3.org>
> Subject: Re: Issues with PDFs
>
> 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.
>
>> Adobe doesn't save my place. If I arrow around in a PDF, alt-tab away 
>> to go do something else, then alt-tab back, I'm never in the place 
>> where I left off. Why is that? Again, fixable?
>
> I can’t speak to the interaction between the PDF viewer and NVDA in 
> this context. It’s likely this behavior is “application-dependent”. I 
> suggest checking NVDA’s support content.
>
>> Also, what commands provide the most random access which you think I 
>> should know?
>
> I’m not sure I understand what you mean here.
>
> Duff.
>

Received on Wednesday, 29 March 2017 21:27:31 UTC