add explanation about access keys, will-fix: #40038

Localization-for-translators.md

@@ -145,7 +145,9 @@ Please read this section to be aware of the most common errors while translating
 
 ## Markdown text
 
-#### Current problems
+Our websites are written using Markdown, which is a text format with simple syntax, similar to wiki syntax. To learn more about markdown syntax you can read this page: https://daringfireball.net/projects/markdown/syntax
+
+#### Current problems in translations
 
 In this page you can see some of the current problematic strings : https://tpo.pages.torproject.net/community/l10n/
 
@@ -159,7 +161,6 @@ Links in markdown are like this: `[linked word](link)`, where link can be a URL
 - `See our [documentation about circumvention](https://tb-manual.torproject.org/circumvention/)`
 
 
-
 Remember **not to leave any spaces between [] and ()**, because otherwise the link will not work.
 
 | good | bad |
@@ -208,6 +209,29 @@ Sometimes the images are included with markdown, as this:
 
 In this case, `Image of an onion with a caution sign` is the alt attribute that needs translation.The address of the image is between parenthesis and is usually not changed.
 
+### Access keys
+
+Access keys are used to create shortcuts on the interface. They usually are marked by an underscore on the string when translating, and they activate when typing `Alt + key` on the keyboard. 
+
+For example for this menu:
+
+![VirtualBox_tails_27_12_2022_12_28_48](uploads/3bae58b30fe4f47d03dd9b383ef4d5a8/VirtualBox_tails_27_12_2022_12_28_48.png)
+
+We can see the access keys underlined on each of the menu options: 
+- A for Administration password
+- M for MAC Address anonymization
+- O for Offline mode, and so on
+
+For this, it is important to give **different access keys to each option on a menu**.
+
+When we are translating, access keys appear as this:
+
+![access_key_in_weblate](uploads/14a42d05db31bb57269bc2fd7a8abe8f/access_key_in_weblate.png)
+
+Or for example in the Tor Browser translations, they will appear separately. In this case you can deduce the access key string with Key information and the screenshot:
+
+ ![access_key.cleaned](uploads/a28068e3513ad54a2e365dc37f018dfe/access_key.cleaned.png)
+
 ## How to find the strings in the websites
 
 When on the transifex page, see in the context tab:
@@ -227,7 +251,7 @@ Ways to review your work and ensure that your translations do not create problem
   * Check specially that the links are working correctly and don't lead to a 404 error.
   * Compare with the English version. Do the images appear? are the styling, links, the same?
 * Check the [broken links page](https://tpo.pages.torproject.net/community/l10n/) to see if there are links you need to fix
-* Check the list of weblate errors.
+* Check the list of weblate errors: https://hosted.weblate.org/checks/?project=tor and make sure there are no problems
 
 ## Corrections to Tor Websites