Guideline 9. Design for device-independence
Use features that enable activation of page elements via
a variety of input devices.
Web sites should be accessible my more than one type of
input device, nor should they cater to any specific type
or group of input devices. They should be
device-independent allowing for a general and wide range
of input devices (i.e. keyboard, mouse, screen reader,
digital pen, touch ;screen display, etc...). Content
developers should create a logical order for accessing
event handlers and ensure that any element that has its
own interface can be operated device-independently.
Checkpoints:
9.1 Provide client-side image maps instead of server-side
image maps except where the regions cannot be defined with
an available geometric shape. [Priority 1] Refer also to
checkpoint 1.1, checkpoint 1.2, and checkpoint 1.5.
9.2 Ensure that any element that has its own interface can
be operated in a device-independent manner. [Priority 2]
Refer to the definition of device independence and to
guideline 8.
9.3 For scripts, specify logical event handlers rather than
device-dependent event handlers. [Priority 2]
9.4 Create a logical tab order through links, form
controls, and objects. [Priority 3] For example, in HTML,
specify tab order via the "tabindex" attribute or ensure a
logical page design.
9.5 Provide keyboard shortcuts to important links
(including those in client-side image maps), form controls,
and groups of form controls. [Priority 3] For example, in
HTML, specify shortcuts via the "accesskey" attribute.
Source:http://www.w3.org/TR/WCAG10/#gl-device-independence
