WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Do fonts have to be embedded in a WCAG 2.0 conformingPDFdocument?

for

From: Moore,Michael (DARS)
Date: Apr 15, 2015 11:14AM

From a functionality standpoint we have found that embedding fonts, particularly in PDF forms is problematic. This issue is that the PDF reader software will embed the fonts over and over again when a form is saved. Thus if a form is passed through a process where several people complete different sections, save the form and pass it to the next person the file size quickly becomes too large to fit through an email system. This has been particularly problematic for forms developed through LiveCycle Designer. We have been able to develop forms that have worked reliably for people using a wide range of assistive technologies on Windows systems. Still waiting for Adobe and Apple to work out their differences though. I don't know of a form technology other than HTML that is working correctly on MAC OS or IOS.

Mike Moore
Accessibility Coordinator,
Texas Department of Assistive and Rehabilitative Services
(512) 424-4159 (Office)
(512) 574-0091 (Cell)

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Duff Johnson
Sent: Wednesday, April 15, 2015 11:11 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Do fonts have to be embedded in a WCAG 2.0 conforming PDF document?

>
>> The lack of embedded fonts can cause a range of issues varying from (merely) an unintended ugly appearance to total illegibility.
>
> Regarding WCAG -- how is the experience specifically for people with disabilities impacted over the experience of people without disabilities.

Examples...

- Some users may depend on characteristics such as word-spacing, line-spacing, text alignment, etc to understand the document. As one example, imagine a screen magnifier user dealing with text in which the breaks between words aren't clear, or where characters overlap. A conventional user might have the problem to a limited extent, but the user running the magnifier is much more likely to be very seriously affected.

- AT software that replaces or manipulates fonts (for example to accommodate those with dyslexia) will not be able to function predictably (if at all).

> It seems that this is an overall usability issue for all people

It is certainly that, but it also disproportionally affects users with disabilities.

> -- but WCAG is focused on situations where comparable or equivalent access is not provided to people with disabilities.

Agreed, and I believe font embedding is such as case.

…but which SC?

Duff.