accessability of javascript

[yawnmoth]

I'd like to make a webpage such that when I move my mouse over a link,
description text appears below the link. eg. maybe make an input
type="text" field below the links and do something like
onhover="document.something.value='whatever'".

I'd also like to make another part of the page only show form elements
when a drop down menu is set to a particular item. I can do this
easily enough with display: none.

Unfortunately, I'm not sure how accessable doing stuff like this is.
In fact, it seems like javascript and truely accessable websites (eg.
accessable even to those who are blind and need screenreaders) just
don't go together. Is this correct or is there some way to make a
website both interactive (well, sorta) and accessable that I'm not
aware of?

 

[RobG]

I'd like to make a webpage such that when I move my mouse over a link,
description text appears below the link. eg. maybe make an input
type="text" field below the links and do something like
onhover="document.something.value='whatever'".

Search the archives for 'tooltip', there are many posts on the subject.

I'd also like to make another part of the page only show form elements
when a drop down menu is set to a particular item. I can do this
easily enough with display: none.

Unfortunately, I'm not sure how accessable doing stuff like this is.
In fact, it seems like javascript and truely accessable websites (eg.
accessable even to those who are blind and need screenreaders) just
don't go together. Is this correct or is there some way to make a
website both interactive (well, sorta) and accessable that I'm not
aware of?

'JavaScript' and 'accessible' aren't mutually exclusive.

Make the website fully accessible first, then add script second to
enhance it for those who can take advantage of the scripting support
provided.

 

[Richard Cornford]

... such that when I move my mouse over ...

Unfortunately, I'm not sure how accessable doing
stuff like this is.

<snip>

One of the things that you will have to think about when creating
accessible web pages is how the user may be interacting with their
computer. They may not be using a mouse at all (through choice or an
inability to successfully manipulate one).

Richard.

 

[yawnmoth]

<snip>
'JavaScript' and 'accessible' aren't mutually exclusive.

Make the website fully accessible first, then add script second to
enhance it for those who can take advantage of the scripting support
provided.

Would a good rule of thumb maybe be that if the website can be used
without javascript than it is accessable? Or do screenreaders run
javascript?

 

[Thomas 'PointedEars' Lahn]

Would a good rule of thumb maybe be that if the website can be used
without javascript than it is accessable?

There are other factors to accessibility, but that would be a good
indicator.

Or do screenreaders run javascript?

Maybe.


PointedEars

 

[Thomas 'PointedEars' Lahn]

Why not just use the title attribute? Simpler and accessible.
http://www.w3.org/TR/html4/struct/links.html#h-12.1.4

It is simpler. However, its limitations are that it requires a pointing
device and the displayed tooltip text length is limited, if the attribute
value is even displayed as a tooltip. So I suggest to use both to be
pretty sure.


PointedEars

 

[Randy Webb]

Thomas 'PointedEars' Lahn said the following on 5/22/2006 11:48 AM:

It is simpler. However, its limitations are that it requires a pointing
device and the displayed tooltip text length is limited, if the attribute
value is even displayed as a tooltip. So I suggest to use both to be
pretty sure.

And even that won't insure that it gets displayed.

 

[VK]

Thomas 'PointedEars' Lahn said the following on 5/22/2006 11:48 AM:

And even that won't insure that it gets displayed.

I guess he's coming, the fate man of c.l.j. : deaf and blind user on
Lynx )

:-|
JavaScript was created to /improve/ accessibility so I'm finding rather
ridiculous to put them into some kind of opposition.
That again like with "cross browser support": without strictly defining
what browsers are included (and excluding any others) they just taking
a broad range of exeptions from wherever - whatever sounds stronger at
this given moment.

 

[Randy Webb]

VK said the following on 5/22/2006 12:29 PM:

I guess he's coming, the fate man of c.l.j. : deaf and blind user on
Lynx )

No, not a deaf and blind user on Lynx, just a user that has a cellphone
with a browser but no mouse and no scripting.

:-|
JavaScript was created to /improve/ accessibility so I'm finding rather
ridiculous to put them into some kind of opposition.

I never said differently.

That again like with "cross browser support": without strictly defining
what browsers are included (and excluding any others) they just taking
a broad range of exeptions from wherever - whatever sounds stronger at
this given moment.

You should spend about a week of reading mine and TL's posts and then
you might begin to understand..

 

[Thomas 'PointedEars' Lahn]

Thomas 'PointedEars' Lahn said the following on 5/22/2006 11:48 AM:

And even that won't insure that it gets displayed.

It is likely, though, for the corresponding meaning of "to display". The
value of the `title' attribute may be not displayed as a tooltip, but a
reasonable UA that conforms to accessibility standards should allow its
users to "see" the `title' attribute value. Because, for example, there
are accessibility standards that _require_ the `table' element's `title'
attribute to be set for conformance, so that users can "see" at a glance
what the table is about.


PointedEars

 

[Randy Webb]

Thomas 'PointedEars' Lahn said the following on 5/22/2006 12:54 PM:

It is likely, though, for the corresponding meaning of "to display". The
value of the `title' attribute may be not displayed as a tooltip, but a
reasonable UA that conforms to accessibility standards should allow its
users to "see" the `title' attribute value.

Then that reasonable UA should display the title attribute when focused
by means other than a mouse. And I don't want to get into an
argument/discussion about what is "focused" and what isn't.

How does a UA know to display the title attribute if there is no mouse
pointer?

Because, for example, there are accessibility standards that _require_ the
`table' element's `title' attribute to be set for conformance, so that users
can "see" at a glance what the table is about.

And every UA follows every standard? I do not even know of one, much
less more, that follow all the standards.

 

[Thomas 'PointedEars' Lahn]

Thomas 'PointedEars' Lahn said the following on 5/22/2006 12:54 PM:

Thomas 'PointedEars' Lahn said the following on 5/22/2006 11:48 AM:
Warren Sarle wrote:
[display description of a hyperlink as content of another element]
Why not just use the title attribute? Simpler and accessible.
http://www.w3.org/TR/html4/struct/links.html#h-12.1.4
It is simpler. However, its limitations are that it requires a
pointing device and the displayed tooltip text length is limited, if
the attribute value is even displayed as a tooltip. So I suggest to
use both to be pretty sure.
And even that won't insure that it gets displayed.

It is likely, though, for the corresponding meaning of "to display". The
value of the `title' attribute may be not displayed as a tooltip, but a
reasonable UA that conforms to accessibility standards should allow its ^^^^^^^^^^^^^^^^
users to "see" the `title' attribute value.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Then that reasonable UA should display the title attribute when focused
by means other than a mouse.

That is what I said.

[...]
How does a UA know to display the title attribute if there is no mouse
pointer?

The `title' attribute _value_ can be displayed when the corresponding
element is focused. That requires that the element can be focused somehow
without a pointing device.

And every UA follows every standard?

Wrong question, and no. However, a UA that does not follow this part of
accessibility standards, probably is not used (by handicapped people).

I do not even know of one, much less more, that follow all the standards.

You are confusing language/API standards and accessibility standards.
The latter are even enforced by national legislation.


PointedEars