WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: revisiting links to document downloads

for

From: Angela French
Date: Jun 16, 2011 2:12PM


Anything is on the table. Right now I'm experimenting with CSS attribute selectors to make the document icon come in dependent upon the file extension like this:

a[href$=".pdf"]:after
{
content: url(/imgs/layout/icon_pdf.gif);
}

but IE 7 doesn't support.

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of <EMAIL REMOVED>
Sent: Thursday, June 16, 2011 12:30 PM
To: WebAIM Discussion List
Cc: 'WebAim Forum ( <EMAIL REMOVED> )'; <EMAIL REMOVED>
Subject: Re: [WebAIM] revisiting links to document downloads

Angela,

I'm not a screen reader user, but I might be able to help. I'm just not sure about the visual and interactive constraints. Can the text be clickable? Does the PDF have to be an actual src image or can it be a background image? Does this PDF image have to be clickable in the way that it is now? Does this HAVE to be in a table?

Thanks!


Vincent Young
User Experience, Web Accessibility Specialist Nationwide Corporate Marketing Nationwide(r) o | 614*677*5094 c | 614*607*3400 e | <EMAIL REMOVED>




From:
Angela French < <EMAIL REMOVED> >
To:
"'WebAim Forum ( <EMAIL REMOVED> )'"
< <EMAIL REMOVED> >
Date:
06/16/2011 03:06 PM
Subject:
[WebAIM] revisiting links to document downloads Sent by:
<EMAIL REMOVED>



I am working on a plan to make our state agency's website accessible.
There are many issues, but one in particular is giving me a headache - how to present, in a consistent manner site-wide, links to documents for download.

Here is an example of one current implementation:
http://sbctc.edu/college/f_operatingbudget.aspx . As you can see, there are two main issues here. One is that a table is used as the presentation method. This table isn't constructed correctly as there are no table headers. The second is that the actual link (the PDF icon) is not associated with its title which is the preceding table cell. I imagine this makes it hard for screen reader users to comprehend the page content, and of course links mode is not possible at all. But for the sighted person, the construct works well design-wise.

These document links could be presented as a list of links with the document category (for example 2011-13 Budget Request) represented as a heading. The problem (visually) with this approach is that different list links on different pages would have these category headings at various heading levels depending on the page context. I would like to come up with a consistent presentational approach.

Here is an example of another current implementation:
http://sbctc.edu/college/_e-assessreports.aspx. As this presentation spans over multiple years, it does "fit" well in a table in that it is a condensed use of page real estate. Put again, no table headers, and no association of document link with the actual title of the document.

Then there is this page, where it is unlikely that any user, sighted or not, has a clue what the document icons open!
http://sbctc.edu/general/a_strategictechplan.aspx

See what I'm up against? If any screen reader users would chime in on this one, I'd be grateful. The goal: a consistent approach to presenting documents for download that is accessible and uses screen real estate in a conservative manner.

Thanks!

Angela French
Internet Specialist
State Board for Community and Technical Colleges
360-704-4316
<EMAIL REMOVED>
http://www.checkoutacollege.com<;http://www.checkoutacollege.com/>;