Edit comment LC-627 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-864 Next: LC-562

Comment LC-627: Comment Shortname:; Commenter: Lisa Seeman 2 <lisa@ubaccess.com> on behalf of Invited expert at W3C, UB access; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/0137.html
http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/att-0137/wcagform_ch2_.html

Comment (including rationale for any proposed change):

sections of content need titles to be able to navigate through a page.
This is particularly true of many AJAX sites that have multiple regions. The regions of a page can change at different rates due to either user actions or asyncrones updates. The user may need to toggle between form controls to results, and updates.

Even in simpler content knowing that a table has a navigation function is hugely usefully even when accessibility is not completely broken.

Proposed Change:

Add level one success criteria
Blocks of content that become updated should be uniquely titled or it's role can be programaticaly determined

When multiple blocks of content in a web unit have the same role they should be uniquely titles

Blocks of content that perform a common task should be titles or its role can be programaticaly determined

success criteria 2.4.1 is no longer needed; Related issues: LC-563
(space separated ids); WG Notes: [TEAMC] [] In responding to this be sure to respond to the last line as well [Becky] I don't think we can make this a level 1 success criterion since it can't be supported today in HTML and current user agents. User Agents and AT do support titles on certain elements (tables, frames, etc) but they do not currently support titles on divs. I don't think we can require folks to program HTML in a certain way - using tables or frames (especially when we want people to stop using tables for layout). While we don't want to tie the guidelines only to current technology - the current guidelines do not prohibit additional techniques. I do think we might consider the first new SC request (Blocks of content that become updated should be uniquely titled or it's role can be programaticaly determined)as a level 3 SC at this point. I think SC 2.4.3 generally covers the request for titles - although it doesn't require unique titles. I also don't see how adding these 3 new SC would eliminate the need for 2.4.1? Just because things are titled, it doesn't mean that UA or AT will support the type of navigation that 2.4.1 is requiring. Thus, I think we should consider a L3 SC for Blocks of content that become updated should be uniquely titled or its role can be programmatically determined. There could be an few sufficient techniques: Using titled frames to organize content that is updated Using tables to organize content (although this could go against not using tables for layout) We could perhaps ask Lisa for more ideas. An advisory technique for using DHTML roles to mark updated content. Discussed in the 01 March 2007 telecon: resolution: Team C to write up as SC under 2.4 http://www.w3.org/WAI/GL/2007/03/01-wai-wcag-minutes.html Team C to consider comments at http://www.w3.org/2002/09/wbs/35422/20070301-teamc/results#x627 Discussed in the 19 April 2007 telecon: accepted by unanimous consent http://www.w3.org/WAI/GL/2007/04/19-wai-wcag-minutes.html {partial-accept} DONE make ARIA Techniques their own category (relates to 630 and 632, also SCR26) DONE Create new L3 SC under 2.4 "Where content is organized into sections, the sections are indicated with headings." DONE Create sufficient HTML technique "Organizing a page using headers" DONE Create sufficient HTML technique "Using titled frames to organize content that is updated" DONE Create advisory ARIA technique "Using the 'live' property to mark live regions" Internal WD updated 20 April 2007. {partial accept} Discussed in the 10 May 2007 telecon: Accepted by Unanimous Consent http://www.w3.org/WAI/GL/2007/05/10-wai-wcag-minutes.html; Resolution: The WCAG WG did not create a success criterion specific to live regions. However SC 4.1.2 was modified to require the general case that roles, states, properties, and values be programmatically determined. In addition, the ability to navigate easily to such regions is an important point and related to other needs as well. Therefore, we created a new Level AAA success criterion in GL 2.4 "2.4.9 Section Headings: Where content is organized into sections, the sections are indicated with headings." Various ways of conforming to this success criterion would exist, including the suggestion to provide headers for live regions as well as any other meaningful section of content. The technique on 'live regions' is advisory at this time because the technology has not been released yet.; (Please make sure the resolution is adapted for public consumption)