15. Site Behaviour
15.1 Pop-ups and other windows appearing
Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. If a window has to be spawned, then the user must be informed (giving them an option to cancel), or the option given to the user asking if they
- wish to open in the same browser form, or,
- pull up a new form.
Guide to this standard
This standard also includes the non-allowance of scripting-based pop-ups.
This standard covers the W3C WAI checkpoint 10.1 for NZ government agencies.
Rationale for this standard
Many users find pop-ups disruptive, annoying and frustrating, as they can feel they are not in control of navigation within the site. It can also cause them to become disorientated with the site.
The annoyance and frustration factor is further increased when site history links are not preserved, preventing a return to the previous page.
Pop-ups are also problematic for screen readers, as the focus is suddenly removed with little or no notice.
15.2 Unique interfacing and device-independence
Ensure that any element that has its own interface can be operated in a device-independent manner and is also directly accessible or compatible with assistive technologies.
Guide to this standard
This standard covers the W3C WAI checkpoints 8.1 and 9.2 for NZ government agencies.
Related Standard
13.2 - Alternative event handlers and device dependence
Rationale for this standard
A mouse as a navigation tool is a common example. Not all users utilise a mouse for navigational purposes. A mouse is a device that assists navigation, but not the only one. Users who suffer from one or more impairments may use other devices for navigation assistance. Correspondingly, if events catered for assistive devices and user interfaces are device-specific (such as “drag and drop” with a mouse), or alternative events not additionally catered for, they may not be recognised by other devices substituted for equivalent functionality.
15.3 Keyboard shortcuts
Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.
Guide to this standard
This standard covers the W3C WAI checkpoint 9.5 (http://www.w3.org/TR/WCAG10-TECHS/#tech-keyboard-shortcuts) for NZ government agencies.
Related Standard
8.4 – Navigational Access Keys defined for NZ Government web sites
Rationale for this standard
Not all users utilise a mouse or other “pointing” device for navigational purposes and rely on “tabbing” (usually via the “TAB” key) to move the cursor. Of further assistance to all users, not just those relying on the keyboard alone, keys that duplicate a navigation link to common or expected parts of a web site assist economy and efficiency.
15.4 Skipping over long lists of unwanted links
Provide a way for the user to skip over long lists of unwanted links.
Guide to this standard
Skip links above navigation links are the most common method of this.
This standard covers the W3C WAI checkpoint 13.6 for NZ government agencies.
Related Standard
8.4 - Navigational Access Keys defined for NZ Government web sites.
Rationale for this standard
Some screen readers read everything including links. Users of such assistive technology may wish to avoid a multitude of links. Skip links enable this.
[ Previous | Next ]
