-
Notifications
You must be signed in to change notification settings - Fork 41
Input/operation user needs statements review #726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
tamsinewing555
wants to merge
7
commits into
add-user-needs
Choose a base branch
from
user-needs-input-operation
base: add-user-needs
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 2 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
c78f9e6
Guideline 2.4.1 Keyboard interface input: Update user needs statements
tamsinewing555 ace7ce1
Guideline 2.4.2 Physical or cognitive effort when using keyboard: Upd…
tamsinewing555 be87230
Guideline 2.4.3 Pointer input: Update user needs statements
tamsinewing555 1bbaaf1
Guideline 2.4.4 Speech and voice input: Update user needs statements
tamsinewing555 2c85be8
Guideline 2.4.5 Input operation: Update user needs statements
tamsinewing555 1d1cc1b
Guideline 2.4.6 Authentication: Update user needs statements
tamsinewing555 9600a98
Remove space
tamsinewing555 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
46 changes: 22 additions & 24 deletions
46
informative/guidelines/input-operation/keyboard-interface-input.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,26 +1,24 @@ | ||
| ## User needs | ||
|
|
||
| * As a user of assistive technology, I need my keyboard commands to remain consistent. | ||
| * As a keyboard user, the complexity and number of input commands required to complete a task should be comparable with those of a user of other methods of input. | ||
| * As a keyboard user, I should be able to perform all actions using a keyboard exclusively. | ||
| * As a keyboard user, I should not get unintentionally stuck. | ||
| * As a keyboard user, keyboard shortcuts and assistive technologies do not interfere with each other. | ||
| * As a keyboard user, timing should not prevent me from completing actions. | ||
| * As a keyboard user, I should not be required to press multiple keys at the same time to complete an action. | ||
| * As a keyboard user, I am informed of non-standard commands before I need to make use of one. | ||
| * As a keyboard user, information on available shortcuts is provided in context and in a way I can perceive. | ||
| * As a keyboard user, the keyboard commands that I need to press don’t interfere with my operating system and/or assistive technology. | ||
| * As a keyboard user, my choice of keyboard is fully supported. | ||
| * As a keyboard user, I should be provided with a method of skipping repetitive navigation links. | ||
| * As a keyboard user, I would like my user agent to provide keyboard shortcuts to quickly navigate around an interface. | ||
| * If I implement a keyboard device within my site/app, that control must respond correctly to standard keyboard commands. | ||
| * As a keyboard user, I am warned about changes in context before they occur. | ||
| * As a keyboard user, I am warned about changes in focus before they occur. | ||
| * As a keyboard user, I am not expected to use a certain viewport in order to use a keyboard. | ||
| * As a keyboard user, applications should be flexible in allowing me to use the keyboard commands I want to use (e.g. through personalization). | ||
| * As a keyboard user, I shouldn't have my expected keyboard commands disabled. | ||
| * As a keyboard user, I should be able to access all scrollable regions of a view/app so I can read all text within these regions. | ||
| * As a keyboard user, when I reach a custom implementation of a common component, all keyboard commands that exist are implemented. | ||
| * As a user, I don’t want a keyboard shortcut to be the only way to do something. (or, there should not be only one way to do something). | ||
| * As a keyboard user typing content, I need to know what the return/tab/delete/… key will do. | ||
| * [TODO] I need multiple ways/formats to access content. | ||
| * As a person who is blind or has low vision, or a motor, cognitive or learning disability, I need keyboard commands to remain consistent. | ||
| * As a person who is blind or has low vision, or a motor disability, I need to be able to complete tasks using a keyboard without it requiring more steps or greater complexity than other input methods. | ||
| * As a person who is blind or has low vision, or a motor disability, I need to be able to perform all actions using only a keyboard. | ||
| * As a person who is blind or has a motor disability, I need to be able to move into and out of all interactive components so that I do not become trapped. | ||
| * As a person who is blind or has low vision, or a motor disability, I need to be able to rely on keyboard shortcuts without them conflicting with my assistive technology. | ||
| * As a person who is blind or has low vision, or a motor disability, I need to be able to complete actions using a keyboard without being prevented by timing constraints. | ||
| * As a person who has a motor disability, I need to be able to complete actions using a keyboard without pressing multiple keys at the same time. | ||
| * As a person who is blind or has low vision, or a motor disability, I need to be informed about non-standard keyboard commands before I need to use them. | ||
| * As a person who is blind or has low vision, or a motor disability, I need information about available keyboard shortcuts to be provided in context and in a way I can perceive it. | ||
| * As a person who is blind or has low vision, or a motor disability, I need keyboard commands to be compatible with my operating system and assistive technology. | ||
| * As a person who is blind or has low vision, or a motor disability, I need my choice of keyboard to be fully supported. | ||
| * As a person who is blind or has low vision, or a motor disability, I need to be able to skip repetitive navigation when using a keyboard. | ||
| * As a person who is blind or has low vision, or a motor disability, I need to be able to quickly navigate an interface using keyboard shortcuts. | ||
| * [TODO]If I implement a keyboard device within my site/app, that control must respond correctly to standard keyboard commands. | ||
| * As a person who is blind or has low vision, or a cognitive or learning disability, I need to be informed before my keyboard actions trigger a change in context. | ||
| * As a person who is blind or has low vision, or a cognitive or learning disability, I need to be informed before my actions trigger an unexpected change in keyboard focus. | ||
| * As a person who has low vision, I need keyboard functionality to work regardless of the viewport I'm using. | ||
| * As a person who is blind or has low vision, or a motor disability, I need applications to support the keyboard commands I’ve personalized to suit my needs. | ||
| * As a person who is blind or has low vision, or a motor disability, I need the keyboard commands I expect to use to remain available. | ||
| * As a person who is blind or has low vision, or a motor disability, I need keyboard access to every scrollable region so that I can read all of the text within it. | ||
| * As a person who is blind or has low vision, or a motor disability, I need custom implementations of common components to support standard keyboard interactions. | ||
| * As a person with a motor, cognitive or learning disability, I need more than one way to perform actions so that I do not have to rely on keyboard shortcuts. | ||
4 changes: 2 additions & 2 deletions
4
.../guidelines/input-operation/physical-or-cognitive-effort-when-using-keyboard.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| ## User needs | ||
|
|
||
| * As a keyboard user, I should be able to complete actions in a comparable amount of time to other users. | ||
| * As a keyboard user, I need to be able to access content in an equivalent way as other input modalities. | ||
| * As a person who is blind, or has low vision or a motor disability, I need to be able to complete tasks as efficiently using only a keyboard as someone using another input device. | ||
| * As a person who is blind, has low vision, or a motor disability, I need to be able to access content using only a keyboard in a way that’s equivalent to using other input devices. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unclear