PDF vs. HTML

Last week I had an oppor­tu­nity to visit with some fac­ulty and staff at a Com­mu­nity Col­lege around the topic of acces­si­ble dis­tance edu­ca­tion. The school had recently cho­sen Black­board as their Learn­ing Man­age­ment Sys­tem and is work­ing to adopt an atti­tude of Uni­ver­sal Design before their instruc­tors learn any other way of doing things– kudos to them.

We talked about under­stand­ing the per­spec­tive of learn­ers with dis­abil­i­ties, went over seman­tic markup, alt tags and acces­si­ble video . Up to this point every­one seemed to be on the same page. How­ever, there were some dif­fer­ences of opin­ion when we talked about the best for­mat for dis­play­ing con­tent online. The Direc­tor of Teach­ing and Learn­ing Tech­nolo­gies, John-Paul San Gio­vanni is encour­ag­ing instruc­tors to con­vert their course con­tent into PDF files to pro­mote a uni­form for­mat for every­thing. Since the train­ing, John-Paul and I have opened up a dia­log and with his per­mis­sion, I’m open­ing the dis­cus­sion up to Curb Cut read­ers– I hope you’ll take a sec­ond to weigh
in with your opin­ion (doesn’t every­one has an opin­ion regard­ing PDF docs?).

Our dis­cus­sion has revolved around both acces­si­bil­ity and usabil­ity. Regard­ing acces­si­bil­ity, I put forth an
arti­cle titled Adobe Acro­bat Acces­si­bil­ity Tech­niques
from the good folks at WebAIM. John-Paul thought­fully went through the arti­cle and rebutted six points made at the begin­ning of the arti­cle, here are his com­ments, verbatim:

  1. �Not every­one has the lat­est ver­sion of the Acro­bat Reader�. This state­ment could be made for any soft­ware prod­uct includ­ing the browsers being used, word pro­cess­ing soft­ware, etc. So what rel­e­vant impor­tance does it really have in com­par­ing the advantages/disadvantages of con­ver­sion to HTML ver­sus con­ver­sion to PDF file? If any­thing, since Acro­bat Reader 6 is a free down­load, one can have the lat­est ver­sion at no cost and will take less time to down­load than an updated browser, etc.
  2. �Not every­one who has the lat­est ver­sion has the full ver­sion with the embed­ded speech syn­the­sizer�. Again, since it is a free down­load, how is this point impor­tant rel­e­vant in com­par­ing the rel­a­tive acces­si­bil­ity achieved via a �con­vert to HTML� ver­sus a �con­vert to PDF�. I won­der when was the last time the author went to the Adobe site for the free down­load with the speech syn­the­sizer � it�s there.
  3. �The embed­ded speech syn­the­sizer is not as good as the full-featured screen read­ers � (i.e., JAWS, Win­dow Eyes)�. This is the equiv­a­lent of say­ing EXCEL is not as good of a word proces­sor as WORD. ACROBAT is a tool for mak­ing PDF files. JAWS, etc. is a screen reader tool. Is it fair to JAWS does not make PDF files as good as ACROBAT? I do not think so! More dis­turb­ing to me, how­ever, is that author missed (or failed to men­tion) an impor­tant point regard­ing ACROBAT 6 rel­a­tive to acces­si­bil­ity fea­tures, namely, that it accu­rately trans­lates the struc­ture and tag­ging of the base doc­u­ment with a com­pe­tence equal to that of a �con­vert to HTML� for MS Office prod­ucts � a major source of e-formatted files.
  4. �Not every­one knows that the speech syn­the­sizer exists � in ACROBAT Reader�. And whose fault is that? This point is obvi­ously not an inher­ent fea­ture of ACROBAT 6. Should a sim­i­lar state­ment be made regard­ing HTML because many of the inex­pe­ri­enced writ­ers of HTML do not know all the para­me­ters avail­able within HTML? One could equally point out that many users of WORD do not know that they can �con­vert to HTML� from a menu (and, for most that do know, how long did it take them to find out?). In a sim­i­lar vein, most WORD users do not know of the �Styles� capa­bil­ity and its value dur­ing a �con­vert to HTML�? The fact that many users of WORD do not know of these fea­tures of WORD is not an inher­ent fault of WORD. Sim­i­larly, the igno­rance of a par­tic­u­lar fea­ture of any tool (espe­cially, if accessed via menus) is not an inher­ent prob­lem with the tool. Since this point does not state an inher­ent prob­lem with ACROBAT 6, it is irrel­e­vant in com­par­ing the afore­men­tioned alter­nate approaches to con­ver­sion rel­a­tive to accessibility.
  5. �Users who know that the speech syn­the­sizer exists may be reluc­tant to use it because they do not know how to use it�. With ACROBAT 6, chal­lenged users may use any full-featured screen reader they choose on the resul­tant PDF. That is part of beauty of what ACROBAT 6 offers regard­ing acces­si­bil­ity. It is a very impor­tant point that it is not nec­es­sary to use the embed­ded syn­the­sizer in ACROBAT Reader 6 � the users can use what­ever they are com­fort­able with. On the other hand, in all hon­esty, with all the truly dif­fi­cult things that chal­lenged indi­vid­u­als must learn to do with a com­puter, three clicks from pull-down menus or, alter­na­tively, click­ing ALT then V then A then O or E would prob­a­bly seem rel­a­tively easy. That is all that is involved in the acti­vat­ing the ACROBAT Reader�s speech synthesizer.
  6. �If the doc­u­ment is not cre­ated with acces­si­bil­ity in mind, it will likely pose acces­si­bil­ity chal­lenges to blind users�. This state­ment is equally true for �con­vert to HTML� or the ACROBAT 6 �con­vert to PDF�. The �con­vert to HTML� in WORD, Pow­er­Point, and other prod­ucts is no bet­ter at mag­i­cally gen­er­at­ing good acces­si­bil­ity code than the ACROBAT 6 �con­vert to PDF�. Con­se­quently, this state­ment says noth­ing about the rel­a­tive advan­tage of con­vert­ing to HTML ver­sus con­vert­ing to a PDF.

