E-mail List Archives

Search E-mail List Archives for

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

From: Tony Olivero
Date: Fri, May 18 2012 7:52AM
Subject: PDF Header Questions
No previous message | Next message →

Hello:



Does anyone have any thoughts on why an H1 (created in the word source file)
would appear to a screenreader to span multiple lines broken across
characters? When I read it with JAWS, it's basically sounding like:



"Heading 1 in word: This is a heading 1.



In the PDF:

T

H

I

S



I

S

A heading 1



The source style is Ariel Narrow, 24pt, all caps



Thanks for any input.



Tony

From: Jared Smith
Date: Fri, May 18 2012 7:56AM
Subject: Re: PDF Header Questions
← Previous message | Next message →

On Fri, May 18, 2012 at 7:52 AM, Tony Olivero wrote:

> The source style is Ariel Narrow, 24pt, all caps

Seeing as only the all caps letters are read individually, I'd presume
that is what's causing it. How are you exporting to PDF? I'd think
that a proper export procedure would keep them together as words, but
maybe it's something in Acrobat. This should be relatively easy to fix
in Acrobat Pro.

Jared

From: Tony Olivero
Date: Fri, May 18 2012 8:01AM
Subject: Re: PDF Header Questions
← Previous message | Next message →

Jared Wrote:
Seeing as only the all caps letters are read individually, I'd presume
that is what's causing it. How are you exporting to PDF? I'd think
that a proper export procedure would keep them together as words, but
maybe it's something in Acrobat. This should be relatively easy to fix
in Acrobat Pro.
---

That was my thought, but I removed the all caps checkbox just to see what
would happened and had the same result. It's Word 2010, so I'm saving as a
PDF.

Tony

From: Birkir R. Gunnarsson
Date: Fri, May 18 2012 8:02AM
Subject: Re: PDF Header Questions
← Previous message | Next message →

When you go to save as PDF in Word, do you check if "save as tagged
PDF" is checked, it is in the options button that pops up in the "save
as" dialog, in 2007 and 2010 anyway.
It could be the capital letters perhaps (I can check later today on my
system), but this sounds like lack of tagging to me at first
impression.


On 5/18/12, Jared Smith < = EMAIL ADDRESS REMOVED = > wrote:
> On Fri, May 18, 2012 at 7:52 AM, Tony Olivero wrote:
>
>> The source style is Ariel Narrow, 24pt, all caps
>
> Seeing as only the all caps letters are read individually, I'd presume
> that is what's causing it. How are you exporting to PDF? I'd think
> that a proper export procedure would keep them together as words, but
> maybe it's something in Acrobat. This should be relatively easy to fix
> in Acrobat Pro.
>
> Jared
> > > >

From: Karlen Communications
Date: Fri, May 18 2012 8:12AM
Subject: Re: PDF Header Questions
← Previous message | Next message →

It sounds like a font issue. This font is known to cause this type of
problems. It can be repaired in Acrobat by adding Actual Text to the <H1>
Tag. However, you might then get an accessibility error indicating that
there is alternative text that will not be read by adaptive technology.
Sometimes you'll get this message and sometimes you won't. It is because
you've added the attribute to something other than a <Figure> Tag.

The type of font you used is not a "standard" font and is sort of a hybrid
for lack of better phrasing.

Cheers, Karen

From: Tony Olivero
Date: Fri, May 18 2012 8:22AM
Subject: Re: PDF Header Questions
← Previous message | Next message →

Birkir Wrote:
When you go to save as PDF in Word, do you check if "save as tagged
PDF" is checked?
---

Birkir-- Yes, it's checked and producing a tagged (all be it freakishly)
file.

Karen wrote:
It sounds like a font issue. This font is known to cause this type of
problems.
---

Karen-- Thanks. That's what my experimenting was leading me to wonder about.
I appreciate the confirmation.

Thanks,
Tony

From: Ted
Date: Sat, May 19 2012 2:01AM
Subject: Re: PDF Header Questions
← Previous message | No next message

If you think your readership might include ZoomText users, a ZoomText bug to
watch for when using Actual Text to fix a problem like this is that the
Actual Text will appear multiple times.

In this case, it will appear once for each of "T", "H", "I", "S", "I", "S"
and "A heading level 1". So the Actual text will be heard seven times in
succession in both App Reader and Doc Reader and will appear (visually)
seven times in a row in DocReader.

With a bit of messing about in the Content panel this can usually be reduced
to just two instances, but much better to try to fix the problem at source
if possible.

Ted Page
Director PWS Ltd
www.pws-ltd.com