E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 7 (In chronological order)

From: David Ashleydale
Date: Wed, Mar 18 2009 3:35PM
Subject: PDF Default Behavior
No previous message | Next message →

Does anyone know the default behavior for links that open PDFs? Is the
default behavior to open the PDF in the parent window, or is it to open
Adobe Reader separate from the browser? I would guess it's different for
different browser/platform combos.

I know that PDFs opening within the browser window can be problematic for
non-mouse users, because the keyboard "previous page" command (Alt + left
arrow) will no longer take the user back to the originating browser page. If
the default behavior is to open PDFs in Reader outside of the browser, then
that's fine. But if the default behavior is to open them within the browser,
I wonder what I can do to make the experience better for non-mouse users. I
could force the PDF to open in a new browser window, but that sometimes
seems to result in blank browser windows, depending on the user's setup.

Is there a good "best practice" for accessibly coding links that go to PDFs?
Is it best to just leave them as is, or is there something that page
designers can do to make them more accessible to everyone? I do like to at
least include "(PDF)" at the end of the link text.

Thanks,
David

From: Waltenberger, Lon (LNI)
Date: Wed, Mar 18 2009 4:10PM
Subject: Re: PDF Default Behavior
← Previous message | Next message →

I think it's best to go by convention, or what users see on 80% of the
sites they visit, and to not override default behavior because that's
what users are accustomed to.

Even though I agree with Nielsen about not opening new browser windows,
that argument didn't prevail in our design planning for our public site.

However, we do include file type, size, download time at 57K dialup plus
20% overhead for files over 400KB, and off-site information in links for
screen reader and other users who list links. We style that additional
info so it visually appears to not be part of the link.

This ensures that the links include vital information to screen reader
users when out of context.

Under the Claims & Insurance tab we also work very hard to ensure the
PDFs are accessible. It's impossible to have a 100% record but we're
close.

For example:
http://www.lni.wa.gov/ClaimsIns/Insurance/RatesRisk/Check/RatesHistory/d
efault.asp.

http://www.lni.wa.gov/ClaimsIns/Insurance/Learn/StateFund/Reports/Defaul
t.asp.

http://www.lni.wa.gov/ClaimsIns/Insurance/Learn/StateFund/RelatedInfo/De
fault.asp.

From: Jablonski, James (LNI)
Date: Thu, Mar 19 2009 12:00PM
Subject: Re: PDF Default Behavior
← Previous message | Next message →

Hi Lon,
Nice contribution to the global discussion!

I fired up a link on one of your offered pages and the way your team put
this together even more excellent in light of the on-line discussion.
(Also, I understand it better now! - thanks again.)

I did find one non-linked file spec on
http://www.lni.wa.gov/ClaimsIns/Insurance/DataStatistics/WorkersCompData
/default.asp that being the first entry under "Research Reports" Right
after the PDF icon, it reads:
Employer Assisted Injury Reporting ( 824 KB PDF / 2.5 min) - A Report to
the Legislature.

There is a leading space in front of the file size, and FYI (oops) none
of the parenthetical info in this one was styled as a link. Thought
you'd like to know.

James

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Waltenberger,
Lon (LNI)
Sent: Wednesday, March 18, 2009 3:09 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [WebAIM] PDF Default Behavior

I think it's best to go by convention, or what users see on 80% of the
sites they visit, and to not override default behavior because that's
what users are accustomed to.

Even though I agree with Nielsen about not opening new browser windows,
that argument didn't prevail in our design planning for our public site.

However, we do include file type, size, download time at 57K dialup plus
20% overhead for files over 400KB, and off-site information in links for
screen reader and other users who list links. We style that additional
info so it visually appears to not be part of the link.

This ensures that the links include vital information to screen reader
users when out of context.

Under the Claims & Insurance tab we also work very hard to ensure the
PDFs are accessible. It's impossible to have a 100% record but we're
close.

For example:
http://www.lni.wa.gov/ClaimsIns/Insurance/RatesRisk/Check/RatesHistory/d
efault.asp.

http://www.lni.wa.gov/ClaimsIns/Insurance/Learn/StateFund/Reports/Defaul
t.asp.

http://www.lni.wa.gov/ClaimsIns/Insurance/Learn/StateFund/RelatedInfo/De
fault.asp.

From: Claudia.Case@wellsfargo.com
Date: Thu, Mar 19 2009 1:20PM
Subject: Re: PDF Default Behavior
← Previous message | Next message →

David,
In my experience, if you are using IE, it seems to depend on how you have your file types configured in Windows Explorer. In Windows Explorer, I have the PDF file type set to Open with Adobe Acrobat so IE follows that rule. I believe the default behavior is for it to open in the browser. (I overruled the default behavior.)

