E-mail List Archives

RE: Accessibility Observations

for

From: Paul Bohman
Date: Feb 26, 2002 8:12PM


With CSS positioning, the tab order will be the same as the reading (or
listening) order. I added some links to my test files so that you can
see how the tab order changes when the div tags are rearranged. (Note:
the links are dummy links that don't go anywhere.)

The div tags work fine in Internet Explorer and Opera. In Netscape (both
4.x and 6.x) the particular kind of style that I used in these files
causes the keyboard accessibility to fail. This is a Netscape bug which
has been around for a while. The truth is that Netscape has never been
very keyboard-friendly. Most people who depend upon keyboard use will be
using a non-Netscape browser.

Here are the links to the test files again:
http://www.webaim.org/paul/css-linearization
http://www.webaim.org/paul/css-linearization2

Paul Bohman
Technology Coordinator
WebAIM (Web Accessibility in Mind)
www.webaim.org
Center for Persons with Disabilities
www.cpd.usu.edu
Utah State University
www.usu.edu




-----Original Message-----

Actually though looking jumbled, this might be another way to put in the
navigation skip without having to code in the skippable links. These
would be heard last, and then if the screen readers or browser readers
read this order the same way.... if there are links in the content or
side box areas would those be hit in the screen reader order with the
tabbing key?

I am curious and will tab work with layers and divisions. I just tested
a page in IE and seems to work well however, same page in opera or even
older nn may not work well on keyboard tabbing of links on pages with
layers or z index.

would having the links in the top most layer matter, or make the
difference... or do these links have to be coded in another way?

Seems they may get trapped in some deliveries.

holly




----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/