- From: Becky Gibson <gibsonb@us.ibm.com>
- Date: Mon, 5 Jun 2006 07:30:02 -0400
- To: public-wcag-teamc@w3.org
comment #624 [1] is requesting additional level 1 success criteria to address the following: 1, The supported behavior of each element and widget can be programmatically determined. 2, The relationships between elements and groups of elements can be programmatically determined. 3, States, properties, and relationships are valid for each elements behavior can be programmatically determined. 4, There is consistently an element having the correct input focus. I believe that items 1 and 3 are covered by SC 4. 4.1.2 For all user interface components, the name and role can be programmatically determined, values that can be set by the user can be programmatically set, and notification of changes to these items is available to user agents, including assistive technologies. Item 2 is covered by 1.3.1: 1.3.1 Information and relationships conveyed through presentation can be programmatically determined, and notification of changes to these is available to user agents, including assistive technologies. I don't think that it is legitimate to have a level one success criteria about always have an element with input focus. There may be cases where the content does not have any input focus and I think that this is covered by 2.1 (although Lisa disagrees). Also, I don't think there is any way to enforce this? A mouse user can click anywhere on the page or make a selection which will change focus. I don't know of a way to maintain input focus while also allowing selection focus? Here is a proposed response - It could probably use some additional word-smithing. Resolution: reject Response: The working group believes that your concerns for additional level one success criterion have already been met with existing criteria. Success criterion 4.1.2 covers the supported behavior of each element and the states properties and relationships of elements and requires that they be programmatically determinable. The relationships between elements is covered by success criterion 1.3.1. Both of these are level 1 success criterion. We also do not believe that there should be a requirement for always requiring an element with input focus. There is often content which requires no input focus. Additionally, the user must be allowed to change focus to make selections within the content. [1] http://www.w3.org/WAI/GL/WCAG20/issue-tracking/viewdata_all.php#624 Becky Gibson Web Accessibility Architect IBM Emerging Internet Technologies 5 Technology Park Drive Westford, MA 01886 Voice: 978 399-6101; t/l 333-6101 Email: gibsonb@us.ibm.com
Received on Monday, 5 June 2006 11:30:19 UTC