E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 9 (In chronological order)

From: Karlen Communications
Date: Thu, Apr 04 2019 7:44AM
Subject: More Adobe Acrobat Accessibility Errors
No previous message | Next message →

I just converted an accessible Word document (created using Word 2016 from
Office 365 subscription )to tagged PDF using the Acrobat/Adobe add-in
Ribbon. I did check the settings before doing so and everything seems fine.
I've used this document consistently since at least 2015 for my workshops.
This is the first time I've received these two errors.



I started getting the primary language failure last week and it continues.
The Microsoft conversion tool identifies the language as English which is
correct. I appreciate that it is not a localized language. But the Adobe
conversion tool from the Acrobat Ribbon did not identify any primary
language.



I also always add a document title in Word and usually this converts when
using either the Microsoft or Adobe conversion tools. It is still there is I
use the Microsoft conversion tool but I get an Adobe Accessibility Full
Check error in Acrobat Pro DC saying that there is no title for the
document. I press Ctrl + D and the title is there. I right click on the
title failure in the Accessibility Report and say "fix" and the title is
passed.



Am not sure what is going on but these two items are pretty basic for the
Acrobat Pro Dc conversion tool to not get right.



Is anyone else seeing this?



Cheers, Karen

From: L Snider
Date: Thu, Apr 04 2019 8:36AM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | Next message →

The title thing has been happening for years for me on both PC and
MAC. I find that now it usually transfers to PDF with the newest
updates to 365.

For the language, I am finding with the newest versions of Word (I am
on Fast Insider so I never know what is mainstream all the time) that
the language is not transferring, where it used to almost always
transfer.

The key is to figure out which program is the problem, this is the problem!

Cheers

Lisa

On Thu, Apr 4, 2019 at 9:02 AM Karlen Communications
< = EMAIL ADDRESS REMOVED = > wrote:
>
> I just converted an accessible Word document (created using Word 2016 from
> Office 365 subscription )to tagged PDF using the Acrobat/Adobe add-in
> Ribbon. I did check the settings before doing so and everything seems fine.
> I've used this document consistently since at least 2015 for my workshops.
> This is the first time I've received these two errors.
>
>
>
> I started getting the primary language failure last week and it continues.
> The Microsoft conversion tool identifies the language as English which is
> correct. I appreciate that it is not a localized language. But the Adobe
> conversion tool from the Acrobat Ribbon did not identify any primary
> language.
>
>
>
> I also always add a document title in Word and usually this converts when
> using either the Microsoft or Adobe conversion tools. It is still there is I
> use the Microsoft conversion tool but I get an Adobe Accessibility Full
> Check error in Acrobat Pro DC saying that there is no title for the
> document. I press Ctrl + D and the title is there. I right click on the
> title failure in the Accessibility Report and say "fix" and the title is
> passed.
>
>
>
> Am not sure what is going on but these two items are pretty basic for the
> Acrobat Pro Dc conversion tool to not get right.
>
>
>
> Is anyone else seeing this?
>
>
>
> Cheers, Karen
>
> > > >

From: Karlen Communications
Date: Thu, Apr 04 2019 8:54AM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | Next message →

I'm on Office Insider as well and both Acrobat Pro DC and Office 365/2016
desktop for Windows versions are up to date.

Cheers, Karen

From: L Snider
Date: Thu, Apr 04 2019 9:32AM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | Next message →

I noticed a change with the language not transferring about a year ago
with Insider, it is annoying.

The title transfer never worked for me for years (the actual title,
not the showing it), and I finally don't have to change that on PC,
but on Mac I can't remember as I have to use the PC to do PDFs...got
frustrated with Mac Word. I just tried it on Mac and the title
transfers but again the language doesn't.

In my view, Adobe fell behind about 7-8 years ago in terms of PDF
accessibility, and they are really making me crazy most of the time
now...

Cheers

Lisa

On Thu, Apr 4, 2019 at 10:04 AM Karlen Communications
< = EMAIL ADDRESS REMOVED = > wrote:
>
> I'm on Office Insider as well and both Acrobat Pro DC and Office 365/2016
> desktop for Windows versions are up to date.
>
> Cheers, Karen
>
>

