Edit comment LC-912 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-935 Next: LC-566

Comment LC-912: Comment Shortname:; Commenter: Giorgio Brajnik <giorgio@dimi.uniud.it> on behalf of University of Udine, Italy; 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:
... all user interface components...: you mean that each single DOM element that has perceivable effects on some user needs to have name and roles defined? eg every <p>?; Related issues: (space separated ids); WG Notes: [TEAMB] BBC: (marking as proposed for Team A Discussion) SC says, "For all user interface components..." Intent says, "The intent of this success criterion is to ensure that Assistive Technologies (AT) can gather information about, activate(or set) and keep up to date on the status of user interface controls in the content.) <previous proposal> {question - answered} @@ update intent to say "component" instead of "control" @@ Repeat failures F48, F42 and F43 in failures for 4.1.2 and retitle ("Failure of 1.3.1 and 4.1.2 due to..."). @@ revise G108 Applicability to read, "Any markup language" @@ Replace the last 2 paragraphs of the G108 description with, "In many cases, the name and role of elements are provided automatically because the user agent or assistive technology is able to relay name and role information to the user based on the markup in use (ex. paragraph marks or links). In some cases, however, it is essential that name and role information be provided by the author. For example, a control may have the ability to provide a name, but only if the author includes the markup necessary for AT to provide it. The role attribute however, may already be provided since it is a standard component with a fixed role that is defined by the markup language. response: In the case of paragraphs, the name and role can be programmatically determined because markup features have been used as defined in the specification and user agents and assistive technologies are capable of relaying this information to the user. We have noted that misuse of markup would be a failure. We have included the following clarifications to help make this clearer: @@ include list of revisions (above). </previous proposal> Discussed in the 03 August 2006 telecon: Resolution: LC-912 referred back to team a to consider adding interactive into the SC: â€œAll <ins>interactive</ins> user interface components..... â€œ http://www.w3.org/WAI/GL/2006/08/03-wai-wcag-minutes.html @@ GV, GL, BB, etc. to review this proposal ===== Discussion from Michael 20 Feb 2007 ===== I have some difficulty with this one, because as a single SC it's so broad. I think we would want to say the role, state, properties, and value of all components should be programatically determined and notification of changes provided. A paragraph, for instance, has a role of "paragraph", a value of its text, and maybe some states and properties. We'd certainly want to require notification of changes if its content/value does change, even though that's not the usual place changes to content are expected to happen. I had to do some looking around to figure out what might have been meant by the term name, and concluded that it's what I call a "label": a human-understandable label/identifier for a component, referred to as "Accessible Name" in accessibility APIs. In the case of form controls in HTML, this would literally be the <label> element. But I don't know what the "name" of a paragraph is, unless it's the same as the value. If name is intended to be same as value in such cases, then although that's weird to me, all we need to do is clarify that in How to Meet 4.1.2. But if that's not what we meant, then I think we've got a situation where parts of 4.1.2 apply to all rendered components, and parts apply only to interactive components. In that case we might need to split the SC in two: remove "name" from the existing SC, and create a new one that says "For interactive user interface components, the name can be programatically determined." Note that if we did that, we'd be moving back in the direction requested in 587 above, and might just as well reinstate 4.1.3 "The label of each user interface control in the Web content that accepts input from the user can be programmatically determined and is explicitly associated with the control." Discussed in the 19 April 2007 telecon: action item 912 sean loretta gregg reopen 912 http://www.w3.org/WAI/GL/2007/04/19-wai-wcag-minutes.html http://digbig.com/4spyc Previous response: @@Change the beginning of 4.1.2 to read "For all <ins>interactive</ins> user interface components" @@Add a note at end of Intent: "Note: only controls with which the user actively interacts are covered by the requirement. While many static objects form part of the user interface, this SC is specific to the accessibility requirements of interactive objects." Surveyed at http://www.w3.org/2002/09/wbs/35422/20070426moremisc/results#xlc912 Discussed in the 03 May 2007 telecon: resolution: accept 912 User interface component as amended http://www.w3.org/WAI/GL/2007/05/03-wai-wcag-minutes.html DONE Add definition: user interface component content that presents an abstraction with which users can interact as a distinct operation Note: Multiple user interface components may be implemented as a single programmatic element. Components here is not tied to programming techniques but rather to what the user perceives as separate controls. Example: An applet has a "control" that can be used to move through content by line or page or random access. Since each of these would need to have a name and be settable independently, they would each be a "user interface component." Discussed in the 10 May 2007 telecon: Updated definition to read: a part of the content that is perceived by users as a single control for a distinct function http://www.w3.org/WAI/GL/2007/05/10-wai-wcag-minutes.html; Resolution: We have added a definition of user interface component to indicate that they present an abstraction with which users can interact. See http://www.w3.org/TR/2007/WD-WCAG20-20070517/#user-interface-componentdef .; (Please make sure the resolution is adapted for public consumption)