RE: Discussion Issues with Landmark ARIA Documentation

Thomas,

 

3. That is normal Jaws behavior. For automatic Jaws "title" announcement
of a div (I found out experimentally), you have to 

 

1) focus div explicitly

2) set in the focus event the title attribute text explicitly

3) this will trigger Jaws to speak the title attribute on focus

 

In addition, I think Jaws will announce landmarks in its Virtual Mode
but I would like to know if this is also true when role=application
(that does automatic Jaws mode switching) is set for the body of the
page.

 

- Stefan

 

 

From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of Thomas Logan
Sent: Montag, 10. November 2008 14:07
To: wai-xtech@w3.org
Subject: Discussion Issues with Landmark ARIA Documentation

 

I tried implementing ARIA landmarks for codetalks.org to create a real
world example.  Here are a few issues for discussion that came up.

 

1.       W3C document says landmark contentinfo applies to immediate
ancestor whose role is not presentation.   If you take the code talks
page this is not valid.  The footer is a child of something called
globalWrapper.  The contentinfo is actually related to the node with
id=content.  I think it would be more logical and accurate to state that
contentinfo corresponds to content that is marked with role=main.  Is
there any other scenario where the contentinfo would not be referring to
the main content on the page?

2.       The Best Practices document says that every region MUST have a
label.  I think contentinfo, search and navigation landmarks should only
be required to be uniquely identified if there is more than one.  This
would be similar to Section 508 1194.22 (i) that requires frames to be
titled to facilitate identification and navigation.  If there is only
one landmark contentinfo, search, or navigation then it is uniquely
labeled and navigable and should not require additional work.  

 

3.       The Best Practices document shows setting a div tag with a
title attribute to identify the element.   Is this equivalent to
providing a header?  Current testing with JAWS does not show support for
reading the title attribute of a div.  

 

Code example 
<div role="complementary" title="weather">  

 

4.       The BP document also shows using aria-labelledby on an element
to point to the header of a region.  I don't understand why the header
content can't be required to be the first element under the region.  
Code example from document
<p role="main" aria-labelledby="hdr1"> 
<div role="header" id="hdr1">  
Top News Stories
</div>
</p> 

Code example from web today
<p role="main">
<h2>Top News Stories</h2>
</p>

Using the existing html markup seems more intuitive.  I'm also not sure
why the example in the document uses <p> tag instead of <div>  What am I
missing?

 

Reference codetalks.org Website

http://wiki.codetalks.org/wiki/index.php/Main_Page

Note you must be logged out of the site to use the landmarks.  Only the
theme for non logged in users currently has role support

 

Reference ARIA Best Practices

http://www.w3.org/WAI/PF/aria-practices/