c
-----Original Message-----
From: David Ashleydale [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Wednesday, March 18, 2009 2:33 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] PDF Default Behavior

Does anyone know the default behavior for links that open PDFs? Is the
default behavior to open the PDF in the parent window, or is it to open
Adobe Reader separate from the browser? I would guess it's different for
different browser/platform combos.

I know that PDFs opening within the browser window can be problematic for
non-mouse users, because the keyboard "previous page" command (Alt + left
arrow) will no longer take the user back to the originating browser page. If
the default behavior is to open PDFs in Reader outside of the browser, then
that's fine. But if the default behavior is to open them within the browser,
I wonder what I can do to make the experience better for non-mouse users. I
could force the PDF to open in a new browser window, but that sometimes
seems to result in blank browser windows, depending on the user's setup.

Is there a good "best practice" for accessibly coding links that go to PDFs?
Is it best to just leave them as is, or is there something that page
designers can do to make them more accessible to everyone? I do like to at
least include "(PDF)" at the end of the link text.

Thanks,
David

From: Eoin Campbell
Date: Thu, Mar 19 2009 2:45PM
Subject: Re: PDF Default Behavior
← Previous message | Next message →

In fact, Jakob Neilsen recommends opening PDFs and other
non-HTML pages in the appropriate application, rather
than inside a browser window.
cf. http://www.useit.com/alertbox/open_new_windows.html

"Waltenberger, Lon (LNI)" wrote:
> I think it's best to go by convention, or what users see on 80% of the
> sites they visit, and to not override default behavior because that's
> what users are accustomed to.
>
> Even though I agree with Nielsen about not opening new browser windows,
> that argument didn't prevail in our design planning for our public site.

--
Eoin Campbell
= EMAIL ADDRESS REMOVED =

From: Travis Roth
Date: Fri, Mar 20 2009 8:45AM
Subject: Re: PDF Default Behavior
← Previous message | Next message →

It is a setting in Adobe Reader preferences if a PDF file opened from the
internet should be displayed in the browser or not.
Look under Preferences.Internet dialog in Adobe Reader.


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Eoin Campbell
Sent: Thursday, March 19, 2009 3:46 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [WebAIM] PDF Default Behavior

In fact, Jakob Neilsen recommends opening PDFs and other
non-HTML pages in the appropriate application, rather
than inside a browser window.
cf. http://www.useit.com/alertbox/open_new_windows.html

"Waltenberger, Lon (LNI)" wrote:
> I think it's best to go by convention, or what users see on 80% of the
> sites they visit, and to not override default behavior because that's
> what users are accustomed to.
>
> Even though I agree with Nielsen about not opening new browser windows,
> that argument didn't prevail in our design planning for our public site.

--
Eoin Campbell
= EMAIL ADDRESS REMOVED =

From: Waltenberger, Lon (LNI)
Date: Fri, Mar 20 2009 1:00PM
Subject: Re: PDF Default Behavior
← Previous message | No next message

Well, I'll be danged...thanks for correcting me.

The decision I mentioned was made prior to Jakob's change of mind in
2005. I must've missed that Alertbox issue.

The linked Alertbox notes 4 guidelines for linking to non-Web documents.
If one decides to open a new browser window, I think the most important
of these is to also warn the users in advance.

That warning is especially important to those who use assistive
technologies such as screen readers and, especially, screen magnifiers.
If someone is zoomed in and a pop-up or other new window opens they may
not get a clue that a new window opened and then not be aware of any
changes.

When screen readers list links, the only way the warning about a new
window would be available to them is if the warning is included in the
link text.

We provide a warning only if users read the page and catch a phrase
about it following a link to "Get Help Downloading Files" that appears
close to linked non-Web files. Technically we fail Jakob's criterion to
warn users in advance because we don't equally and effectively warn all
users.

By standard, we open all files (non-Web documents) in new browser
windows not in a file's native PC format. Even PDFs open in another
browser window by default. I think that PDFs will, by default, open in
Adobe Acrobat (standard or pro) if it's on the system. If MS Office 2007
products are on a system, those file types open in the native
application, at least that's my experience.

This brings me back to my original premise: Leave changes to default
behaviors up to the user who is accustomed to how their systems
function. There are too many unknowns to determine the outcome of
changing default behaviors. I'll now add that if you choose to change
default behaviors, then effectively and equally warn all users.

It's not a perfect world. I support portions of arguments on both sides
of the issue; however, in the end, it's about serving information to
users in the simplest, most easily understood manner possible.
Unexpected changes to default behavior is confusing.

If I'm not understanding something, I look forward to someone helping me
out.