W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2008

Re: UAAG2: Ideas for 10.1

From: David Poehlman <poehlman1@comcast.net>
Date: Thu, 7 Feb 2008 11:48:14 -0500
Message-ID: <001801c869a9$3bd7d850$0601a8c0@HANDS>
To: "Jan Richards" <jan.richards@utoronto.ca>, "WAI-UA list" <w3c-wai-ua@w3.org>

+1 but I'm interested in further discussion.

----- Original Message ----- 
From: "Jan Richards" <jan.richards@utoronto.ca>
To: "WAI-UA list" <w3c-wai-ua@w3.org>
Sent: Thursday, February 07, 2008 11:45 AM
Subject: Re: UAAG2: Ideas for 10.1



REVISED AFTER JAN 31 CALL

Please Note:
1. We haven't talked about how we are going to call out what the base
browser has to do versus the assistive technologies...what do people
think of something like the "BASE_UA" label shown here for this?


X.Y Provide access to relationship information

Level A

(BASE_UA) 1. Make explicitly-defined relationships in the content (e.g.,
labeledby, describedby, which table header?, etc.) available
programmatically.
2. Allow the user to access information from explicitly-defined
relationships in the content (e.g., label, description, table header, etc.).
3. For content in a hierarchy (e.g., tree node, nested frame), allow the
user to view the path of nodes leading from the root to the content.

Level AA

N/A

Level AAA

N/A


Thoughts?

Cheers,
Jan




Jan Richards wrote:
>
> As per my action item from last week
> (http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JanMar/0022.html):
>
> I don't think this is fully worked out, but it might make sense to pair
> it with our reworded "2.3 Render Conditional Content":
> http://www.w3.org/WAI/UA/2008/WD-UAAG20-20080110/WD-UAAG20-20080110.html#tech-conditional-content)
>
>
> POTENTIAL NEW WORDING:
>
> X.Y Provide associated orientation information
>
> Level A
>
> 1. For content in a hierarchy (e.g., nested frame), provide access to
> the path of nodes leading from the root.
>
> 2. For content in a graphical layout (e.g., table cell, map location)
> allow the user to access information about associations (e.g., relevant
> table header(s), map coordinates).
>
> Level AA
>
> N/A
>
> Level AAA
>
> N/A
>
> ==========================================================
> CURRENT WORDING:
>
> 10.1 Associate table cells and headers (P1)
>
> 1. For graphical user agents that render tables, for each table cell,
> allow the user to view associated header information.
>
>
>

-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information Studies
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896
Received on Thursday, 7 February 2008 16:48:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:53 GMT