[
    {
        "role": "user",
        "content": "I%20notices%20in%20a%20we%20page%20I%20need%20to%20page%20down%20but%20jaws%20is%20stopping%20I%20have%20to%20hi%20the%20pass%20thought%20key%20before%20pressing%20page%20down%20how%20can%20I%20fix%20that"
    },
    {
        "role": "assistant",
        "content": "It sounds like when you press Page Down on a web page, JAWS isn\u2019t passing that keystroke through\u2014you have to hit the \u201cPass\u2013through\u201d key (Insert+3 on the number row, or Caps Lock+3 if using the laptop layout) first. ([freedomscientific.com](https://www.freedomscientific.com/training/jaws/hotkeys/?utm_source=openai))  \n\nHere are things to check and ways to fix this so Page Down works without needing Pass-through every time:\n\n---\n\n## What\u2019s going on\n\nJAWS has different modes and behaviors:\n\n1. **Virtual Cursor (Browse Mode)**  \n   This is the default on web pages. Keys like Page Up / Page Down may be handled by JAWS\u2019s built-in navigation rather than sent directly to the page. It intercepts some keys. ([webaim.org](https://webaim.org/articles/jaws/?utm_source=openai))\n\n2. **Forms Mode / Focus Mode**  \n   When you\u2019re in a field (like an input box) or doing interactive elements, JAWS sometimes switches modes so that keystrokes go directly to that field rather than command navigation. But outside that, many keys are still managed by JAWS. ([support.freedomscientific.com](https://support.freedomscientific.com/support/technicalsupport/bulletin/1665?utm_source=openai))\n\n3. **Pass-through**  \n   This special command temporarily tells JAWS: \u201cLet the next keystroke go to the application/webpage normally.\u201d That\u2019s what you\u2019re using before pressing Page Down. The key is `Insert + 3` (number row) on most desktops, or `Caps Lock + 3` if using the laptop layout. ([freedomscientific.com](https://www.freedomscientific.com/training/jaws/hotkeys/?utm_source=openai))  \n\n---\n\n## How to fix so that Page Down works normally\n\nHere are a few options\u2014try one or more to see what works best:\n\n- **Enable \u201cPass Keys Through\u201d permanently or more automatically**  \n  Sometimes there's a setting or shortcut in JAWS that lets more keystrokes pass through without needing Pass-through each time. This might help if you're in a part of a web page (like embedded app/widgets) where Page Down isn't being forwarded. However, there isn\u2019t a global \u201calways pass all keys through\u201d setting for all pages\u2014JAWS expects some control so users don't activate things accidentally.  \n\n- **Change to \u201cRole=application\u201d in the website code** *(if you are a developer or webmaster)*  \n  Pages (or components) coded with `role=\"application\"` tell screen readers that the content is more like an app than a document. In \u201capplication\u201d mode, more keys are passed through to the browser/web app rather than being intercepted. If the site you\u2019re using is poorly coded or uses custom input widgets, this might cause Page Down or other keys to be blocked. ([stackoverflow.com](https://stackoverflow.com/questions/59056943/keydown-event-in-jaws-ie11-not-firing-properly?utm_source=openai))  \n\n- **Toggle Forms Mode manually**  \n  When you're in a form or interactive field, Forms Mode allows many keys to go through. Press `JAWS + Z` (Insert+Z or Caps Lock+Z depending on layout) to switch between Virtual Cursor mode and Forms Mode to test whether Page Down works. ([webaim.org](https://webaim.org/articles/jaws/?utm_source=openai))  \n\n- **Keyboard layout and JAWS modifier key setting**  \n  If your modifier (\u201cJAWS key\u201d) layout is switched in a way you did not expect (desktop vs laptop layouts), some shortcuts (like Pass-through) might be mapped differently or less accessible. Check:  \n  Settings \u2192 Options \u2192 Basics \u2192 Keyboard Layout and make sure you know whether your JAWS modifier is Insert or Caps Lock. ([unimelb.edu.au](https://www.unimelb.edu.au/accessibility/tools/testing-web-pages-with-jaws?utm_source=openai))  \n\n- **Update JAWS or switch browsers**  \n  Sometimes specific browsers or older versions of JAWS have bugs or incompatible behaviors. Updating JAWS might help. Also, testing Page Down in different browsers (Chrome, Edge, Firefox) may show whether it\u2019s specific to one. ([unimelb.edu.au](https://www.unimelb.edu.au/accessibility/tools/testing-web-pages-with-jaws?utm_source=openai))  \n\n---\n\nIf you tell me **which version of JAWS** you\u2019re using, and **what browser** (Chrome, Edge, Firefox, etc.), I can give you direct steps tailored for your setup."
    },
    {
        "role": "user",
        "content": "using%20edge%20and%20jaws%202026"
    },
    {
        "role": "assistant",
        "content": "Using Edge with JAWS 2026, the reason you're having to hit the Pass-through key before using Page Down is likely because JAWS is in **Virtual Cursor** mode (Browse/Read-only mode). In that mode, many keys (including Page Up / Page Down / Arrow keys) are captured by JAWS rather than being passed to the web page unless you either put JAWS in a different mode or disable the Virtual Cursor for the current context.\n\nHere\u2019s how to fix the issue so Page Down works more naturally:\n\n---\n\n## Key Concepts\n\n- **Virtual Cursor Mode**  \n  This is the default when reading web pages. Keys like Page Up / Page Down are handled by JAWS itself (navigating the virtual buffer) rather than being sent directly to the webpage. ([website-archive.mozilla.org](https://website-archive.mozilla.org/www.mozilla.org/access/access/qa/win-webcontent-jaws.html?utm_source=openai))\n\n- **Turning off Virtual Cursor**  \n  Disabling or toggling off the Virtual Cursor lets more keystrokes go directly to the page/content, which allows things like Page Down, custom key handlers, or app-embedded keyboard shortcuts to work normally. ([blindadrenaline.com](https://blindadrenaline.com/instructions/virtualCursor.html?utm_source=openai))\n\n---\n\n## How to Fix It in JAWS 2026 + Edge\n\nHere\u2019s what to try in your specific setup:\n\n1. **Toggle Virtual Cursor off**  \n   Press **JAWS Key + Z**.  \n   - *JAWS Key* is usually **Insert** (on full keyboards) or **Caps Lock** (if using the laptop layout).  \n   - So: **Insert + Z**, or **Caps Lock + Z**.  \n   Turning it off will allow most keys\u2014including Page Down\u2014to pass through directly. ([blindadrenaline.com](https://blindadrenaline.com/instructions/virtualCursor.html?utm_source=openai))\n\n2. **Switch Forms Mode / Applications mode**  \n   If you\u2019re interacting with a widget (e.g. a web-application, embedded map or interactive control), those components sometimes require being in Forms Mode or that the site marks the component with `role=\"application\"`. These roles tell JAWS to switch into a mode where keystrokes are passed through. If you can\u2019t change the site, turning off the Virtual Cursor usually works similarly. ([accessible-data-interfaces.com](https://www.accessible-data-interfaces.com/testing-accessibility-for-data-uis/assistive-technology-behaviour-differences/jaws-virtual-cursor-versus-forms-mode-in-data-grids/?utm_source=openai))\n\n3. **Check Quick Settings for Virtual Cursor behaviour**  \n   There\u2019s a setting in Quick Settings (JAWS Key + V) that controls how Virtual Cursor behaves when switching browser tabs or returning to the browser. If Page Down works in some tabs/pages but not others, the state may not be retained. Turning on the \u201cVirtual Cursor On/Off based on Browser Tabs\u201d or similar setting might help. ([sastltd.zohodesk.eu](https://sastltd.zohodesk.eu/portal/en/kb/articles/jaws-virtual-pc-state-not-remembered-when-returning-to-a-browser-hosted-web-app?utm_source=openai))\n\n4. **Keep JAWS up to date**  \n   In JAWS 2026, there were enhancements related to web automation (UIA support) and the virtual cursor. Ensuring you have the latest update means fixes for browser compatibility are applied. ([support.freedomscientific.com](https://support.freedomscientific.com/Downloads/JAWS/JAWSWhatsNew?version=17See&utm_source=openai))\n\n---\n\nIf you tell me whether your JAWS key is Insert or Caps Lock and whether the Page Down issue happens on *all* webpages or just some (maybe pages with custom web apps), I can guide you to the exact setting or mode switch for your case."
    }
]