United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-4638136 stddoclet: Add ability to skip over nav bar for accessibility
JDK-4638136 : stddoclet: Add ability to skip over nav bar for accessibility

Details
Type:
Enhancement
Submit Date:
2002-02-14
Status:
Resolved
Updated Date:
2002-09-28
Project Name:
JDK
Resolved Date:
2002-09-28
Component:
docs
OS:
generic
Sub-Component:
doclet
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
1.4.0
Fixed Versions:
1.4.2 (mantis)

Related Reports

Sub Tasks

Description
Skip navigation links 

  Accessibility Priority 3
  Section 508 1194.22(o)  
      "A method shall be provided that permits users to skip 
       repetitive navigation links."
  W3C Checkpoint 13.6    
       http://www.w3.org/TR/WCAG10-HTML-TECHS/#group-bypass

Note that the Sun Accessibility Program Office says: 
    "These jump-to links can be made invisibl" (sic)
Source: http://solaris.eng/accessibility/508_friendly/preamble.html#1194.22o

When running Dreamweaver test on javadoc, it 
requests a means for speech synthesizers to skip
over the navigation bar in one or more of these ways:

- Include a link that allows users to skip over the 
  set of navigation links. 
- Provide a style sheet that allows users to hide the 
  set of navigation links. 
- Use the HTML 4.01 MAP element to group links, then 
  identify the group with the "title" attribute

In the first choice, the skip link does not need to be visible.  
We can use a hypertext link with no text: <A HREF="#skip"></A>.
The second choice seems rather burdensome for the user, 
as they would need to load that style sheet.
Because the navigation bar is in a table, we could just
mark the table with alternate text, rather than use a 
map.

We could put <MAP> around the table.  This is the example they give:

<BODY>     
<MAP title="Navigation Bar">    
 <P>
 [<A href="#how">Bypass navigation bar</A>]
 [<A href="home.html">Home</A>]
 [<A href="search.html">Search</A>]
 [<A href="new.html">New and highlighted</A>]
 [<A href="sitemap.html">Site map</A>]
 </P>
</MAP>     
<H1><A name="how">How to use our site</A></H1>
<!-- content of page -->     
</BODY>


                                    

Comments
EVALUATION

Needed for 508 accessibility compliance
###@###.### 2002-02-14

I think we have a case that the a"title" attribute
be used in a link to skip over a navigation bar
(in Javadoc HTML pages):

  <a href="#skip" title="Skip navigation bar"></a>

The navigation links are already grouped by way of being
contained in a table. 

This is simpler and more straightforward than combining
<MAP> with a link that is recommended by W3C:

<MAP title="Navigation bar">
   <a href="#skip"></a>
</MAP

source: http://www.w3.org/TR/WCAG10-HTML-TECHS/#group-bypass

It is also simpler than including a one-pixel image simply 
for the sake of using the "alt" attribute:

  <a href="#skip"><img src="pixel.gif" alt="Skip navigation bar"></a>

These facts support this case:

1) 508 accessibility already identifies the "title" attribute as suitable
   for accessibility text for <FRAME> and <MAP> elements. 

   Source: http://www.w3.org/TR/WCAG10-HTML-TECHS/#frame-names 
   Source: http://www.w3.org/TR/WCAG10-HTML-TECHS/#group-bypass

2) The W3C description of the title attribute gives the very example
   of an audio user agent speaking the title information for a link, 
   as follows:

     Audio user agents may speak the title information in a similar 
     context. For example, setting the attribute on a link allows 
     user agents (visual and non-visual) to tell users about the 
     nature of the linked resource:

     ...some text...
     Here's a photo of 
     <A href="http://someplace.com/neatstuff.gif" title="Me scuba diving">
        me scuba diving last summer
     </A>
     ...some more text...

   Source: http://www.w3.org/TR/html401/struct/global.html#adef-title

3) The W3C gives the following example of an empty named anchor tag:

   "Note. User agents should be able to find anchors created by 
    empty A elements, but some fail to do so. For example, some 
    user agents may not find the "empty-anchor" in the following 
    HTML fragment:"

              <A name="empty-anchor"></A>
              <EM>...some HTML...</EM>
              <A href="#empty-anchor">Link to empty anchor</A>

4) I tested this with JAWS reader on Windows, and it works fine.
   The default configuration is to read title attributes in links.
   It says: "Link skip navigation bar" and pauses.  If you press 
   Enter, it skips over the navigation bar and continues speaking. 

###@###.### 2002-08-22

Also note that the following construct, where the content in <a> 
elements is empty. is valid HTML 4.0:

  <a href="#skip" title="Skip navigation bar"></a>
  [navigation bar]
  <a name="skip"></a>

The DTD for the <A> element follows.  The content model includes (&inline;)*,
which means zero or more terms (and -(A) means nested anchor tag disallowed).  
Also, in all cases, "no content" can satisfy #PCDATA.
The inclusion of the attribute "name" or "href" cannot change this content model.

<!ELEMENT A - - (%inline;)* -(A)       -- anchor -->
<!ATTLIST A
  ...
  name        CDATA          #IMPLIED  -- named link end --
  href        %URI;          #IMPLIED  -- URI for linked resource --
  ...
>

<!ENTITY % inline "#PCDATA | %fontstyle; | %phrase; | %special; | %formctrl;">

Source: http://www.w3.org/TR/REC-html40/struct/links.html#edef-A

###@###.### 2002-08-25
                                     
2002-08-25
PUBLIC COMMENTS

.
                                     
2004-06-10
WORK AROUND



Name: dk30142			Date: 02/14/2002



======================================================================
                                     
2004-06-11
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
mantis

FIXED IN:
mantis

INTEGRATED IN:
mantis
mantis-b03


                                     
2004-06-14



Hardware and Software, Engineered to Work Together