From: Philip Kiff
Date: Thu, Apr 04 2019 12:36PM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | Next message →

I'm using current versions for Windows 10:
Office 365 on the monthly update stream (v16.0.11328.202220) 32-bit.
Acrobat Pro DC continuous release (v2019.010.20098)

When I generate a PDF using Acrobat's Save as Adobe PDF feature, the
title property gets transferred correctly, but the Filename is displayed
in the Title bar instead of the Title property. So I always get at least
this one error in Acrobat's Accessibility "Full Check" in any PDF
generated by Microsoft Word. This has been the case for a long time for me.

By contrast, if I generate the same file using the built-in MS Word
engine (using File -> Export - Create PDF/XPS Document), then the title
transfers correctly AND the title is also correctly displayed in the
title bar. There is no error produced in Acrobat's Accessibility Checker.

The language setting seems to be set just fine in PDFs that I generate
from MS Word with language set as Canadian English. This is true for
PDFs generated using Acrobat Pro or using MS  Word's built-in export to
PDF engine.

Phil.

Philip Kiff
D4K Communications

On 2019-04-04 11:32, L Snider wrote:
> I noticed a change with the language not transferring about a year ago
> with Insider, it is annoying.
>
> The title transfer never worked for me for years (the actual title,
> not the showing it), and I finally don't have to change that on PC,
> but on Mac I can't remember as I have to use the PC to do PDFs...got
> frustrated with Mac Word. I just tried it on Mac and the title
> transfers but again the language doesn't.
>
> In my view, Adobe fell behind about 7-8 years ago in terms of PDF
> accessibility, and they are really making me crazy most of the time
> now...
>
> Cheers
>
> Lisa
>
> On Thu, Apr 4, 2019 at 10:04 AM Karlen Communications
> < = EMAIL ADDRESS REMOVED = > wrote:
>> I'm on Office Insider as well and both Acrobat Pro DC and Office 365/2016
>> desktop for Windows versions are up to date.
>>
>> Cheers, Karen
>>
>>

From: Philip Kiff
Date: Thu, Apr 04 2019 12:43PM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | Next message →

I wonder if perhaps the language settings can get messed up if a file
contains multiple languages, or if there are some passages that contain
different regional variations of a language (for e.g., Canadian English
and U.S. or U.K English)? Some regional versions of English don't exist
in some versions of Word - especially when comparing Word for Windows
and Word for Mac - so it is possible for new language variations to
appear in code when someone else edits a file even though they are
editing in the same general language as the original. These kinds of
things might mess up the language settings of a file?

Phil.

On 2019-04-04 14:36, Philip Kiff wrote:
> I'm using current versions for Windows 10:
> Office 365 on the monthly update stream (v16.0.11328.202220) 32-bit.
> Acrobat Pro DC continuous release (v2019.010.20098)
>
> When I generate a PDF using Acrobat's Save as Adobe PDF feature, the
> title property gets transferred correctly, but the Filename is
> displayed in the Title bar instead of the Title property. So I always
> get at least this one error in Acrobat's Accessibility "Full Check" in
> any PDF generated by Microsoft Word. This has been the case for a long
> time for me.
>
> By contrast, if I generate the same file using the built-in MS Word
> engine (using File -> Export - Create PDF/XPS Document), then the
> title transfers correctly AND the title is also correctly displayed in
> the title bar. There is no error produced in Acrobat's Accessibility
> Checker.
>
> The language setting seems to be set just fine in PDFs that I generate
> from MS Word with language set as Canadian English. This is true for
> PDFs generated using Acrobat Pro or using MS  Word's built-in export
> to PDF engine.
>
> Phil.
>
> Philip Kiff
> D4K Communications
>
> On 2019-04-04 11:32, L Snider wrote:
>> I noticed a change with the language not transferring about a year ago
>> with Insider, it is annoying.
>>
>> The title transfer never worked for me for years (the actual title,
>> not the showing it), and I finally don't have to change that on PC,
>> but on Mac I can't remember as I have to use the PC to do PDFs...got
>> frustrated with Mac Word. I just tried it on Mac and the title
>> transfers but again the language doesn't.
>>
>> In my view, Adobe fell behind about 7-8 years ago in terms of PDF
>> accessibility, and they are really making me crazy most of the time
>> now...
>>
>> Cheers
>>
>> Lisa
>>
>> On Thu, Apr 4, 2019 at 10:04 AM Karlen Communications
>> < = EMAIL ADDRESS REMOVED = > wrote:
>>> I'm on Office Insider as well and both Acrobat Pro DC and Office
>>> 365/2016
>>> desktop for Windows versions are up to date.
>>>
>>> Cheers, Karen
>>>
>>>

