Open klemay opened 3 years ago
Example of potential for conflict between shortcut keys: Using keyboard shortcut 'h' with PDF changes pointer to Hand Tool
Proposed list of actions to trigger with a keyboard shortcut:
In Editor:
[DONE]
a
h
Some additional notes:
- Navigate to next/previous annotation card
- Navigate to next/previous selected document text
It may make sense for these to use same KB shortcut, with the difference being whether sidebar is open or shut.
Also, if a user has navigated to a selected text in the document, opening the sidebar should transfer that focus to the related annotation card. Vice versa with an annotation card selected when the sidebar is closed.
Adding a detail I noted during the OSU call.
The "h" shortcut for "Highlight" conflicts with the common use of "h" as a shortcut to navigate "Headers."
While there is a "pass through mode" in screen readers to avoid this conflict, not all screen reader users will be that sophisticated.
@mattdricker you had mentioned something about work we had planned on "modifier keys" that might address this.
@jeremydean yes, we will plan on using modifier keys (e.g. ctrl + alt) with all of our kb shortcuts to avoid these conflicts. Modifier keys currently TBA.
Discussion on this topic will likely solve https://github.com/hypothesis/support/issues/201.
Issue was linked to Harvestr Discovery: Use only my keyboard
Some additional notes:
- Navigate to next/previous annotation card
- Navigate to next/previous selected document text
It may make sense for these to use same KB shortcut, with the difference being whether sidebar is open or shut.
Also, if a user has navigated to a selected text in the document, opening the sidebar should transfer that focus to the related annotation card. Vice versa with an annotation card selected when the sidebar is closed.
Hi @jeremydean ,
Do you know if they've gotten anywhere on "Navigate to next/previous annotation card?"
Currently, users can annotate selected text by typing
a
to create an annotation orh
to create a highlight. This meets WCAG guidelines but could use some improvement and new additions. For example:Notes
To Do: