W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2007

TOCs and accessibility

From: Jesper Tverskov <jesper@tverskov.dk>
Date: Tue, 8 May 2007 16:22:52 +0200
Message-ID: <852456e80705080722r3d8e4e78sd2740994e295974@mail.gmail.com>
To: w3c-wai-ig@w3.org

Hi list

Making research for my tutorial, "TOC for XHTML with XSLT",
http://www.xmlplease.com/tocxhtml, I couldn't help but notice that
most of the TOCs for web documents are far from Best Practice. See my
article: "The TOC freak show at W3C and OASIS",

Let us focus on the most important accessibility issue: the IE focus bug.

The IE focus bug is mostly considered a "skip navigation" issue. It is
often forgotten that the bug is also with us in documents having a TOC
and if cross-references are used or always when fragment identifiers
are used.

Let us take the spec for WCAG 1.0 as example,
http://www.w3.org/TR/WCAG10/. The document has a huge TOC and also
very many cross-references. If it is true, and I believe it to be,
that the TOC and the cross-references must be considered indispensable
for navigating the spec in a useful manner, these features must also
work for keyboard users.

Since tabbing to the next link doesn't work when TOC and
cross-references are used in Internet Explorer, the spec of WCAG 1.0,
claiming Triple-A accessibility, must be considered so inaccessible
that it does not live up to any acceptable accessibility level. The
same is the case for probably all major specs and documents at W3C
including the draft for WCAG 2.0, http://www.w3.org/TR/WCAG20/.

How can we ever discuss the finer details of accessibility and of WCAG
2.0 if even the accessibility specs are not accessible for keyboard

Jesper Tverskov

Received on Tuesday, 8 May 2007 14:22:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:30 UTC