EASI Archives

Equal Access to Software & Information: (distribution list)

EASI@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
"* EASI: Equal Access to Software & Information" <[log in to unmask]>
X-To:
Alan Cantor <[log in to unmask]>
Date:
Thu, 22 Jul 2004 14:26:11 -0700
Reply-To:
"* EASI: Equal Access to Software & Information" <[log in to unmask]>
Subject:
From:
Dan Comden <[log in to unmask]>
In-Reply-To:
Content-Type:
TEXT/PLAIN; charset=US-ASCII
MIME-Version:
1.0
Parts/Attachments:
TEXT/PLAIN (24 lines)
Keyboard accessibility in other browsers is a problem as well.

Agreed that there is a continuum of accessibility for text that is related
to an indivdual's needs. My take on the original question was creation of
alt text for academic purposes -- that is a very targeted situation where
the consumer/requestor has some input concerning the process and product.

For Web-based resources, PDF format should only be done after accessible
HTML has been created.

-*- Dan

On Thu, 22 Jul 2004, Alan Cantor wrote:

> Accessibility is not binary. There are degrees of accessibility. A PDF
> document may be excellent for a person with low-vision, but terrible for a
> screen reader user.
>
> Here's another consideration: when PDF files are opened in Internet Explorer,
> keyboard-only navigation goes to pot. Alt + left arrow no longer goes back to
> the previous page, and choosing items from menus using the keyboard becomes
> difficult or impossible. (I am not sure what happens in other browsers.)
>

ATOM RSS1 RSS2