What are your thoughts on the above?

On the usabil­ity front, I’ll point to two arti­cles. The first one from Jakob Nielsen is titled
PDF: Unfit for Human Con­sump­tion
where he out­lines the “usabil­ity crimes” of PDF doc­u­ments and the sec­ond is a rebut­tal
to the first titled Adobe’s Robert McDaniels responds (again) to
Nielsen crit­i­cisms of PDF
which both make good points. What do you think about the usabil­ity of PDF docs?

I have my own opin­ions on the mat­ter, but will reserve them for the com­ments or a later post. In the mean­time, site
stats show we’re get­ting a fair num­ber of daily vis­its– even though not many of you com­ment, I know you’re out there. If you don’t mind, take a sec­ond to post your thoughts and on the topic, thanks.

  1. temelini says:

    I think that the good folks at WebAIM make some impor­tant points, in gen­eral, about pdf doc­u­ments and acces­si­bil­ity. I do have to say, though, that I was sur­prised at the some­what flimsy “words of cau­tion” that were put forth by WebAIM when think­ing about using Acro­bat to cre­ate “acces­si­ble files.” I agree with most of John-Paul’s points that he makes in refut­ing the WebAIM doc­u­ment. The first five cau­tions do not in fact have any­thing to do with the Acro­bat soft­ware itself– they cau­tion that USERS might not “have the soft­ware.. be afraid to use it, etc.” I think that it is a very good thing that Adobe is work­ing hard toward mak­ing pdfs acces­si­ble… this is cer­tainly a pos­i­tive step in the right direc­tion, albeit not perfect.

    In a per­fect world, every­one cre­at­ing web­sites would have access to a web devel­oper who is up to speed on the lat­est in acces­si­bil­ity, and per­haps even the money to hire that per­son. This, unfor­tu­nately, is not so now, nor will it ever be that way. Web experts these days need to be more spe­cial­ized than ever. There is no escap­ing the fact, how­ever, that schools and other orga­ni­za­tions will con­tinue to cre­ate web­sites with­out using “pro­fes­sion­als.” There is also no doubt that both Microsoft Word or Adobe Acro­bat are not going away any­time soon. If any­thing they are becom­ing more ubiq­ui­tous. So if (and admit­tedly this is a big IF…) Adobe con­tin­ues to move toward mak­ing it easy to mark up sim­ple word docs so that the result­ing pdfs are acces­si­ble, then I think it is more real­is­tic to go this way, at least for now, then to cling to the hope that teach­ers and oth­ers will some­how yearn to become expert in XML and the sub­tle nuances of code.

    Now please take this all with the knowl­edge that I have not had much expe­ri­ence in mark­ing up Word docs or pdf so that they are able to be read by screen read­ers. If peo­ple need to go ahead and get some advanced train­ing on how to mark these up just like one would go about post­ing acces­si­ble text in gen­eral, then I believe that one should go ahead and learn html. My feel­ing is that this is not in fact the case. But that is for some­one else to com­ment on.

  2. I am not a usabil­ity expert, but here are my com­ments:
    I thought that ver­sion 6.0 speech fea­ture was cool, and found it with­out any notice that it was avail­able.
    I don’t like pdf for gen­eral infor­ma­tion, because it is harder to index in a site search, and I would rather not down­load an entire arti­cle, just to read in the first five lines that it is not what I was look­ing for.
    But it has a place, for archive infor­ma­tion that needs to be looked at more that once, for print­ing, and for re-distribution in a com­mon for­mat.
    It has a strong place as a file/reporting format.

  3. Carey says:

    Adobe Acro­bat became pop­u­lar because of its abil­ity to pre­serve the lay­out, typo­graphic, and other visual qual­i­ties of doc­u­ments in a world frus­trated by so many vari­a­tions in avail­able fonts, browser quirks, and pro­pri­etary doc­u­ment view­ing pro­grams. Design­ers and authors were will­ing to put forth the money and time to use Acro­bat because the final product’s visual accu­racy was “worth it”. But in cre­at­ing this safe zone for pre­serv­ing visual design, Adobe ignored, until ver­sion 6, the need for inter­nal markup to reflect the con­cep­tual orga­ni­za­tion of con­tent. This fun­da­men­tal pref­er­ence for visual design over con­cep­tual orga­ni­za­tion will not dis­ap­pear any time soon because Adobe will never aban­don their orig­i­nal pur­pose for Acro­bat. They are try­ing to have it both ways, but at its very best, Acro­bat will always be visual with struc­ture added. HTML on the other hand was designed around hier­ar­chi­cally struc­tured con­tent and only became con­cerned with visual design as an after-thought. In an acces­si­ble Web-based learn­ing envi­ron­ment, struc­ture and con­sis­tency are every­thing and visual design fidelity is nearly noth­ing. There­fore HTML (or bet­ter yet XHTML) IS the future of acces­si­ble markup and PDF has no short-term future. Uni­ver­si­ties would be wiser to develop and dis­trib­ute well-designed CSS2 style sheets to be applied to stan­dard HTML tagged doc­u­ments than to train their fac­ulty and staff to mas­ter the mys­ter­ies of Acro­bat Acces­si­bil­ity Plug-ins.

  4. Thanks for your com­ments– this is def­i­nitely an impor­tant issue. My expe­ri­ence with mark­ing up Word/PDF doc­u­ments is that it is not an extremely intu­itive or user-friendly process. Is it eas­ier than cre­at­ing an HTML page? I sup­pose that depends pri­mar­ily on what train­ing and resources are avail­able to fac­ulty. If fac­ulty were given a tem­plate with a well-defined style sheet for a Word to PDF doc­u­ment it would def­i­nitely be doable for most peo­ple, but I think that the same could be said of an HTML doc­u­ment.
    Unfor­tu­nately few if any of the tools com­monly used in cre­at­ing either for­mat still have a ways to go in encour­ag­ing (or forc­ing) users to cre­ate acces­si­ble doc­u­ments.
    As for some of the rea­sons that I pre­fer HTML over PDF– look for a post in the near future…