[
    {
        "role": "user",
        "content": "I%20am%20running%20the%20latest%20Jaws%20screen%20reader%20wit%20the%20latest%20Windows11%20releaseand%20using%20Chrome%20as%20my%20main%20browser.%20When%20I%20am%20in%20the%20Audible%20Cloud%20player%20for%20example%2C%20I%20arror%20or%20tab%20past%20buttons%20that%20say%20Rewind%2030%20Seconds%20when%20I%20have%20my%20virtual%20cursor%20turned%20on.%20The%20buttons%20exhibit%20the%20correct%20labels%20of%20Rewind%2C%20Play%2FPause%2C%20FasForward%20etc%2C%20when%20I%20turn%20off%20my%20virtual%20cursor%20and%20navigate%20the%20page.%20This%20is%20drinv%20me%20nuts.%20How%20do%20I%20fix%20this%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s a detailed rundown of what\u2019s likely happening when you're using JAWS (with virtual buffer / virtual PC cursor on) in Chrome and browsing Audible\u2019s Cloud Player\u2014and how to fix or work around it. This gets a little technical\u2014it deals with different \u201ccursors\u201d in JAWS, forms vs. virtual mode, and how web apps sometimes obscure correct labels of buttons.\n\n---\n\n## What Might Be Causing Your Issue\n\nYou describe: when Virtual Cursor is turned **on**, moving past buttons (Rewind 30s, Play/Pause, etc.) via arrow/tab reads incorrectly or skips labels. When it's **off**, the labels come through properly.\n\nHere are key features & modes in JAWS involved in this:\n\n- **Virtual PC Cursor Mode / Virtual Buffer (\u201cbrowse mode\u201d)** \u2013 used for reading through web pages and general navigation. It *intercepts* your arrow keys and reads a virtual internal representation of the page. ([docs.bmc.com](https://docs.bmc.com/xwiki/bin/view/Service-Management/Innovation-Suite/AR-System/ars221/Developing-applications/Testing-and-deploying-applications/Making-your-application-accessible-Section-508-compatibility/JAWS-settings-for-the-Web/Cursor-types-and-Forms-mode-on-the-Web/?utm_source=openai))\n- **Forms Mode (or application mode)** \u2013 used when you interact with form inputs or interactive widgets; browser passes keystrokes through normally. ([docs.bmc.com](https://docs.bmc.com/xwiki/bin/view/Service-Management/Innovation-Suite/AR-System/ars221/Developing-applications/Testing-and-deploying-applications/Making-your-application-accessible-Section-508-compatibility/JAWS-settings-for-the-Web/Cursor-types-and-Forms-mode-on-the-Web/?utm_source=openai))\n- **Application Regions / Application Mode in web apps** \u2013 when parts of the site use JS/CSS to create custom controls; JAWS may switch into a mode where only certain navigation works as the site intends. This sometimes hides or overrides the Virtual Cursor behavior. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/what-is-application-mode?utm_source=openai))\n\nWhat likely happens with Audible's cloud player is:\n\n- With Virtual Cursor on, JAWS is in **browse mode**, reading text like a document.\n- Audible\u2019s buttons may use custom HTML/ARIA roles or control labelling that are only correctly exposed when the site is in \u201capplication mode\u201d or when focus / virtual mode is off. These custom roles sometimes override or suppress the default `aria-label` or button text when in browse mode.\n- When you turn off the Virtual Cursor (or toggle to pc cursor / Forms Mode), you allow the browser and the page\u2019s interactive widget behavior to take effect, and then JAWS reads the correct visible labels (like \u201cRewind 30 seconds\u201d, \u201cFast Forward\u201d etc.).  \n\nSo this is *not* a bug unique to your setup\u2014this is common behavior when web applications use custom controls or reroute key events in ways that Virtual Cursor doesn\u2019t always traverse correctly.  \n\n---\n\n## What You Can Do to Fix / Work Around It\n\nHere are steps to try, and some settings that might help:\n\n| Action | What to Do | Why it Might Help |\n|---|---|---|\n| **Toggle Virtual Cursor On/Off** | Press **JAWSKey + Z** (usually Insert + Z) to toggle Virtual Cursor. Try turning it *off* when in the Audible Cloud Player. | That allows your keyboard commands (like arrow/tab) to reach the web component in its \u201cinteractive\u201d mode. The correct labels may then be available. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/what-is-application-mode?utm_source=openai)) |\n| **Ensure Browser Focus is Correct** | Make sure the Audible Cloud Player has focus. Sometimes after loading, focus may be trapped elsewhere or not in the player control region. | If focus isn\u2019t where the player controls are, Virtual Cursor might read only surrounding text, not trigger button label speech. |\n| **Use Tab Navigation Instead of Arrow (in Browse Mode)** | When in Virtual Cursor mode, pressing Tab might better focus each interactive button and read its accessible name. | Tab focuses interactive elements as the page is set up; buttons generally get announced correctly when focused. |\n| **Check JAWS Verbosity / Advanced Settings** | Open Settings Center (JAWSKey+6), go to Web \u2192 HTML \u2192 Reading / Accessibility settings, and ensure button roles/labels and ARIA attributes are announced (verbosity settings high enough). | Sometimes labels are hidden if verbosity is low. Increasing verbosity can allow more detail. |\n| **Update JAWS / Chrome** | Ensure you\u2019re using the latest JAWS version *and* the latest Chrome build. | There have been bugs (Chrome updates breaking virtual PC buffer reading etc.) that are fixed in newer JAWS/Chrome versions. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/jaws-loss-of-virtual-pc-cursor-in-microsoft-edge-and-chrome?utm_source=openai)) |\n\n---\n\n## Possible Underlying Improvements (for Audible / Web Developers)\n\nIf you want Audible (or any site) to behave more consistently *without requiring users to toggle modes*, here are what good accessibility practices suggest:\n\n- Use **ARIA roles** properly on buttons\u2014for example `role=\"button\"` with a clear `aria-label` or ensure the visible text is exposed correctly to accessibility APIs. Invisible labels or decorative icons can be problematic.  \n- Avoid custom control scripts that suppress or replace native behavior in browse mode; interactive control state should be exposed both in application mode *and* browse/virtual buffer mode.  \n- Make sure button text (visible) matches the accessible name (`aria-label` or `aria-labelledby`) so screen readers don\u2019t read confusing names.  \n- Use landmark roles or application regions sparingly; only when necessary, and ensure fallback labeling is correctly supported.  \n\n---\n\n## What I Recommend Trying **Right Now**\n\nHere\u2019s what I\u2019d do step by step (you can try them in this order to see which helps):\n\n1. Open Audible Cloud Player in Chrome.\n\n2. Press **Insert + Z (JAWSKey + Z)** to turn **off** the Virtual Cursor. See if navigating with arrow keys or Tab now reads the correct labels for Rewind, Pause, Fast Forward etc.\n\n3. If that helps, use Tab to jump between buttons, instead of arrow keys in browse mode.\n\n4. If turning Virtual Cursor off breaks some parts of navigate, try turning it back on and instead focus the controls (click into the control region with mouse or Tab) so JAWS might recognize the control label.\n\n5. Open JAWS Settings Center (`JAWSKey + 6`) \u2192 search for \u201cVirtual PC Cursor\u201d or \u201cApplication mode\u201d \u2192 see what\u2019s set. Sometimes toggling \u201cUse Virtual PC Cursor for Windows Universal Apps\u201d helps. ([nelowvision.com](https://nelowvision.com/wp-content/uploads/2021/02/Software-Updates-2021-Versions-of-ZoomText-JAWS-Fusion-February-2021.pdf?utm_source=openai))\n\n6. Make sure Chrome is updated; check JAWS is up to date. If this issue is recent, it might coincide with a Chrome change. There have been specific Chrome / JAWS interactions fixed in recent updates. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/jaws-loss-of-virtual-pc-cursor-in-microsoft-edge-and-chrome?utm_source=openai))  \n\n---\n\nIf you like, I can also try to test this behavior myself (or check web dev resources) to see if this is an Audible bug vs. a JAWS/Chrome limitation, and maybe show you screenshots / examples. Would that be helpful?"
    },
    {
        "role": "user",
        "content": "I%27m%20lbind%20so%20screen%20shots%20owuld%20be%20useless."
    },
    {
        "role": "assistant",
        "content": "Thanks for clarifying. Since screen shots aren\u2019t helpful here, I\u2019ll focus on text-based ideas and settings that blind users can use to adjust what JAWS says. Based on what you've described and what I found, here are some additional things you can try, plus what might be going on under the hood.\n\n---\n\n## More Suggestions You Can Try (No Visual Needed)\n\n1. **Toggle Virtual Cursor / PC Cursor (JAWSKey + Z / Insert + Z)**  \n   When you're on Audible\u2019s cloud player page, turn Virtual Cursor **off**. This forces JAWS to use the standard, interactive mode; buttons are often labeled correctly here. Then navigate using Tab or Space/Enter to activate buttons.  \n   When you\u2019re done, you can turn the Virtual Cursor back on for general reading.\n\n2. **Use Tab Navigation**  \n   Even when the Virtual Cursor is on, Tab should move focus to interactive items (\u201cbuttons\u201d) and cause JAWS to read their accessible name. So try using Tab instead of arrow keys when you want to get accurate labels like \u201cRewind 30 seconds.\u201d\n\n3. **Make sure focus is inside the player**  \n   Sometimes after a page loads and streaming starts, focus stays outside the control bar. If you don\u2019t hear anything, you might be outside the control region. Press Tab repeatedly to bring focus into the control region of the audio player; then the labels should read correctly.\n\n4. **Check JAWS Quick Settings for \u201cSelect and Copy / Reading using virtual cursor\u201d**  \n   As noted in the JAWS loss of Virtual PC Cursor issue, there\u2019s a setting called \u201cSelect And Copy\u201d or a related setting where you can switch how screen highlight and virtual cursor behave. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/jaws-loss-of-virtual-pc-cursor-in-microsoft-edge-and-chrome?utm_source=openai))  \n\n5. **Check whether Audible is using role=\"application\" or custom ARIA/hiding visible labels**  \n   - If the player\u2019s control wrapper has `role=\"application\"`, JAWS treats that part of the page differently: likely leaving browse mode and entering application mode, which can change how it announces labels. ([support.freedomscientific.com](https://support.freedomscientific.com/support/technicalsupport/bulletin/1665?utm_source=openai))  \n   - If a button has `aria-describedby` pointing to hidden text or uses non-visible labels only, browse mode may read only the description, or suppress certain label parts. ([mit.edu](https://www.mit.edu/~rjc/aria/describedby.html?utm_source=openai))  \n\n   Unfortunately, as a user you can\u2019t fix Audible\u2019s code, but knowing this helps understand why behavior is different depending on mode.\n\n6. **Ensure your JAWS and Chrome are Fully Updated**  \n   There have been known bugs where Chrome updates break how JAWS reads the virtual buffer. These are usually resolved in newer versions. For instance, a known issue in Chrome 114 was fixed, and newer versions of JAWS have resolve related problems. ([training.vispero.com](https://training.vispero.com/chrome-114-breaks-web-page-reading-with-jaws-2021-and-earlier/?utm_source=openai))\n\n---\n\n## What\u2019s Likely Going On\u2014Why Labels are Missing in Browse/Virtual Cursor Mode\n\nHere\u2019s a guess at the technical cause, based on what\u2019s described in developer documents and accessibility reports:\n\n- Audible\u2019s controls might **hide visible text in favor of icons or use `aria-describedby`** or custom navigation scripts that confuse the reading order in virtual mode.\n- In Virtual Cursor / Browse Mode, JAWS ignores some interactive controls\u2019 visible labels if they are not part of the element\u2019s accessible name or are hidden. It might read only the `aria-describedby` or summary text, or skip parts altogether. Buttons might look fine visually, but screen readers rely on accessibility API (which draws from `aria-label`, `aria-labelledby`, button text, etc.). Only focus via Tab or turning off Virtual Cursor seems to trigger the correct accessible name. ([mit.edu](https://www.mit.edu/~rjc/aria/describedby.html?utm_source=openai))  \n- If the control region is marked `role=\"application\"`, JAWS may stop treating it as normal content and enter application mode. In that mode, arrow keys may be expected to behave like within an app\u2014some information may be suppressed unless focus or code explicitly raises it. ([support.freedomscientific.com](https://support.freedomscientific.com/support/technicalsupport/bulletin/1665?utm_source=openai))  \n\n---\n\nIf you agree, I can prepare a list of JAWS keystrokes and settings (with descriptions you can hear) that\u2019ll help you more easily switch modes and check what\u2019s being read. Would that be helpful?"
    }
]