[
    {
        "role": "user",
        "content": "using%20a%20braille%20display%20how%20do%20I%20type%20the%20symbol%20using%20the%20braille%20input"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s how you type the percent sign (\u201c%\u201d) using a braille display or input that supports Unified English Braille (UEB):\n\n---\n\n## \ud83d\udd0d What is the Braille for \u201c%\u201d\n\nIn UEB, the percent sign is represented by the following braille cell:\n\n\u2828\u2834\n\nThat\u2019s dots 4\u20136 followed by dots 3\u20135\u20136. ([brailleaustralia.org](https://brailleaustralia.org/wp-content/uploads/2013/10/UEB-Australian-Training-Manual-January-2022-Unicode.pdf?utm_source=openai))\n\n---\n\n## \u2328\ufe0f How to enter it using a braille keyboard / display\n\nIf your braille device or display lets you input braille directly (6-dot braille), here\u2019s what to do:\n\n- Press **dots 4-6** (sometimes referred to as the \u201cupper\u201d three right-hand dots) *followed immediately by*  \n- **dots 3-5-6** (a cluster of three dots: bottom left + right side two bottom dots)  \n\u2014 those two cells together form the \u201c%\u201d sign \u2828\u2834. ([brailleaustralia.org](https://brailleaustralia.org/wp-content/uploads/2013/10/UEB-Australian-Training-Manual-January-2022-Unicode.pdf?utm_source=openai))\n\nSo, it's a two-cell sequence:  \n**first cell:** dots 4,5,6  \n**second cell:** dots 3,5,6\n\n---\n\n## \ud83d\udccf Context rules you might need to know\n\n- Generally, the percent sign is **not spaced** from the number before it. E.g., **5%** would be written without a space: `\u283c\u2811\u2828\u2834`. ([brailleaustralia.org](https://brailleaustralia.org/wp-content/uploads/2013/10/UEB-Australian-Training-Manual-January-2022-Unicode.pdf?utm_source=openai))  \n- Make sure you are in a mode that recognizes **special symbols** in UEB (sometimes there is a symbol-mode or computer-braille mode required) so the device does not interpret these cells as contractions or lower-case letters. ([brailleaustralia.org](https://brailleaustralia.org/wp-content/uploads/2013/10/UEB-Australian-Training-Manual-January-2022-Unicode.pdf?utm_source=openai))\n\n---\n\nIf you tell me which device you\u2019re using (e.g. Brailliant, Focus, iPhone VoiceOver, Windows/NVDA, etc.), I can give you exact button combinations for your setup."
    },
    {
        "role": "user",
        "content": "%20no%20no%20%25%20sign%20the%20at%20sign%20in%20an%20email%20mail"
    },
    {
        "role": "assistant",
        "content": "To type the \u201c@\u201d symbol (commercial at sign) in Unified English Braille (UEB) using a braille display or braille input, follow this:\n\n---\n\n## \u2705 Braille for \u201c@\u201d in UEB\n\n- The \u201c@\u201d sign in UEB is represented by the braille cell: **\u2808\u2801** \u2014 that is, dots 4 followed by dot 1. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/ueb-and-computer-braille-entry-tips-for-hims-polaris-and-braillesense-6-notetakers?utm_source=openai))  \n- Sometimes shown or referred to as \u201c@a\u201d in UEB symbol tables. ([brailleauthority.org](https://www.brailleauthority.org/ueb/brailleprimer20080301.pdf?utm_source=openai))\n\n---\n\n## \ud83d\udd27 How to type it using a braille device or input\n\nIf your device lets you input braille cells directly (either via screen-reader in \u201cbraille input\u201d mode or on a refreshable braille display with keys), here\u2019s how:\n\n1. Make sure you're using **UEB mode** (not older EBAE or other braille codes). Many devices default to UEB. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/ueb-and-computer-braille-entry-tips-for-hims-polaris-and-braillesense-6-notetakers?utm_source=openai))  \n2. Then type the sequence:\n\n   - **Dot 4** (one cell)  \n   - Immediately followed by **Dot 1** (second cell) \n\n   That\u2019s **\u2808\u2801** together forming the \u201c@\u201d sign. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/ueb-and-computer-braille-entry-tips-for-hims-polaris-and-braillesense-6-notetakers?utm_source=openai))\n\n---\n\n## \u26a0\ufe0f Special notes & contexts\n\n- When writing email addresses, this \u201c@\u201d is used inline, just like in print. E.g., in **user@example.com**, the \u201c@\u201d would be \u2808\u2801 placed appropriately between the parts. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/ueb-and-computer-braille-entry-tips-for-hims-polaris-and-braillesense-6-notetakers?utm_source=openai))  \n- If using rules of contraction (literary braille / Grade 2), you generally still use the same \u201c@\u201d braille symbol for email addresses. UEB handles \u201c@\u201d directly; you don\u2019t need to switch into another mode just for that. ([pharmabraille.com](https://www.pharmabraille.com/wp-content/uploads/2015/10/guidelines_for_technical_material_2014.pdf?utm_source=openai))  \n\n---\n\nIf you tell me which device or screen reader you\u2019re using (for example, a Focus display, BrailleSense, iPhone with VoiceOver, Windows with JAWS/NVDA, etc.), I can give exact key-chord instructions for your situation."
    },
    {
        "role": "user",
        "content": "i%20also%20use%20leasey%20and%20dot%20four%20invokes%20leasey"
    },
    {
        "role": "assistant",
        "content": "It\u2019s understandable that this can get confusing! When you press \u201cdot 4\u201d and it invokes something called *Leasey*, it suggests that your device or screen reader has a command mode or a shortcut bound to dot-4. That\u2019s likely overriding typing the \u201c@\u201d symbol. I\u2019ll help you figure out what\u2019s going on, and how to type \u201c@\u201d without triggering that command.\n\n---\n\n## \ud83d\udd27 What \u201cLeasey\u201d Could Be\n\n- \u201cLeasey\u201d here probably isn\u2019t the property-management platform. It sounds like a mis-hearing or mis-display of a screen-reader voice announcing a command or mode when you press dot-4.\n- Many braille input/display systems use single dot chords (especially with dot 4) to switch modes, navigate, or issue commands. This behavior is common in iOS VoiceOver, Android accessibility, or specific display firmware. ([tripletaptech.org](https://tripletaptech.org/command-mode-braille-screen-input-for-ios-18/?utm_source=openai))\n- For example, in iOS 18\u2019s Braille Screen Input, \u201cpress dot four\u201d is the command to go to the next item while in \u201cCommand Mode\u201d. ([tripletaptech.org](https://tripletaptech.org/command-mode-braille-screen-input-for-ios-18/?utm_source=openai))  \n- In other devices, dot-4 + space or dot-4 alone might be mapped to a navigation or modifier function. ([aphtech.org](https://aphtech.org/rbd_doc.htm?utm_source=openai))\n\n---\n\n## \ud83c\udd94 What the \u201c@\u201d Sign Needs in Braille Input\n\nTo type \u201c@\u201d, you need to produce the UEB two-cell symbol:\n\n- First cell: dot 4 (\u2808)  \n- Second cell: dot 1 (\u2801)  \n\nTogether: **\u2808\u2801** = \u201c@\u201d in email addresses.  \n\n---\n\n## \u2699\ufe0f Why Dot-4 is Already Doing Something\n\nBecause pressing dot-4 is already tied to a different command, it can\u2019t be used as the start of the \u201c@\u201d symbol sequence in that context *unless*:\n\n- You\u2019re in a text-entry mode that accepts regular UEB input,\n- The command mode is off or overridden,\n- The system allows you to suppress or disable that dot-4 command binding.\n\n---\n\n## \ud83d\udca1 What You Can Try\n\nHere are ways to get \u201c@\u201d typed, depending on your setup:\n\n1. **Check if you are in Command Mode vs Text Input Mode**\n   - If in a mode where dot-4 commands navigate or control, try switching to text or input mode where full braille entry is accepted. For example, in iOS 18, \u201cCommand Mode\u201d is activated or deactivated manually. ([tripletaptech.org](https://tripletaptech.org/command-mode-braille-screen-input-for-ios-18/?utm_source=openai))\n\n2. **Use space plus dot combination**\n   - Many refreshable braille displays require you to hold down the **Space** key while pressing dots to form a chord. If you hold Space + dot-4, followed by Space + dot-1, it might allow input rather than invoking commands.  \n   - Some devices use the Spacebar with dot to type instead of signals. Check your device manual for \u201cbraille input chords\u201d or \u201cSpace + dot commands\u201d sections. ([aphtech.org](https://aphtech.org/rbd_doc.htm?utm_source=openai))\n\n3. **Disable or change the dot-4 shortcut**\n   - If your system settings let you change or disable the binding for the dot-4 command, doing that can prevent invoking the \u201cLeasey\u201d command when you press it.  \n   - This might be under Accessibility > Braille or Braille display settings.\n\n4. **Enter the two-cell \u201c@\u201d quickly as a single chained input if supported**\n   - Some software supports passing of both cells in one quick sequence so it\u2019s not interpreted as the dot-4 command alone.\n\n---\n\nIf you tell me which exact device or screen reader you\u2019re using (VoiceOver on iPhone/iPad, a specific refreshable display model, NVDA, JAWS, etc.), I can help you with the exact setting or key combination to make \u201c@\u201d work without invoking that command."
    },
    {
        "role": "user",
        "content": "leassey%20is%20a%20set%20of%20scripts%20that%20helps%20blind%20people%20use%20Jaws%20os%20dot%20four%20is%20needed%20but%20in%20a%20email%20body%20message%20I%20need%20to%20write%20an%20email%20address%20how%20can%20I%20achieve%20this%20with%20my%20brailliant%20BI40X"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s how you can write an \u201c@\u201d (at sign) in an email body when using JAWS + Leasey scripts and your HumanWare Brailliant BI 40X, despite dot-4 being tied to a Leasey command. I\u2019ll walk you through understanding the conflict, then show how to enter \u201c@\u201d, and finally how to adjust Leasey settings so dot-4 doesn\u2019t block that typing when you need it.\n\n---\n\n## Understanding the conflict: Leasey\u2019s dot-4 use\n\n- **Leasey** is a set of scripts in JAWS by Hartgen. It uses a special \u201cLeasey Key\u201d (the grave accent ` key, left of \u201c1\u201d) to start most commands. ([hartgenscripts.com](https://hartgenscripts.com/Leasey11Help/005_getting_started_with_leasey.html?utm_source=openai))  \n- Sometimes single keys or combinations (such as dot-4, probably meaning the command tied to the \u201cLeasey Key + \u2026\u201d) get intercepted by Leasey. If you're typing just dot-4 in your standard Perkins-style input while Leasey is running, Leasey may think you're initiating a Leasey command.  \n- The **Brailliant BI 40X** has a full 6-dot Perkins keyboard at the top for input (dots 1-6), plus a spacebar and Enter/Backspace keys. ([perkins.org](https://www.perkins.org/resource/so-many-braille-displays-which-one-right-my-student-part-one/?utm_source=openai))\n\n---\n\n## How to type \u201c@\u201d (at sign) in UEB / Computer Braille\n\nWhen typing in UEB or standard computer braille (6-dot, not contracted):\n\n- The \u201c@\u201d symbol is entered with dot-4 followed by dot-7 in **8-dot braille** tables, but in standard **6-dot/computer-braille**, \u201c@\u201d is typically dot-4, then dot-1 (i.e. \u2808\u2801). ([subvisionmilano.com](https://www.subvisionmilano.com/wp-content/uploads/2023/11/Manuale-utente-BI-40X-1.pdf?utm_source=openai))  \n- Since BI 40X supports both 6-dot UEB/computer braille tables, confirm you are using the Computer Table or a table that defines \u201c@\u201d as dot-4 + dot-1. ([subvisionmilano.com](https://www.subvisionmilano.com/wp-content/uploads/2023/11/Manuale-utente-BI-40X-1.pdf?utm_source=openai))\n\n---\n\n## Steps to enter \u201c@\u201d when dot-4 triggers Leasey\n\nHere\u2019s what to try when typing an email address in an email body using your BI 40X + JAWS + Leasey:\n\n1. Make sure your **braille input is set to a 6-dot computer or UEB table** that supports \u201c@\u201d as dot-4 + dot-1.\n   - On the BI 40X, you can switch tables or profiles; see the Manual\u2019s section on switching Braille Profile: `Enter + L` or `C4` shortcuts. ([files.ltalk.net](https://files.ltalk.net/download/Docs_Help/BrailliantBI40_Manual.pdf?utm_source=openai))\n\n2. In your email body field, type the \u201c@\u201d by inputting dot-4 and then dot-1:\n   - Hold dot-4 key (the \u201cupper right\u201d group dot).\n   - Release, then hold dot-1 key (\u201cupper left\u201d dot).\n   - This sequence should produce \u201c@\u201d in text mode, unless dot-4 is treated as a Leasey command.\n\n3. If pressing dot-4 alone invokes Leasey, try temporarily **disabling Leasey\u2019s \u201cLeasey Key\u201d binding** or suspending Leasey while entering email addresses.\n\n---\n\n## How to adjust Leasey so it doesn\u2019t block email address entry\n\nHere are some ways to reduce or disable Leasey\u2019s interference during typing:\n\n- **Leasey\u2019s settings include \u201cpunctuation\u201d and \u201ctyping \u00adecho\u201d modes**. There\u2019s a Leasey command to change how punctuation is handled: `Leasey Key then P`. This might help define how symbol inputs are treated vs commands. ([server1.hartgenscripts.com](https://www.server1.hartgenscripts.com/LeaseyHelp/AdditionalUtilities.html?utm_source=openai))  \n- When typing in text (like in an email body), ensure you are **not in a Leasey command mode**. Leasey commands always begin with the grave accent key (\u201eLeasey Key\u201c). If you don\u2019t press that key first, dot-4 alone shouldn\u2019t invoke Leasey\u2014unless there\u2019s a custom binding.\n\n- If there\u2019s **custom Leasey scripting** in your setup (some users add shortcuts that map dot-4 to specific functions), you could edit or remove that binding. You\u2019ll need the Leasey configuration files or speak to someone who installed Leasey for you to modify that.\n\n- As a workaround, **type the email address in a plain text editor or Notepad** where Leasey is less likely to intercept, then copy/paste it into the email. Leasey often doesn\u2019t interfere in plain text files. \n\n---\n\nIf you want, I can give you **exact keystroke combinations** for your setup (BI 40X + JAWS + Leasey) to disable the dot-4 Leasey shortcut temporarily, or to switch tables. Would you prefer that?"
    }
]