-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Keyboard shortcuts for list items are missing #9611
Comments
This is quite annoying for me too. It's a bit blocked in that the expected behaviour is to use tabs, but that can interfere with keyboard navigation. @mcsf do we have other issues for this? Can we consolidate? I'd like to move forwards with using tabs and showing that shortcut in the tooltip. |
As noted in #10744 (comment), the current list shortcuts aren't the best. I think we should update them before making them more visible. |
@afercia Any ideas for good list indentation shortcuts that don't cash with the browser/OS? |
@iseulde I'm afraid there's no Escape 😆 from potential clashes. As mentioned in #4181 (comment) Google Docs uses Cmd+square brackets and yes, they clash with browsers history navigation on macOS. Also Gmail uses the same combination: Any keys combination will always have a chance to conflict with browsers, OSes, and assistive technologies shortcuts. Also, users have different needs. The only real solution to this problem is a mechanism to allow users to remap shortcuts based on their own needs. See #3218. I understand at this point of the release cycle that's not feasible, but #3218 is open since more than one year and it hasn't been prioritized by the team. At this point I can only suggest to try with two modifier keys. Maybe |
What are the action items here? |
You can use |
Google Docs is not a comparable example, as it's a full page editor in an ARIA application mode. Gutenberg is a Web application, where the Tab key is expected to keep its native behavior: navigate through focusable elements. The accessibility team has already given feedback in the previous issues, recommending to not change the default behavior and use alternative shortcuts for indentation. Thank you 🙂 |
If this ( |
Add the keyboard shortcuts for indent less and indent more on the list block when a user hover or focus over the particular item (not sure the correct term for 'item' is here) in the block's toolbar I don't know if all keyboard shortcuts should be added to all 'core' blocks in when a user focuses/hovers on the toolbar or if that decision has been made yet (that's another issue perhaps and out of this scope; but consistency's sake, I'd argue yes). ============================= |
@aduth #5807 was an experiment and we've decided to not implement it. role=application destroys any native semantics, i.e. any document information, as the page is not treated as a document any longer. That means no lists of heading announced, no list of links, no screen reader shortcuts to navigate through elements, no landmarks, etc. etc. Also, as already noted in previous issues and although Google Docs is not comparable to Gutenberg, it is true that the tab key works for indentation but the keyboard shortcut exposed to users is (on a mac) |
As much as I'd like the convenience of using tab for list indentation, I gather from @afercia that we still have a ways to go to make that happen. I think we could at least start with something like cmd + ]. Two questions that stand:
|
True that square brackets are not directly available in some keyboard layouts. As mentioned in many other issues, the only real solution to this and to potential shortcuts conflict is a mechanism to allow users to re-map the shortcuts. See #3218 |
@mcsf In Linux, the control keys are either CTRL, CTRL+ALT. ALT and ALT+SHIFT are reserved to open menu items. This is how Google Docs Keyboard Shortcuts looks like for me (Ubuntu Linux w Firefox browser): Text formatting Paragraph formatting Editing |
Actually, I've realized indentation was not part of the shortcuts I captured and I can only know the shortcut if I search for "indent"! Crazy GDocs. It looks like there are two shortcuts for Indentate paragraphs/lists on Google Docs:
Only the first one gets announced through the shortcuts help menu: |
Thanks for the insight, @nosolosw! |
Tested some editor desktop apps (LibreOffice, GEdit) and doesn’t seem to be an idiomatic way in Linux beyond Tab. |
Wild idea: what if space and backspace could be used at the start of a list item to indent in/out? |
@mcsf I like your idea! Would it be strange to require two spaces? Backspace definitely makes a lot of sense. |
Hm, at least on first consideration, two spaces would seem awkward to me. Single space seems more discoverable and natural. What do you think?
|
space / backspace as keyboard shortcuts for that sounds very odd to me. I guess we could try if there are no a11y drawbacks. |
Sounds good, if we work towards it being undoable.
Could you elaborate? Or does it merely sound odd? |
I like it because it's a bit inspired by Markdown/typewriting, where you would create the following: * base
* indented |
Definitely. This was, in my mind, a way to keep tab intact, as well as keyboard arrows. Indentation events (increase/decrease) would be announced ( |
Similar issues filed: #4181, #5087, #7051, #12142.
While editing a post in Gutenberg, I couldn't figure out how to indent list items by the keyboard which is a habit of mine (and I'd argue many others editors as well).
Describe the bug
No keyboard shortcuts display for the list block.
Mentioned in #7051 but that issue is not dedicated to this, I decided to make a new issue for this; close if this is too explicit.
To Reproduce
without looking on a separate page of documentation, right now:
Expected behavior
Personally, the expected action to indent an item in a list block would be done by issuing 'TAB' but that has been decided against for accessibility reasons
That the default behavior isn't used stresses the utility of having the keyboard shortcuts for list actions (outdenting, indenting) available.
Screenshots
see https://user-images.githubusercontent.com/1682452/40778281-f1054ca2-64d0-11e8-953f-704ef1e5ba1d.png
Additional context
(Issue made on CPL time)
The text was updated successfully, but these errors were encountered: