Could we merge keyboard shortcut lists to have one only source.

[gautierchomel]

Thorium settings panel displays the shortcuts list and allows users to modify them to his needs. It is authored with h3 titles.

Aside from this, for quick reference, the support page lists the default shortcuts and adds a short description. It is authored as a definition list instead of headings.

I have a hard time maintaining that second source. We could think about how to use the original content generated by Thorium to publish the list parallelly on the support page or enhance the Thorium list with definitions and an export (as HTML) button so the user can generate his helper/cheatsheet for quick reference.

[gautierchomel]

For the documentation generation, I have this https://rawcdn.githack.com/edrlab/thorium-reader-doc/4776ef848afc2bc0f31e6b0b922b722d39cc56fa/content/en/th3/400_ressources/keyboard_default.html HTML from this code https://github.com/edrlab/thorium-reader-doc/blob/shortcut-ganeration/content/en/th3/400_ressources/keyboard_default.html

[danielweck]

Hello @gautierchomel FYI there is now an additional keyboard shortcut to add to the list:
https://thorium.edrlab.org/en/th3/400_ressources/402_keyboard-shortcuts/

Current documentation prose:

Main content(FocusMain) Ctrl + F10
in reader and library windows, moves the keyboard focus to the "main" area landmark (in the reader view, this is immediately before the frame that displays publication content)

I propose the following edit:

in reader and library windows, moves the keyboard focus to the "main" area landmark. in the reader view, the keyboard focus moves one step further into the frame that displays publication content (screen readers automatically read the currently-focussed HTML element inside the displayed document)

...and I propose the additional keyboard shortcut with key modifier SHIFT:

Main content Deep (FocusMainDeep) Shift + Ctrl + F10
just like "Main content" / FocusMainDeep in the reader view (see above), but the keyboard focus is forced deeper into the frame that displays publication content (this can help in cases where screen readers do not automatically read the currently-focussed HTML element inside the displayed document)