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
Content-Type:
text/plain
Sender:
"* EASI: Equal Access to Software & Information" <[log in to unmask]>
Subject:
From:
"Senge, Jeff" <[log in to unmask]>
Date:
Fri, 4 May 2001 11:16:27 -0700
MIME-Version:
1.0
X-To:
"Powell, Jim" <[log in to unmask]>
Reply-To:
"* EASI: Equal Access to Software & Information" <[log in to unmask]>
Parts/Attachments:
text/plain (80 lines)
Hi Jim,

I thought this might be of interest to you...

Jeff

> ----------
> From:         Richard Jones[SMTP:[log in to unmask]]
> Reply To:     * EASI: Equal Access to Software & Information
> Sent:         Friday, May 04, 2001 8:37 AM
> To:   [log in to unmask]
> Subject:      Re: acronym and abbr tags don't seem to work in JAWS
>
> We are just at the beginning of web accessibility.  With 508 these
> attributes will become standard place.  What we are seeing is the
> developmental work that must be done before a tag can be accepted by
> vendors.  You might want to look at Amaya.  Amaya is the W3C test bench
> web browser.  I can't guarantee that all proposed tags are supported in
> Amaya, but it is a good place to start.
>
> Richard Jones
> Assistant Director
> Disability Resources for Students
> Arizona State University, Main
> 480-965-1234
>
>  -----Original Message-----
> From:   Rosemary Ernst [ mailto:[log in to unmask]]
> Sent:   Friday, May 04, 2001 8:31 AM
> To:     [log in to unmask]
> Subject:        Re: acronym and abbr tags don't seem to work in JAWS
>
> On Thu, 3 May 2001 15:16:14 -0600, Jim Rebman <[log in to unmask]>
> wrote:
>
> >>Hmmm... So there is not even one browser that can read these tags?? I'm
> >>checking with IE 5.5.
> >
> >The Opera browser may support one or more of these tags (I'm fairly sure
> it
> >supports longdesc).  I really question how useful any tag that isn't
> >universally supported is, and I wish either W3C or the vendors would come
>
> >to some kind of resolution of this issue soon, but that is probably just
> a
> >pipe dream.
> >
> >JAWS and IE 5.5 is a powerful and popular combination (I use it myself
> much
> >of the time), but to test with only this combination will almost
> certainly
> >lead to undetected problems with other screen reader/browser
> combinations.
> >
> >-- Jim
> >
> >------------------------------
> >James A. Rebman
> >
> >Cognitive Levers Project
> >Center for Life-Long Learning and Design
> >Department of Computer Science
> >University of Colorado, Boulder
> >
> >"In times of change, the learners will inherit the earth while the
> learned
> >will find themselves beautifully equipped for a world that no longer
> exists."
> >
> >- Eric Hoffer
>
> Just to clarify, I'm not building for one scenario or browser. I am just
> continually astounded at the W3C's persistence in putting forth design
> standards that are not functional. It seems like the cart before the horse
>
> to me. As a web designer, I'm supposed to use this new language they made
> up, just hoping someone will be able to understand it some day??!!
>
>

ATOM RSS1 RSS2