WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Do fonts have to be embedded in a WCAG 2.0 conforming PDF document?

for

From: Jonathan Avila
Date: Apr 15, 2015 6:41AM

> Well, what is the problem that can arise when fonts aren't embedded?

The idea as I understand it is that glyphs can be rendered differently such as enlarged when the font is embedded properly. While many people think non-scanned PDFs are not images they are actually rendered glyphs. I don't know all of the details and I know PDF/UA goes more into this topic -- but it would be good to hear from a PDF Guru as to whether not embedded fonts could impact SC 1.4.4. I'm sure someone could also put together some test files to compare how enlargement and reflow works in these different situations.

In addition, embedding the fonts allows you to change or fix things in the document with the original font. For example, say there is a typo and you need to correct it.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>

703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Patrick H. Lauke
Sent: Wednesday, April 15, 2015 8:04 AM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] Do fonts have to be embedded in a WCAG 2.0 conforming PDF document?

On 15/04/2015 12:46, Duff Johnson wrote:
>> I.e. if fonts are not embedded, what SC do you think is failing? If that failure can be turned into a pass/success if fonts *are* enabled, then that is justification enough for embedding the fonts.
>
> So… what do you think? Which SC applies, if any?

Well, what is the problem that can arise when fonts aren't embedded?

P