Edit comment LC-755 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-503 Next: LC-932

Comment LC-755: Comment Shortname:; Commenter: Jim Allan <jimallan@tsbvi.edu> on behalf of UAWG; 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:
Comment (including rationale for any proposed change):

SC 3.2.2 Changing the setting of any form control or field does not automatically cause a change of context (beyond moving to the next field in tab order) unless the authored unit contains instructions before the control that describe the behavior.

<comment>
This is the only SC with a parenthetical clause (beyond moving to the next field in tab order). UAWG believes the clause violates user expectations of form control behavior.

Further, the clause violates UAAG Checkpoint 9.3 Move content focus (P1) http://www.w3.org/TR/2002/REC-UAAG10-20021217/guidelines.html#tech-nav-active

Techniques for checkpoint 9.3

1. Allow the user to move the content focus to any enabled element in the viewport.
2. Allow configuration so that the content focus of a viewport only changes on explicit user request.
3. If the author has not specified a navigation order, allow at least forward sequential navigation, in document order, to each element in the set established by provision one of this checkpoint.

Sufficient techniques

1. To satisfy provision two of this checkpoint, configuration is preferred, but is not required if the content focus only ever changes on explicit user request.

Default behavior is for content focus only ever changes on explicit user request.

Proposed Change:

remove the clause (beyond moving to the next field in tab order); Related issues: LC-968 LC-1299
(space separated ids); WG Notes: [TEAMB] 22-08-06 Team B meeting: considered changing "(beyond moving to the next user interface component in tab order)" to "that is not the expected behavior of that user interface component". Discussed in the 24 August 2006 telecon: Resolution: Accept the proposed changes but include clear discussion that auto next field ok if advance warning is given, make response clear that 504 overcome by events. Loretta will clear up the responses http://www.w3.org/WAI/GL/2006/08/24-wai-wcag-minutes.htm {accept} DONE Delete "(beyond moving to the next user interface component in tab order)" from SC 3.2.2. DONE Add example to How to Meet SC 3.2.2 A form contains fields representing US phone numbers. All of the numbers have a three digit area code followed by a three digit prefix and finally a four digit number, and each part of the phone number is entered into a separate field. When the user completes the entry of one field and enter the first digit of the next field, the focus automatically moves to the next field of the phone number. This behavior of phone fields is described for the user at the beginning of the form. Internal WD updated 25 August.; Resolution: We have accepted your recommendation and removed the parenthetical clause. Note that auto-advance-focus can be an important accessibility aid for the mobility impaired, so it is still permitted, but only if the user has been warned about it as they would be if configured their user agent for this behavior.; (Please make sure the resolution is adapted for public consumption)