Accessible Search Engine

With­out a doubt, my favorite online learn­ing tool is Google where I can gen­er­ally find answers to just about what­ever real world prob­lem I hap­pen to be fac­ing at any given time. I’m not sure how acces­si­ble Google and other major search engines are (or aren’t) but I just came across YouSe­arched which bills itself as The Acces­si­ble Search. I would doubt that the qual­ity of search results is as high as the big play­ers, but some of the fea­tures may be nice for cer­tain situations.

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.

Understanding Experiences of Users with Disabilities

A List Apart pub­lished an arti­cle a few days ago titled, What is Web Acces­si­bil­ity? by Tren­ton Moss. The arti­cle doesn’t attempt to explain any tech­ni­cal con­cept, but sim­ply to help the reader under­stand the impli­ca­tions of dif­fer­ent dis­abil­i­ties of web use. WebAIM does the same thing in their Intro­duc­tion to Web Acces­si­bil­ity by Paul Bohman, espe­cially with the accom­pa­ny­ing arti­cles on visual, hear­ing, motor and cog­ni­tive dis­abil­i­ties listed at the bot­tom of that page, each con­tain­ing infor­ma­tion on spe­cific dis­abil­i­ties in those categories.

Under­stand­ing the nature of how dif­fer­ent dis­abil­i­ties affect web use (as opposed to sim­ply under­stand­ing acces­si­ble cod­ing prac­tices) is essen­tial in order to ensure your site is really acces­si­ble. If you have a solid under­stand­ing of what bar­ri­ers your vis­i­tors might encounter then there may be occa­sions when it would be okay to break a gen­er­ally accepted rule or a need to go beyond what is required by accepted guidelines.

So can these per­spec­tives be gained? I think a good place to start would be to talk to per­sons who might encounter some of the bar­ri­ers from inac­ces­si­ble design, ask them ques­tions about their expe­ri­ences. Arti­cles such as those men­tioned above can be help­ful, as well as online sim­u­la­tions such as these from WebAIM (Screen Reader, Low-vision and Cog­ni­tive), a vision sim­u­la­tion from the State of Ver­mont or a color blind­ness sim­u­la­tion from Vischeck.

Other ideas on how to gain this perspective?