From: Karlen Communications
Date: Thu, Apr 04 2019 1:38PM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | Next message →

I haven't had problems with EN-CA. I notice that when I use the Word/Microsoft conversion tool the primary language for the document I'm working on is English which is correct. You always want to have a generic language identified as the primary language (or on any Tags in a multilingual document) so that if a localized version of the language is not supported, the person can use their default generic language synthesizer/voice.

It also lets someone listen to the document with pronunciations they are used to hearing. For example, I use Eloquence with the British voice. If I have to listen to content using different pronunciations (for example American English), it takes me quite a while to understand what I'm reading and I imagine the same can be said for those using American English as their default synthesizer language who may have to listen to British pronunciations.

Maybe this is a change Word to snag a generic language and the Adobe conversion tool hasn't caught up to this yet. I would still think that they should be able to snag the language from somewhere in the document.

Cheers, Karen

From: Philip Kiff
Date: Thu, Apr 04 2019 2:16PM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | Next message →

On 2019-04-04 15:38, Karlen Communications wrote:
> You always want to have a generic language identified as the primary language (or on any Tags in a multilingual document) so that if a localized version of the language is not supported, the person can use their default generic language synthesizer/voice.
>
> It also lets someone listen to the document with pronunciations they are used to hearing.

Right. I think you or someone has mentioned that on this list before,
but I confess that I've been neglecting to do that in files I edit. My
Word files always have the language set to Canadian English to take
advantage of spellcheck using the Canadian dictionary in Word. I'll have
to pay closer attention to how I set the language when those get
exported into PDF.

Phil.

Philip Kiff
D4K Communications

From: Ilana Gordon
Date: Thu, Apr 04 2019 2:16PM
Subject: Re: More Adobe Acrobat Accessibility Errors
← Previous message | No next message

I've been monitoring this conversation closely and have one additional
question about the conversion from Word to PDF? I have both PC and MAC
versions of Word. I use Acrobat DC. It seems that both Microsoft and Adobe
have created a seemless and effective export with tags. But.... the
documents are sent to either Microsoft's cloud or Adobe's cloud if you use
the export features and not save as.

The big question by using that process does Adobe or Microsoft have use of
those documents and/or own them on the cloud and thus creating a security
and intellectual property ownership issue?

Looking forward to some answers on that!

Ilana Gordon




On Thu, Apr 4, 2019 at 4:03 PM Karlen Communications <
= EMAIL ADDRESS REMOVED = > wrote:

> I haven't had problems with EN-CA. I notice that when I use the
> Word/Microsoft conversion tool the primary language for the document I'm
> working on is English which is correct. You always want to have a generic
> language identified as the primary language (or on any Tags in a
> multilingual document) so that if a localized version of the language is
> not supported, the person can use their default generic language
> synthesizer/voice.
>
> It also lets someone listen to the document with pronunciations they are
> used to hearing. For example, I use Eloquence with the British voice. If I
> have to listen to content using different pronunciations (for example
> American English), it takes me quite a while to understand what I'm reading
> and I imagine the same can be said for those using American English as
> their default synthesizer language who may have to listen to British
> pronunciations.
>
> Maybe this is a change Word to snag a generic language and the Adobe
> conversion tool hasn't caught up to this yet. I would still think that they
> should be able to snag the language from somewhere in the document.
>
> Cheers, Karen
>
>
>