[
    {
        "role": "user",
        "content": "How%20do%20I%20fix%20the%20way%20jaws%20announces%20windows%20in%20its%20window%20list%20pressing%20insert%2Bf10"
    },
    {
        "role": "assistant",
        "content": "If when you press INSERT+F10 (or CAPS LOCK+F10 on a laptop layout) in JAWS and the \u201cWindow List\u201d dialog doesn\u2019t read out information the way you expect\u2014or announces too much or too little\u2014you can change how JAWS announces things in a couple of settings. Here are steps to adjust what's announced, what you\u2019ll need to check, and where settings have changed in recent versions.\n\n---\n\n## What the Window List normally announces\n\nBy default, the Window List shows all currently open windows; when you open it (INSERT+F10), JAWS will read out the titles of open windows, possibly with information like window status (maximized, minimized), and sometimes with position counts (\u201c1 of 5\u201d, \u201c2 of 5\u201d). ([freedomscientific.com](https://www.freedomscientific.com/training/jaws/hotkeys/?utm_source=openai))\n\n---\n\n## How to change what's announced\n\nThere are two main settings that control what\u2019s spoken in the Window List or similar lists:\n\n1. **Verbosity settings**  \n   These control how chatty JAWS is in different contexts (web, application, etc.). Particularly relevant are settings like whether to announce window status or position in the list. ([dsurf.net](https://dsurf.net/custom-jaws-preferences-and-settings/list-box-position-and-count/?utm_source=openai))\n\n2. **\"Announce position and count when navigating lists\"**  \n   This specific option makes JAWS say things like \u201c2 of 4\u201d when moving through a list. It affects both the Window List dialog and other list-like dialogs or listview controls. ([dsurf.net](https://dsurf.net/custom-jaws-preferences-and-settings/list-box-position-and-count/?utm_source=openai))\n\n---\n\n## Steps to adjust or fix\n\nHere\u2019s how you can modify how the Window List behaves when you press INSERT+F10:\n\n1. **Open the Settings Center**  \n   - Press **INSERT+F2**, choose **Settings Center**. ([dsurf.net](https://dsurf.net/custom-jaws-preferences-and-settings/list-box-position-and-count/?utm_source=openai))\n\n2. **Get the default settings if you want the changes global**  \n   - Press **CTRL+SHIFT+D** inside Settings Center to load the Default settings file. ([dsurf.net](https://dsurf.net/custom-jaws-preferences-and-settings/list-box-position-and-count/?utm_source=openai))\n\n3. **Search for \u201cposition and count\u201d**  \n   - In the search box, type \u201cposition count\u201d or \u201clist box announce position\u201d. You're looking for something like *Announce Position and Count when navigating in lists*. ([dsurf.net](https://dsurf.net/custom-jaws-preferences-and-settings/list-box-position-and-count/?utm_source=openai))\n\n4. **Disable or enable as needed**  \n   - If you want fewer announcements (no \u201c1 of 5\u201d, etc.), uncheck that box.  \n   - If you want status (like \u201cwindow is maximized/minimized\u201d) to be spoken, there may also be separate options in **Verbosity** or **Windows event notifications** to do with how Windows accessible events are announced. ([support.freedomscientific.com](https://support.freedomscientific.com/downloads/jaws/PreviousFeatures?version=2021&utm_source=openai))\n\n5. **Check in Quick Settings first (optional)**  \n   - Sometimes it\u2019s easier to test things without making them permanent. You can try **INSERT+V** (Quick Settings) when inside an application to change verbosity for that app. If the behavior improves in that app, then make a permanent change in Settings Center. ([support.freedomscientific.com](https://support.freedomscientific.com/downloads/jaws/PreviousFeatures?version=2021&utm_source=openai))\n\n---\n\n## A few sanity checks\n\n- Make sure you remember whether you\u2019re using INSERT as the JAWS key or you swapped it with CAPS LOCK. The Window List shortcut is INSERT+F10 (or CAPS LOCK+F10 on the laptop layout). If your JAWS key isn\u2019t what you think, the command may act differently. ([freedomscientific.com](https://www.freedomscientific.com/training/jaws/hotkeys/?utm_source=openai))\n\n- If you recently updated JAWS, it\u2019s possible behavior changed. Some settings, especially those around accessible events or notifications, have been modified in recent versions. ([support.freedomscientific.com](https://support.freedomscientific.com/downloads/jaws/JAWSWhatsNew?utm_source=openai))\n\n---\n\nIf you tell me:\n\n- what you *are* hearing now when you press INSERT+F10 (what exactly it says, e.g. \u201cwindow list dialog, 5 open windows, window A, minimized, window B\u2026\u201d)  \n- and what version of JAWS you have  \n\nI can give you more targeted commands to adjust or even custom scripts if needed. Do you want me to walk through based on your current version?"
    },
    {
        "role": "user",
        "content": "No%2C%20it%20does%20not%20make%20sense%20why%20it%20is%20saying%20parts%20of%20window%20titles%2C%20for%20example%20my%20teams%20chat%20window%20says%20calendar%20even%20though%20I%20am%20not%20in%20the%20calendar"
    },
    {
        "role": "assistant",
        "content": "If JAWS is announcing parts of a window title that don\u2019t reflect what you actually see (for example, it says \u201cCalendar\u201d when you're in a Teams chat), it\u2019s likely related to how Teams structures its windows or how the title bar is being updated. Sometimes the *accessibility name* (which JAWS uses) is different from what\u2019s visually in view. Here are things to try to fix or work around this, plus why it might be happening.\n\n---\n\n## Possible causes\n\n1. **Teams uses a combined title bar**  \n   Microsoft Teams often includes dynamic content in the title bar. For example, even if you're in Chat, the title might still contain \u201cCalendar\u201d (or a navigation reference) as a part of the window title or accessibility name. This can be a scripting or labeling issue inside Teams itself.\n\n2. **Old or conflicting scripts**  \n   If you or your organization have custom JAWS scripts for Teams\u2014or any version difference\u2014those can produce unexpected title announcements. For example, Teams\u2019 scripts try to include things like the app area (Chats, Calendar, etc.) when you press certain commands. ([dlee.org](https://dlee.org/teams/?utm_source=openai))\n\n3. **Reports of Teams stating \u201c(no title)\u201d or wrong title**  \n   Many users have filed bugs where meeting chats say \u201c(no title)\u201d even though there *is* a title. This suggests Microsoft\u2019s internal system is sometimes faulty or behind in updating that accessible name. ([github.com](https://github.com/MicrosoftDocs/msteams-docs/issues/4857?utm_source=openai))\n\n---\n\n## What you can try to fix it or work around\n\n1. **Confirm Teams is up to date**  \n   Make sure you're using the latest version of Microsoft Teams; these title issues are often addressed in updates. Also check whether you're using the desktop app vs. browser\u2014behavior might differ.\n\n2. **Check for updated or custom JAWS scripts for Teams**  \n   There\u2019s a detailed guide (\u201cUsing the JAWS Scripts for Microsoft Teams\u201d) that outlines how window titles are handled in different Teams views. Ensuring you're using the latest scripts can help correct bad or stale naming. ([dlee.org](https://dlee.org/teams/?utm_source=openai))\n\n3. **Use the \u201cSay Window Title\u201d command**  \n   Press INSERT+T (or CAPS LOCK+T depending on your JAWS key setup) when Teams is active to hear the title JAWS currently sees. That helps determine if the wrong part is embedded in the title or if the error is coming from Teams. (This is generally how you troubleshoot title issues in JAWS.) ([srt.csb-cde.ca.gov](https://srt.csb-cde.ca.gov/jaws/jaws-lesson-1.3.html?utm_source=openai))\n\n4. **Report the issue to Microsoft**  \n   If the title or accessibility owner is wrong, it's likely a bug in Teams. Microsoft has an issue tracker (as seen with chats saying \u201c(no title)\u201d) and they do release fixes. Reporting the problem with your exact version helps. ([github.com](https://github.com/MicrosoftDocs/msteams-docs/issues/4857?utm_source=openai))\n\n5. **As a workaround, silence or ignore parts**  \n   While you probably can\u2019t fully avoid this if it\u2019s built into the code, you could set JAWS to be less verbose in certain contexts (e.g., turn off status announcements) so those extra title parts don\u2019t distract as much.\n\n---\n\nIf you tell me which version of Teams you\u2019re using and whether it\u2019s the desktop app or the web version, I can check whether there's a known fix for *your* specific version. Do you want me to look that up for you?"
    }
]