Fwd: ATAG 2.0 Inputs

----- Forwarded message from Barry Feigenbaum <feigenba@us.ibm.com> -----
    Date: Mon, 20 Jun 2005 13:21:53 -0500
    From: Barry Feigenbaum <feigenba@us.ibm.com>
Reply-To: Barry Feigenbaum <feigenba@us.ibm.com>
 Subject: ATAG 2.0 Inputs
      To: w3c-wai-au@w3.org

(Jan, copied to you incase it does not go on to the list)

Here is some of the input I owe.

A.1.3 Ensure that the visual presentation is configurable. 

Priority: relative

Rationale: Different authoring tool users have different user interface 
interaction needs (based on a disability or some other usage constraint). 
A inflexible user interface rarely will meet the user interface needs of 
such a diverse population.

belongs???[[[Different web content users also have different needs.  The 
authoring tool needs to generate content for which an accessible 
presentation is possible.]]]

Success Criteria:

1 Dynamically adapt your user interface to conform to the current host 
operating system and/or platform user interface ("the host") and/or 
accessibility settings for visual presentation. This includes, but is not 
limited to, items such as use of colors (including color pallette and 
contrast), use of fonts (including types and sizes), presentation rates 
and delays, language used and locale based formatting. (Priority 1)
2 Support within the authoring tool any configuration of any user 
interface characteristic not covered by 1. Avoid duplication of 
configuration for items controlled by the host.  (Priority 2)
3 Document in an easily accessible location the usage of any configuration 
user interface defined in 2 (Priority 2).
4 Provide accessible alternatives to any visual alerts (such as dynamic 
status lines) provided by the authoring tool (explicitly in the tool or 
through the host). (Priority 1)
[[[5 Assist the user with providing, editing and packaging accessible 
alternatives to any presentation content created using the authoring tool 
(Priority 1)]]]

Note; Criteria 1 of often achieved by simply using user interface controls 
provided by the host with their default settings.   Customizing settings 
in the authoring tool can lead to a less configurable design or require 
that elaborate configuration user interfaces be added to the authoring 
tool.


belongs???[[[, keyboard input sequences, pointer parameters, input 
delays]]]

A.1.4 Ensure that the audio presentation is configurable.

Priority: relative

Rationale: Different authoring tool users have different abilities to 
receive and process audio information (based on a disability or 
environmental conditions).  A inflexible set of audio presentations rarely 
will meet the audio input needs of such a diverse population. 

belongs???[[[Different web content users also have different needs.  The 
authoring tool needs to generate content for which an accessible 
presentation is possible.]]]

Success Criteria:

1 Dynamically adapt your user interface to conform to the current host 
operating system and/or platform user interface ("the host") and/or 
accessibility settings for audio presentation. This includes, but is not 
limited to,  items such as alert sounds (configurations of aspects such as 
tone and tone variation, volume, duration), audio clips and audio mixed 
with video (configuration of aspects such as volume, start, stop/pause and 
playback rate). (Priority 1)
2 Support with in the authoring tool any configuration of any user 
interface characteristic not covered by 1. Avoid duplication of 
configuration for items controlled by the host.  (Priority 2)
3 Document in an easily accessible location the usage of any configuration 
user interface defined in 2 (Priority 2).
4 Provide accessible alternatives to any audio alerts (such as sounding 
the system "bell") provided by the authoring tool (explicitly in the tool 
or through the host). (Priority 1)
[[[5 Assists the user with providing, editing and packaging accessible 
alternatives to any audio content created using the authoring tool 
(Priority 1).]]]

Note; Criteria 1 of often achieved by simply using sound generation user 
interface controls provided by the host with their default settings. 
Customizing settings in the authoring tool itself can lead to a less 
configurable design or require that elaborate configuration user 
interfaces be added to the authoring tool.

A.1.7 Ensure that all user interface labels are clearly associated with 
the controls they are intended to label. [Priority ?] 
Rationale: Assistive technologies often require logical associations 
between labels and controls in addition to whatever visual association may 
be provided.
Note: (covers input fields, table cells, etc.) 

Priority: 1
Success Criteria:
1) The authoring tool should assist the user in creating and validating 
labels and label associations for all controls that cannot provide 
sufficient information to assistive technologies for full presentation of 
the control state (such as role (i.e, type of control), name (i.e., usage 
in the user interface), value, focusable, enabled) to the user.
2) For web content types that support explicit labeling relationships, the 
authoring tool should assist the user in creating these relationships.
Techniques: 
1 In many GUI Toolkits, an association is automatically made between a 
label and the control (aka widget) that follows it (follows may mean in 
screen coordinates (i.e., to the right of, or below) or be set by order of 
creation/addition to the containing control). If no other mechanism (see 
2) is provided, the authoring tool should assist the user to place 
controls in the proper locations to enable the establishment of  these 
relationships.
2 In hosts that provide API to establish explicit relationships between 
controls, this API should be used; no dependence should be made on any 
automatic associations. The authoring tool should assist the user in 
creating and/or editing these explicit relationships.


Barry A. Feigenbaum, Ph. D.
Worldwide Accessibility Center - IBM Research
www.ibm.com/able, 
w3.austin.ibm.com/~snsinfo 
voice 512-838-4763/tl678-4763
fax 512-838-9367/0330
cell 512-799-9182
feigenba@us.ibm.com
Mailstop 904/5F-021
11400 Burnet Rd., Austin TX
W3C AUWG Representative
IBM Club Representative
IEB Member
QSE Development TopGun

Sun Certified Java Programmer, Developer & Architect 
IBM Certified XML Developer; OOAD w/UML

This message sent with 100% recycled electrons
----- End forwarded message -----