Guideline 5. Ensure user control of user interface behavior
5.1 No automatic content focus change (P2)
- Allow configuration so that if a viewport opens without explicit user request, neither its content focus nor its user interface focus automatically becomes the current focus.
Sufficient techniques
- To satisfy provision one of this checkpoint, configuration is preferred, but is not required if the content focus can only ever be moved on explicit user request.
Normative inclusions and exclusions
UAAG2 ISSUES
5.2 Keep viewport on top (P2)
- For graphical user interfaces, allow configuration so that the viewport with the current focus remains "on top" of all other viewports with which it overlaps.
Normative inclusions and exclusions
UAAG2 ISSUES
5.3 Manual viewport open only (P2)
- Allow configuration so that viewports only open on explicit user request.
- When configured per provision one of this checkpoint, instead of opening a viewport automatically, alert the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent).
- Allow the user to close viewports.
Sufficient techniques
- To satisfy provision one of this checkpoint, configuration is preferred, but is not required if viewports can only ever open on explicit user request.
Normative inclusions and exclusions
- If a viewport (e.g., a frame set) contains other viewports, the provisions of this checkpoint only apply to the outermost container viewport.
- User creation of a new viewport (e.g., empty or with a new resource loaded) through the user agent's user interface constitutes an explicit user request.
Note
- Generally, viewports open automatically as the result of instructions in content. See also checkpoint 5.1 (for control over changes of focus when a viewport opens) and checkpoint 6.6 (for programmatic notification of changes to the user interface).
UAAG2 ISSUES
5.4 Selection and focus in viewport (P2)
- Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.
Normative inclusions and exclusions
- Conformance profile labels: Selection
Note
- For example, if users navigating links move to a portion of the document outside a graphical viewport, the viewport should scroll to include the new location of the focus. Or, for users of audio viewports, allow configuration to render the selection or focus immediately after the change.
UAAG2 ISSUES
5.5 Confirm form submission (P2)
- Allow configuration to prompt the user to confirm (or cancel) any form submission.
Sufficient techniques
- Configuration is preferred, but is not required if forms can only ever be submitted on explicit user request.
Normative inclusions and exclusions
Note
- Examples of automatic form submission include: script-driven submission when the user changes the state of a particular form control (e.g., via the pointing device), submission when the user has interacted with all form controls, and submission when an onmouseover or onchange event occurs.
UAAG2 ISSUES
Proposal 5.x Allow configuration to allow users to open viewports with full user interface or author specified user interface. ja: Nov 4 2007
ja: fixes javascript opening windows with no scroll bars, etc.