[
    {
        "role": "user",
        "content": "I%20am%20using%20an%20NLS%20E-Reader%20as%20a%20braille%20display%20for%20Jaws%20o%20my%20Windows11%20PC.%20I%20want%20ot%20assign%20a%20braille%20keystroke%20that%20will%20open%20a%20contextmenu%2C%20such%20as%20a%20menu%20os%20spelling%20suggestions%2C%20etc.%20I%27ve%20looked%20in%20Jaws%20keyboard%20manager%20and%20can%27t%20find%20where%20to%20assign%20or%20how%20to%20add%20this%20braille%20keystroke.%20What%20do%20I%20do%3F"
    },
    {
        "role": "assistant",
        "content": "I couldn\u2019t find anything showing that JAWS allows **assigning a braille-display key or chord** directly to open the *context menu* (like Shift+F10 or the Applications key) *through the standard Keyboard Manager*. The available documentation doesn\u2019t describe a built-in way to map a braille input key or chord to that Windows context menu command. However, I also found some useful alternatives and workarounds, and details on what *is* possible. Here\u2019s a summary plus what you can try:\n\n---\n\n## What the official docs say\n\n- JAWS\u2019s \u201cKeyboard Manager\u201d lets you remap *some* commands, especially keyboard commands, but the braille command assignments are more rigid (especially core system commands). There\u2019s no documented example of mapping a braille chord to open the context menu via Keyboard Manager. ([support.freedomscientific.com](https://support.freedomscientific.com/Content/html/jawshq/JAWS-braille-keystrokes.html?utm_source=openai))  \n- The \u201cBraille Commands\u201d documentation describes the many built-in chords on Focus displays (and others), including how to simulate modifier keys, handle selections, and other functions. It lists what already exists, but does *not* cover mapping new custom functions like opening context menus beyond the existing ones. ([support.freedomscientific.com](https://support.freedomscientific.com/Content/html/jawshq/JAWS-braille-keystrokes.html?utm_source=openai))  \n\n---\n\n## Possible workarounds\n\nWhile you may not be able to directly assign a custom chord for \u201ccontext menu,\u201d here are ways to get similar functionality or use existing functionality:\n\n1. **Use \u201cWindows context menu key\u201d or Shift+F10**  \n   * If your braille display has buttons that can mimic \u201cApplications key\u201d or Shift+F10 via built-in chords, see if one of them already triggers the context menu.  \n   * On Focus displays, many commands simulate modifier + other keys. For example, pressing DOT 8 CHORD + modifier keys followed by a command. If you find which combination means SHIFT or the Applications key, you might pair that with F10 or whatever your device supports. ([support.freedomscientific.com](https://support.freedomscientific.com/Content/html/jawshq/JAWS-braille-keystrokes.html?utm_source=openai))  \n\n2. **Check \u201cCursor Router + Panning Button\u201d combinations**  \n   * On Focus displays, pressing and holding a panning button while pressing a cursor router can simulate a right-mouse-click, which usually opens a context menu in many Windows contexts. For example: *\u201cPress and hold the LEFT or RIGHT PANNING BUTTON while simultaneously pressing a CURSOR ROUTER BUTTON to simulate a right mouse click at that location.\u201d* That may be sufficient depending on what context you\u2019re in. ([support.freedomscientific.com](https://support.freedomscientific.com/Content/Documents/Manuals/Focus/Focus14Blue/Focus-14-Blue-Online-Users-Guide.htm?utm_source=openai))  \n\n3. **Use existing \u201cOpen context menu\u201d Windows commands via your braille display**  \n   * If a chord combination exists that sends Shift+F10 (or the Applications key), that might work. It\u2019s worth exploring your device\u2019s Documentation (e.g. Focus manual) under \u201cJAWS Commands\u201d or \u201cWindows Commands\u201d section to find any existing mapping. The Focus 40/80 manuals include \u201cConvenient JAWS and Windows Commands\u201d lists. ([freedomscientific.com](https://www.freedomscientific.com/content/downloads/focus/documentation/Focus40_80_Users_Guide.pdf?utm_source=openai))  \n\n4. **Custom scripting**  \n   * JAWS has a scripting language and a \u201cKeyboard Manager\u201d for customizing behavior in specific applications. You might write a small JAWS script that defines a custom function to open context menu (send Shift+F10) and then assign a keyboard shortcut (using the standard PC keyboard) to trigger that script.  \n   * If your braille display is using HID mode (as newer ones do), you may be able to send a standard PC key combination from the display that the script can pick up. JAWS 2026 has expanded HID braille support and more default commands for HID displays. ([support.freedomscientific.com](https://support.freedomscientific.com/Downloads/JAWS/JAWSWhatsNew?version=17See&utm_source=openai))  \n\n5. **Using AutoHotKey or other external key-mapping software**  \n   * If the braille display can send a specific signal or chord that\u2019s distinct, you might intercept it with a tool like AutoHotKey to translate it into Shift+F10 or whatever. This depends a lot on whether the display\u2019s input is recognizable as a unique key or chord at the system level.  \n   * Be aware that using AutoHotKey may conflict with some system protections and might require administrator access.\n\n---\n\n## What you should try\n\nHere\u2019s a step-by-step you can try to see if you can make this work:\n\n1. **Check your display\u2019s manual**, especially the sections \u201cWindows Commands\u201d and \u201cJAWS Commands\u201d under your specific model (e.g. Focus Blue, etc.). See if there is a chord already assigned to \u201cApplications key\u201d or \u201ccontext menu\u201d or Shift+F10.  \n\n2. **Try the \u201cRight-mouse click simulation\u201d**: On a Focus display: press and hold a panning button while pressing a cursor router button, to see if that brings up the context menu at that position.  \n\n3. **Experiment with a chord that includes DOT 8 CHORD** plus a combination that might equate to Shift or the Applications key, then F10\u2014if your display lets you do modifier mapping with DOT 8.  \n\n4. If above fail, **use Keyboard Manager + scripting**:  \n   * Write a small script in JAWS that issues the context menu key (Shift+F10) in the desired application(s).  \n   * Then assign a QWERTY keyboard shortcut to that script, something you can press (or send from braille).  \n\n5. If your display is HID, see if there\u2019s a newer firmware or setting that identifies the display\u2019s input as standard keyboard inputs\u2014because newer JAWS versions treat HID braille input more like a regular keyboard, which might open up mapping options. ([support.freedomscientific.com](https://support.freedomscientific.com/Downloads/JAWS/JAWSWhatsNew?version=17See&utm_source=openai))  \n\n6. **Contact Freedom Scientific support** or check their forums/hotline: they may have unpublished tips or best practices for users wanting to map non-standard functions via the braille display.\n\n---\n\nIf you tell me *which exact model* of NLS eReader or braille display you're using, I can try to pull up its manual and see if there's a specific command already there or more precise steps for your device. Do you want me to look up instructions for your specific model?"
    },
    {
        "role": "user",
        "content": "In%20the%20beginning%20of%20htis%2C%20I%20told%20you%20that%20I%20was%20using%20an%20NLS%20Humanware%20E-Reader%20display."
    },
    {
        "role": "assistant",
        "content": "Thanks for clarifying that you're using the **NLS Braille eReader by HumanWare** as your display. I checked the latest documentation and resources, and there\u2019s no indication in the public documentation that you can map or customize a **braille display chord** to send specific Windows keystrokes like \u201cApplications key\u201d or \u201cShift+F10\u201d in JAWS. The \u201cContext Menu\u201d commands built into the reader are for the device\u2019s own OS, not for Windows or JAWS contexts. ([loc.gov](https://www.loc.gov/nls/services-and-resources/equipment-for-nls-materials/nls-braille-ereader-humanware-user-guide/?utm_source=openai))\n\nHere are what I found relevant and what you *can* do, plus some suggestions that might help you achieve something close to what you want.\n\n---\n\n## What the NLS E-Reader *can* do\n\n- The eReader has a built-in \u201cContext Menu\u201d within its own OS, accessible via **Space + h** (braille \u201ch\u201d = dots 1-2-5). This menu is part of the eReader hardware/software, not something directed to the PC/JAWS. ([loc.gov](https://www.loc.gov/nls/services-and-resources/equipment-for-nls-materials/nls-braille-ereader-humanware-user-guide/?utm_source=openai))  \n- When used in **Braille Display Mode**, the device passes keystrokes (via its Perkins braille keyboard and braille input keys) to the host (e.g. Windows). This includes typical editing and navigation keys. ([loc.gov](https://www.loc.gov/nls/services-and-resources/equipment-for-nls-materials/nls-braille-ereader-humanware-user-guide/?utm_source=openai))  \n- The manual confirms that you can use the eReader as an external keyboard in this mode. That means keys like space-with-something should be recognized by JAWS/WIndows if they correspond to standard key events. ([loc.gov](https://www.loc.gov/nls/services-and-resources/equipment-for-nls-materials/nls-braille-ereader-humanware-user-guide/?utm_source=openai))\n\n---\n\n## What the eReader *cannot* do (from what I saw)\n\n- There is **no public support** for customizing or creating a chord on the eReader that sends a non-predefined Windows command such as \u201copen context menu in Windows\u201d (Shift+F10 or the Applications key).  \n- The \u201cContext Menu\u201d command (Space + h) refers to the eReader\u2019s own menu when it is operating as a standalone reader \u2014 not to arbitrarily send a \u201ccontext menu\u201d to Windows or JAWS in all applications. ([helenkeller.org](https://www.helenkeller.org/a-review-of-the-humanware-nls-ereader-a-free-braille-display-for-nls-patrons-in-the-u-s/?utm_source=openai))  \n- The NLS eReader manual does not include any facility for **user-defined macros** of key chords related to PC/JAWS functionality. ([loc.gov](https://www.loc.gov/nls/services-and-resources/equipment-for-nls-materials/nls-braille-ereader-humanware-user-guide/?utm_source=openai))\n\n---\n\n## What you *can* try as a workaround\n\nSince you likely can\u2019t remap a chord on the eReader itself to send \u201ccontext menu\u201d in Windows directly, here are some workarounds or strategies you could use to approximate this functionality:\n\n1. **Test built-in keystrokes that may already send the PC context menu**  \n   - Try pressing the **Applications key** or **Shift+F10** from the eReader\u2019s keyboard (if those keys are sent in Braille Display Mode). Sometimes dot-combinations like Space + *some letter* produce those keys when connected. See which keys your device sends when in PC mode.\n\n2. **Use Windows/JAWS scripting or Keyboard Manager**  \n   - In JAWS, you can write a **script** or set a **Keyboard Manager** shortcut that sends **Shift+F10** when you press a specific PC key chord. Then see if your eReader in Braille Display Mode can send that chord/key.  \n   - For example, pick a chord that the eReader sends as a unique key sequence, map that in JAWS to run a script which triggers Shift+F10 (the Windows context menu).\n\n3. **Use external key-mapping tools**  \n   - Use a tool like **AutoHotKey** (on PC) to capture a particular key press sequence coming from the eReader and translate it into Shift+F10. This is a \u201ccatch-all\u201d approach, but depends on whether the eReader\u2019s chord produces a recognizable unique input.\n\n4. **Contact HumanWare or Freedom Scientific support**  \n   - Sometimes internal firmware or driver settings not in the public manual allow more functionality. Ask whether there is undocumented support for mapping new chords to Windows commands when in Braille Display Mode.\n\n5. **Check for firmware or software updates**  \n   - Sometimes new firmware updates change or expand what can be done when the device is used as a braille display. Make sure your eReader is fully updated. ([loc.gov](https://www.loc.gov/nls/services-and-resources/equipment-for-nls-materials/nls-braille-ereader-humanware-user-guide/?utm_source=openai))\n\n---\n\nIf you like, I can try looking up **whether in the latest firmware** there is now a way to map Space + h (or some other chord) *when connected to Windows* to do Shift+F10. Would you want me to check the most recent release notes or firmware details for your model?"
    },
    {
        "role": "user",
        "content": "There%20are%20no%20shift%20keys%20on%20this%20braille%20display.%20If%20it%20helps%20the%20display%20is%20practically%20a%20clone%20of%20the%20Brailliant%20BI20X."
    },
    {
        "role": "assistant",
        "content": "Thanks \u2014 I looked into the Brailliant BI-X series documentation (which is very close to the NLS eReader in hardware) and I found confirming info plus possibilities based on their behavior. Here\u2019s a more focused breakdown based on that:\n\n---\n\n## What the BI-X / NLS eReader *already does*\n\n- On the Brailliant BI X series (and NLS eReader which is a close \u201cclone\u201d in physical layout), within the device\u2019s *own* KeySoft OS, the **Context Menu** is opened by pressing **Space + M**. In KeySoft, this shows app-specific functions and available actions. ([scribd.com](https://www.scribd.com/document/970842987/User-Manual?utm_source=openai))  \n- On the NLS eReader, the KeySoft-style \u201cContext Menu\u201d key used within device menus is **Space + H**. Note: \u201cSpace+M\u201d on Brailliant/Chameleon shows the Context Menu; but on NLS eReader that same function is mapped to Space + H, while Space + M returns to the Main Menu. ([nfbnet.org](https://nfbnet.org/pipermail/trainer-talk_nfbnet.org/2024-March/006927.html?utm_source=openai))  \n\n---\n\n## What this means for mapping into *Windows / JAWS*\n\n- The key combos like **Space + M** or **Space + H** are interpreted *by the device firmware* for the eReader in its standalone mode (KeySoft). **They are not documented** to send specific Windows/JAWS keystrokes like Shift+F10 or Applications key. In other words, they don\u2019t magically become \u201csend Shift+F10 to Windows\u201d\u2014they are internal device commands.  \n\n- The documentation for BI X series doesn\u2019t include a way to **reassign** those built-in device commands to other functions, or define custom chord to send Windows context menu commands. ([scribd.com](https://www.scribd.com/document/970842987/User-Manual?utm_source=openai))  \n\n---\n\n## Possible approaches you *can* try\n\nEven though the device firmware doesn\u2019t support mapping Space+H or Space+M to Shift+F10 directly, here are potential workarounds using JAWS or external tools:\n\n1. **Find a key or chord that is passed through as a PC key**  \n   - Some Perkins layout keys are passed through exactly as standard keys (for letters, Enter, backspace). Test if pressing certain braille keyboard combinations is recognized by Windows/JAWS (for example via a keyboard test app).  \n   - If you find such a chord, you could use that in JAWS\u2019s Keyboard Manager or Scripts to send \u201ccontext menu.\u201d\n\n2. **Use JAWS scripting / Keyboard Manager**  \n   - Create a JAWS script that triggers the Windows context menu (Shift+F10).  \n   - Assign it to a keyboard shortcut that you can send via the device. If the device can send some unused letter or combination, map that.  \n\n3. **AutoHotKey (or similar key intercept tool)**  \n   - If you discover a unique key/chord signal coming from the eReader in Windows, use AutoHotKey to catch it and then send \u201cShift+F10\u201d or whatever you need. This depends on whether the chord generates something catchable.  \n\n4. **Firmware or driver update**  \n   - Sometimes display firmware / driver improvements expand HID or Bluetooth keyboard behavior. Check if your eReader/BI-X firmware is latest. Maybe future updates will allow more remapping or BLE HID key customization.\n\n---\n\nIf you like, I can try to pull up the *very latest* firmware/driver notes for your specific NLS eReader (or BI-20X, since similar) to see whether HumanWare or NLS has added any custom key mapping functionality (especially for mapping to Windows/JAWS context menu). Would you prefer I go ahead and check that for your model?"
    },
    {
        "role": "user",
        "content": "How%20would%20I%20write%20a%20Jaws%20script%20that%20maps%2C%20for%20example%2C%20the%20braille%20keys%201-3-4-5-space%20to%20Shift%2BF10%3F%20I%27d%20like%20it%20towork%20about%20anywhere%20but%20especially%20in%20Chrome%2Ca%20nd%20more%20specifically%20on%20Google%20Docs%20in%20Chrome."
    },
    {
        "role": "assistant",
        "content": "Here\u2019s how you *could* write a JAWS script that maps a custom braille\u2010chord (like \u201cdots 1-3-4-5 + Space\u201d) to send **Shift+F10** (which opens the Windows \u201cApplications\u201d/context menu). This will work globally (in the Default script), and you can also override it specifically for Chrome or Google Docs if needed.\n\n---\n\n## Key points you need to know first\n\n- In JAWS scripting, you can bind a script to a *keystroke*. ([freedomscientific.com](https://www.freedomscientific.com/Content/Documents/Other/ScriptManual/03-2_ProcessingKeystrokes.htm?utm_source=openai))  \n- In the script you write, you can call `TypeKey(\"...\")` to simulate pressing other keys (like Shift+F10). ([support.freedomscientific.com](https://support.freedomscientific.com/Content/Documents/Other/ScriptManual/10-1_PassThroughScripts.htm?utm_source=openai))  \n- The \u201cDefault.jss\u201d script file holds scripts that work globally (across applications). Individual application scripts (like for Chrome) will override Default when in that application. ([support.freedomscientific.com](https://support.freedomscientific.com/content/documents/other/scriptmanual/03-1_jawsscriptsandscriptfiles.htm?utm_source=openai))  \n\n---\n\n## How to map \u201cdots 1-3-4-5 + Space\u201d to Shift+F10\n\nSince your display has no \u201cShift\u201d key, the chord you choose (dots 1-3-4-5 + Space) must be recognized by JAWS *as a single keystroke* in Braille Display (or Braille Input) mode. If that\u2019s possible, then you can bind it.\n\nBelow is **example script text** for Default.jss that will:\n\n- Capture the custom chord \u201cDots1345+Space\u201d\n- Simulate Shift+F10\n- Work everywhere\n- Have a version specific for Chrome / Google Docs if needed\n\nYou\u2019ll use the Script Manager in JAWS to add this.\n\n---\n\n### Example Default.jss Script\n\n```jss\n// Place this in Default.jss via Script Manager (Insert+0, open Default, etc.)\n\nScript Chord1345Space_ContextMenu ()\n    TypeKey(\"Shift+F10\")\nEndScript\n```\n\nThen, you bind this script to the keystroke that represents your chord. The binding may look something like:\n\n```\nDots1345 Space = Chord1345Space_ContextMenu\n```\n\n---\n\n### Full steps to write and bind the script\n\n1. Open the **JAWS Script Manager** (Insert + 0).\n2. Open **Default.jss** (if you want it global) or Chrome.jss (if you want just for Chrome).\n3. Press **Ctrl+E** to create a new script:\n   - Name: `Chord1345Space_ContextMenu`\n   - Check \u201cCan be attached to a key\u201d\n   - Write a synopsis like: \u201cChord dots 1-3-4-5 + Space invokes context menu (Shift+F10)\u201d\n4. In the \u201cAssignable Key\u201d field, try pressing the chord (dots 1-3-4-5 + Space). If the system recognizes it, it will fill that field. If not, you may need to refer to how your braille display signals that chord in JAWS; sometimes these are reported as \u201cBrailleDots1345SpaceChord\u201d or similar.\n5. Enter the script body like:\n\n   ```jss\n   Script Chord1345Space_ContextMenu ()\n       TypeKey(\"Shift+F10\")\n   EndScript\n   ```\n\n6. Save / compile the script (Ctrl+S). JAWS should say \u201cCompile Complete.\u201d\n7. Test it somewhere (File Explorer, desktop) to see if pressing your chord triggers the context menu.\n\n---\n\n## Overriding in Chrome / Google Docs\n\nIf you want Google Docs (in Chrome) to behave differently, you can put the same script into **Chrome.jss** or even **Docs in Chrome** script file:\n\n- The same `Script Chord1345Space_ContextMenu()`  \n- Then bind the same keystroke inside that application-specific script file  \n- Because application-specific scripts take precedence, this ensures that in Chrome or Docs the chord still works (or if you want different behavior, you could adjust it).\n\n---\n\n## Possible issues & things to test\n\n- **Does pressing \u201cdots 1-3-4-5 + Space\u201d generate a keystroke that JAWS can catch?** If the device\u2019s driver or firmware intercepts it before JAWS, or if the chord isn\u2019t exposed in Windows as a regular input, then JAWS won\u2019t be able to bind or script to it.\n- **Conflicts with existing key bindings.** If that chord is already bound to something (maybe built-in), the new binding may override or conflict. The Script Manager will usually warn you. ([freedomscientific.com](https://www.freedomscientific.com/Content/Documents/Other/ScriptManual/03-2_ProcessingKeystrokes.htm?utm_source=openai))  \n- **Verifying sequence names.** When you bind the key, JAWS might expect you to choose from a list like \u201cBraille Dots 1-3-4-5 + Space\u201d or \u201cSpace + Dots 1-3-4-5 Chord,\u201d depending on display manufacturer. Check your display\u2019s description in the \u201cKeyboard Manager\u201d or under \u201cBraille Input Commands.\u201d  \n- **Permission to send Shift+F10** \u2013 some applications (especially web apps) might handle context menus differently. But since Shift+F10 is the standard Windows context menu key, most applications will respond.\n\n---\n\nIf you like, I can write a *ready-to-import* JSS file tailored to your device (if you tell me the exact model) and test lines (with the likely chord names) so you can just paste it in. Do you want me to prepare that for you?"
    },
    {
        "role": "user",
        "content": "What%20if%20my%20Default.jss%20says%20User%20Default.jss.%20Is%20tht%20the%20same%20hting%3F"
    },
    {
        "role": "assistant",
        "content": "Yes\u2014they're related but **not exactly the same**, and understanding the difference can help you know where to put scripts like the chord\u2010to\u2010Shift+F10 mapping.\n\nHere\u2019s how it works in JAWS:\n\n---\n\n## What \u201cDefault.jss\u201d is\n\n- **Default.jss** is the *global/default* script file. It contains scripts that are active in **all applications** in JAWS. ([support.freedomscientific.com](https://support.freedomscientific.com/content/documents/other/scriptmanual/03-1_jawsscriptsandscriptfiles.htm?utm_source=openai))  \n- Anytime a key or event occurs, JAWS looks in the **application\u2010specific script** if it is active, and if no match is found there, then in **Default.jss**. ([afb.org](https://afb.org/aw/4/6/14806?utm_source=openai))  \n\n---\n\n## What \u201cUser Default.jss\u201d means\n\n- The name \u201cUser Default.jss\u201d generally refers to a **user\u2010customized version** of the Default.jss script\u2014scripts saved under your *user settings*.  \n- There are **shared settings** (for all users on the computer) and **user settings** (for your user profile). If you modify Default.jss via Script Manager and save it under your user settings, sometimes JAWS refers to it as *User Default.jss* to distinguish yours from the shared version. ([sensibiliser.avh.asso.fr](https://sensibiliser.avh.asso.fr/fiches-informatique-adaptee/fiches_jaws/jaws/jaws_installer_supprimer_script.htm?utm_source=openai))  \n\n---\n\n## Are they the same or different?\n\n- **They serve the same purpose**: hold global scripts for JAWS.  \n- The difference is **whose copy you're editing**\u2014the shared (for all users) vs. your personal (user\u2010specific). If Default.jss only exists in the shared folder and you edit it, sometimes a \u201cuser\u201d copy is created so that updates to shared scripts (e.g. via JAWS update) won\u2019t overwrite your customizations. ([mail-archive.com](https://www.mail-archive.com/jaws-users-list%40jaws-users.com/msg52382.html?utm_source=openai))  \n\n---\n\n## What it means for your script mapping\n\n- If your *Default.jss* appears as *User Default.jss*, that\u2019s the correct place for your custom chord \u2192 Shift+F10 mapping if you want it global.  \n- Make sure you\u2019re editing the user version so your changes persist across updates and are only affecting your user account.  \n\n---\n\nIf you want, I can walk you through exactly how to open the correct Default (or User Default) file in your version of JAWS (2026) and insert the script\u2014so you don\u2019t accidentally modify the shared one."
    },
    {
        "role": "user",
        "content": "Yes%2C%20how%20do%20I%20get%20to%20the%20actual%20default.jss%20file%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s how to locate the **actual Default.jss (or the user\u2019s version, often called User Default.jss)** in JAWS, and how to open it safely so your edits only affect your user profile.\n\n---\n\n## Where Default.jss lives: shared vs user settings\n\nJAWS uses two script file areas:\n\n| Scope | Folder | When it\u2019s used / replaced |\n|---|---|---|\n| **Shared / All Users** | `C:\\ProgramData\\Freedom Scientific\\JAWS\\<version>\\Settings\\enu` (on English installs) or similar. Contains the default, original Default.jss provided by Freedom Scientific. ([sensibiliser.avh.asso.fr](https://sensibiliser.avh.asso.fr/fiches-informatique-adaptee/fiches_jaws/jaws/jaws_installer_supprimer_script.htm?utm_source=openai)) |\n| **User / My Settings** | `C:\\Users\\<YourUserName>\\AppData\\Roaming\\Freedom Scientific\\JAWS\\<version>\\Settings\\enu` | This is where any custom or user\u2010modified Default.jss (\u201cUser Default.jss\u201d) lives. If you make changes, you should use this copy so the shared version stays untouched. ([sensibiliser.avh.asso.fr](https://sensibiliser.avh.asso.fr/fiches-informatique-adaptee/fiches_jaws/jaws/jaws_installer_supprimer_script.htm?utm_source=openai)) |\n\n---\n\n## How to open the correct Default.jss file in JAWS\n\n1. **Open the Script Manager**  \n   Press **Insert + 0** while JAWS is running. This opens the Scripts Manager tool. ([www2.freedomscientific.com](https://www2.freedomscientific.com/PDF/visionloss/manuals/ScriptManual/04-2_StartingTheScriptManager.htm?utm_source=openai))\n\n2. **Determine which file is open**  \n   - If you open Script Manager from the JAWS window without being inside a specific application, it will open the Default script file (which may already be the shared version or your user version). ([www2.freedomscientific.com](https://www2.freedomscientific.com/PDF/visionloss/manuals/ScriptManual/04-2_StartingTheScriptManager.htm?utm_source=openai))  \n   - If you're inside an application (like Chrome or Word), Script Manager opens the *application-specific script file*. To open Default.jss instead, you need to switch manually. ([sensibiliser.avh.asso.fr](https://sensibiliser.avh.asso.fr/fiches-informatique-adaptee/fiches_jaws/jaws/jaws_installer_supprimer_script.htm?utm_source=openai))\n\n3. **Switch to Default.jss if needed**  \n   In Script Manager, do this:\n\n   - Press **Alt + F** to open the File menu.  \n   - Press **E** to \u201cExplore Shared Files Folder\u201d or something similar if you want the default shared version.  \n   - There should also be an option (through menus or \u201cOpen File\u201d) to go into your **user settings folder** and find **Default.jss** there. ([sensibiliser.avh.asso.fr](https://sensibiliser.avh.asso.fr/fiches-informatique-adaptee/fiches_jaws/jaws/jaws_installer_supprimer_script.htm?utm_source=openai))\n\n4. **Identify \u201cUser Default.jss\u201d**  \n   - If you see \u201cDefault.jss\u201d in your user folder, that\u2019s your personal version. Sometimes it is shown as \u201cUser Default.jss\u201d in JAWS UI.  \n   - If that file does *not* yet exist in your user settings folder, then you are still using the shared version. If you save Default.jss via Script Manager, JAWS will often save user modifications into your user settings folder, effectively creating \u201cUser Default.jss.\u201d ([freedomscientific.com](https://www.freedomscientific.com/Content/Documents/Other/ScriptManual/03-1_JAWSScriptsAndScriptFiles.htm?utm_source=openai))\n\n---\n\n## Best practices when editing Default.jss\n\n- Work in your **user settings copy** (User Default.jss), so your changes apply only to your account and won\u2019t be overwritten by updates.  \n- Always **compile** after editing (in Script Manager, Ctrl + S). This creates the binary version (.JSB) that JAWS actually runs. If there are compilation errors, you\u2019ll be notified. ([sensibiliser.avh.asso.fr](https://sensibiliser.avh.asso.fr/fiches-informatique-adaptee/fiches_jaws/jaws/jaws_installer_supprimer_script.htm?utm_source=openai))  \n- If something breaks or doesn\u2019t work correctly, you can remove or rename the user Default.jss file. JAWS will revert to using the shared version only. ([mail-archive.com](https://www.mail-archive.com/jaws-users-list%40jaws-users.com/msg52384.html?utm_source=openai))  \n\n---\n\nIf you tell me which version of JAWS you\u2019re using (for example, JAWS 2026 or 2024), I can give you the exact path on your computer to look in\u2014and walk you through opening the user vs shared file. Do you want that?"
    },
    {
        "role": "user",
        "content": "Give%20me%20the%20exact%20script%20text%20to%20paste%20in.%20I%27ve%20already%20assigned%20it%20to%20braille%20keys%201-3-4-5-space."
    },
    {
        "role": "assistant",
        "content": "Here\u2019s a complete JAWS script snippet you can paste into your **Default.jss / User Default.jss**. Since you've already bound the chord **dots 1-3-4-5 + Space** to a script name, this script just needs to match that name.\n\n---\n\n### Script Text\n\n```jss\nScript Braille1345Space_ContextMenu ()\n    // Simulate pressing Shift + F10 to open the context / Applications menu\n    TypeKey(\"Shift+F10\")\nEndScript\n```\n\n---\n\n### What to check / ensure\n\n- You bound **dots 1\u20103\u20104\u20105 + Space** to the script named `Braille1345Space_ContextMenu`.  \n- The script\u2019s **name** (`Braille1345Space_ContextMenu`) in the binding matches exactly the name here.  \n- After pasting in and saving, compile the scripts (in Script Manager usually Ctrl+S). Make sure it says \u201cCompile complete\u201d with no errors.  \n- Test it: Go to something like a file in File Explorer or an empty area on the desktop, press that braille chord, and see if the context menu (right\u2010click menu) opens.  \n\n---\n\nIf you want, I can give you an alternate version that works only in Chrome / Google Docs (in case you later want a different behavior there)."
    }
]