Guideline
2.1 Allow users to operate all functionality device-independently
Level 1 Success Criteria for Guideline 2.1
- All
of the interactive functionality of the content is operable through a keyboard interface. [I]
Note:
This includes author-provided accessibility features.
Note:
Other interfaces (such as a mouse) can be provided in addition to keyboard operation.
Note:
Refer to guideline 4.2 for information regarding user agent support.
Level 2 Success Criteria for Guideline 2.1
- Where
possible for the chosen technology, use device-independent event handlers.
[I]
Guideline 2.1 (keyboard-operation) Issues
Changes
The proposal only includes our ideas for the guideline text and the success criteria.
We will include proposals for the benefits and examples once the proposal for
the guideline and success criteria has been discussed.
Changed wording
- Guideline text: changed from "Make
all functionality operable via a keyboard or a keyboard interface" to "Allow users to operate all functionality
device-independently"
- lvl 1 SC 1: changed from "All of the functionality of the content, where the
functionality or its outcome can be described in a sentence, is operable
through a keyboard or keyboard interface. " to "All of the functionality of
the content is operable through a keyboard or keyboard interface. "
Rationale: A lot of people had problems with the concept 'described in a
sentence' and did not understand what it means. In practice, this means everyone
will think you need to make everything keyboard operable at level 1, so why
not just say so. During our analysis we could not think of any functionality
that could not be described
in a
sentence
so we
deleted
the
entire subsentence. Unless we find some real-world examples of content where
requiring keyboard operability would be an undue burden at level 1, I propose
to go with the shorter, simpler version.
Also, "keyboard or keyboard interface" is redundant since a keyboard is an
example of a device that uses a keyboard interface. We propose to drop the
'keyboard or'.
We added the word 'interactive' to make sure that we do not require keyboard
operability for functionality that does not require user input.
- Lvl 2 SC 1: Changed from "Wherever a choice between input device event handlers
is available and supported, the more abstract event is used. " to "Where possible for the chosen technology, use device-independent event handlers."
Deleted SC
- Deleted lvl 3 SC 1: "All of the functionality of
the content is operable through a keyboard or keyboard interface." because
that's the proposed formulation for level 1.
New SC
- Added level 3 SC: "Provide single-key
bindings to frequently-used functionality.". The fact that there are user-agent issues for accesskey support
in HTML does not mean providing shortcut keys isn't a good idea in general.
If properly supported by the user agents, it can be a great help.
- Added level 3 SC: "All of the functionality of the content is operable through
voice commands." Voice commands can do more than just simulate keystrokes so it isn't covered
by the level 1 item. We're not sure whether this belongs in the SC or in the
guide and seek input on that
from
the group.
New definitions
interactive functionality:Interactive functionality is a purpose or intended effect of the content that requires input from the user. This may include
on demand presentation of information, data collection as a result of a query, securing a response from the
user, providing user experience, linking to other content, testing, confirmation,
purchasing, etc.
single key binding: A single-key binding is one where a single key press performs
the task, with zero modifier keys.
[This formulation was taken from UAAG 1.0]
voice command: A voice command is a spoken instruction.