E-mail List Archives
Thread: PDF: Discrepancy with JAWS and NVDA
Number of posts in this thread: 9 (In chronological order)
From: Mohith BP
Date: Mon, Aug 22 2016 11:30PM
Subject: PDF: Discrepancy with JAWS and NVDA
No previous message | Next message →
Hi List,
I am facing a strange issue with the PDF files produced by Adobe InDesign.
The images in the document are with the appropriate alternate text.
NVDA is recognizing the images. However, JAWS is not recognizing any
images in the document.
Please suggest is there any solution for the same.
Thanks & Regards,
Mohith B. P.
From: Sean Murphy
Date: Mon, Aug 22 2016 11:57PM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | Next message →
What version of Jaws and Adobe?
> On 23 Aug 2016, at 3:30 PM, Mohith BP < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi List,
>
> I am facing a strange issue with the PDF files produced by Adobe InDesign.
> The images in the document are with the appropriate alternate text.
> NVDA is recognizing the images. However, JAWS is not recognizing any
> images in the document.
>
> Please suggest is there any solution for the same.
>
>
> Thanks & Regards,
> Mohith B. P.
> > > >
From: Mohith BP
Date: Tue, Aug 23 2016 12:37AM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | Next message →
Hi Sean,
Adobe Reader Version 11.0.10.32
JAWS Version 17.0.2619.400
Thanks & Regards,
Mohith B. P.
On 8/23/16, Sean Murphy < = EMAIL ADDRESS REMOVED = > wrote:
> What version of Jaws and Adobe?
>
>> On 23 Aug 2016, at 3:30 PM, Mohith BP < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> Hi List,
>>
>> I am facing a strange issue with the PDF files produced by Adobe InDesign.
>> The images in the document are with the appropriate alternate text.
>> NVDA is recognizing the images. However, JAWS is not recognizing any
>> images in the document.
>>
>> Please suggest is there any solution for the same.
>>
>>
>> Thanks & Regards,
>> Mohith B. P.
>> >> >> >> >
> > > > >
From: Karlen Communications
Date: Tue, Aug 23 2016 6:10AM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | Next message →
I think there is still the bug in JAWS 17 where it is not reading/finding images in PDF documents. I'm finding the same issue in Acrobat/Reader DC that existed in Acrobat/Reader XI. So this is a JAWS thing.
Cheers, Karen
From: Jamous, JP
Date: Tue, Aug 23 2016 6:19AM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | Next message →
Folks,
Please, if you are finding such bugs make sure to report them to FS or whatever the heck they are called now. We all pay for our SMAs and FS needs to live up to that promise of deliver Job Access with Speech.
Quick example, I was unable to use the Schedule Assistant to find vacant rooms to hold meetings with other teams. After their Tier I support was useless, they elevated my ticket to their escalation team, which I am not that crazy about either.
I was called twice and went through the issue with them thoroughly. They were unable to give me a solution or work-around. Lastly, they notified me that they contacted Microsoft and that is an issue that they are aware of at Microsoft. It will be fixed in 2016 365.
That answer was not a solution for me. I kept digging around and guess what? JAWS is capable of doing it and yes there is a work-around. I backfired at them with an e-mail that put them to shame.
The NVDA guys are not getting paid and are doing a much better job. We pay this company and we deserve as customers to get a good customer support.
So please, make sure to file this ticket with them. Do not let it slide. It behooves all of us.
Thank you.
**************************************************
Jean-Pierre Jamous
Digital Accessibility Specialist & Developer
UI Accessibility Team
The only limitations in life are those we set for ourselves
**************************************************
From: Jonathan Avila
Date: Tue, Aug 23 2016 6:53AM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | Next message →
> I think there is still the bug in JAWS 17 where it is not reading/finding images in PDF documents. I'm finding the same issue in Acrobat/Reader DC that existed in Acrobat/Reader XI. So this is a JAWS thing.
Yes, sadly this has been reported and is still an issue with the latest update of JAWS 17.
Jonathan
From: Whitney Quesenbery
Date: Tue, Aug 23 2016 8:47AM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | Next message →
What is a poor content producer supposed to do with this sort of problem?
Let's say you created an accessible PDF, with properly tagged and
alt-texted images.
Whose responsibility is it?
On Tue, Aug 23, 2016 at 8:54 AM Jonathan Avila < = EMAIL ADDRESS REMOVED = >
wrote:
> > I think there is still the bug in JAWS 17 where it is not
> reading/finding images in PDF documents. I'm finding the same issue in
> Acrobat/Reader DC that existed in Acrobat/Reader XI. So this is a JAWS
> thing.
>
> Yes, sadly this has been reported and is still an issue with the latest
> update of JAWS 17.
>
> Jonathan
>
>
>
>
From: Duff Johnson
Date: Tue, Aug 23 2016 8:53AM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | Next message →
>> I think there is still the bug in JAWS 17 where it is not reading/finding images in PDF documents. I'm finding the same issue in Acrobat/Reader DC that existed in Acrobat/Reader XI. So this is a JAWS thing.
>
> Yes, sadly this has been reported and is still an issue with the latest update of JAWS 17.
PDF/UA differs from other accessibility specifications, not only because it is unabashedly technology-specific, but because it includes requirements for:
- Files
- Reader software
- AT (yes!! even for AT!)
I look forward to the day when customers ask their AT vendor who *claims* to support accessible PDF this simple question:
"Does your software conform to PDF/UA? If not, when can we expect it?"
By their answer(s) shall their intentions be known.
Duff.
From: Karlen Communications
Date: Tue, Aug 23 2016 10:52AM
Subject: Re: PDF: Discrepancy with JAWS and NVDA
← Previous message | No next message
JAWS, while having a lot of the market share, is not the only adaptive technology so we have to keep that in mind. And for the previous versions of JAWS and hopefully the next version, this bug will be fixed...and hopefully it will be fixed in a JAWS 17 update.
While we may play "troubleshooting twister" in trying to ensure that graphics are "read" by one version of one adaptive technology, the good thing about PDF/UA and tagging to a standard rather than focusing on making content accessible to a specific adaptive technology and a specific version of an adaptive technology is that the content is universally accessible to other adaptive technologies and other version of JAWS (in this case) and if the problem isn't fixed, those of us who use screen readers will gravitate to the tools that serve us best.
Cheers, Karen