W3C

Edit comment LC-624 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-531 Next: LC-663

Comment LC-624
:
Commenter: Lisa Seeman 2 <lisa@ubaccess.com> on behalf of Invited expert at W3C, UB access

or
Resolution status:

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 proposed change):

Interfaces become inoperable when one of the following brake:

1. Each element or widget is marked with full and corrected semantics that fully describes it's behavior Note this is more then information and structure can be separated from presentation .This includes creating enabled javascripted widgets that the Assistive Technology does not know what it is, what states are supported and how it maps to the operating system API. If non exists (like a tree item that can expand to a sub tree when you click on it) Then you may need to add a technology, such as xforms, XHTML 2 Roles

2. The relationships between elements and groups are known. Again, this is more then I see supported by navigation Success criteria. What form element controls what AJAX operated section is a good example of a relationship

3. States, properties, and relationships are valid for each elements behavior and are accessible via the DOM. For example if clicking on a tree item makes it expand or collapses, then it's state (such as expanded) needs to be accessible via the Document Object module Via an attribute that can be understood by assistive technology..

4. There is an element having the correct input focus. This is different to just being keyboard navigatable

Proposed Change:

Add success criteria at level 1 along the lines of:

1, The supported behavior of each element and widget can be programaticaly determined.

2, The relationships between elements and groups of elements can be programaticaly determined.

3, States, properties, and relationships are valid for each elements behavior can be programaticaly determined.

4, There is consistently an element having the correct input focus.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 624.html,v 1.1 2017/08/11 06:41:43 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org