WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Errors with tab order and reading order in forms

for

From: Chagnon | PubCom
Date: Nov 29, 2016 11:50AM

No.
Part by part...
PDF is a self-contained file that includes the page layout, fonts, tags, graphics, and all other information required for the appearance.
Originally used PostScript page description programming language to do this, PDF now uses its own PostScript-like encoding. This "nails down" the appearance at the time the PDF is created from the source file. There's nothing left to anyone's interpretation or rendering. It is a hardwired file, which is why it's used in enterprises that need to record the data at a specific time.

Originally intended for the printing and graphics arts community which needed a way to move a design/layout from the designer's computer to the print shop's computer so that it could be printed. That's why it's locked down. Nothing should move, rewrap, or change as the file moves from one computer to the other.

There are no styles in a PDF.
So there isn't anything to apply to anything to create the presentation.

Not at all like HTML! To me, they are the exact opposites of each other.

--Bevi

-----Original Message-----
From: JP Jamous [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, November 29, 2016 1:30 PM
To: <EMAIL REMOVED> ; 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: RE: [WebAIM] Errors with tab order and reading order in forms

But doesn't Adobe reader reads the binary file and all of the styles in it and apply them to the objects to create the presentation intended?
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Chagnon | PubCom
Sent: Tuesday, November 29, 2016 11:37 AM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Errors with tab order and reading order in forms

JP Wrote: "I would tackle this one just like a web page since Adobe Reader is the equivalent of a browser."

Adobe/Acrobat Reader is definitely NOT the equivalent of a browser because a PDF is not the equivalent of an HTML file.

Two different coding entities. And the Acrobat PDF file format was in development before HTML was released.

You might be confusing the end-result action or delivery to the AT user, which should be similar, regardless of the file format. The PDF/UA standard was deliberately created to mirror and harmonize with the WCAG standard as much as possible, but it is not a duplicate of WCAG so, therefore, user agents like screen readers will interpret PDFs differently than HTML.

Acrobat Reader is a standalone software program as well as a plug-in for browsers, and it is not anything like a browser.

--Bevi Chagnon

- - -
Bevi Chagnon | www.PubCom.com
Technologists, Consultants, Trainers, Designers, and Developers for publishing & communication
| Acrobat PDF | Print | EPUBS | Sec. 508 Accessibility |
- - -

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of JP Jamous
Sent: Tuesday, November 29, 2016 11:44 AM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Errors with tab order and reading order in forms

Quickly, the answer is Yes.

I would tackle this one just like a web page since Adobe Reader is the equivalent of a browser.

Let Adobe set the tabindex based on the structure of the document. Map that structure in your head or on paper first. Secondly, test the output and if it needs a tabindex of 0 or higher to adjust it, you are good to go.

As long as the tab order for keyboard only and screen reader users is how it should be, go ahead and move on with other work. Don't sweat it.