On Friday, June 2, we reported an issue with Google Chrome Version 114 and JAWS 2019, 2020, and 2021 where web page content cannot be accessed by the Virtual buffer when initially launching the browser. For more on this issue, visit this Technical Support Bulletin.
Microsoft has now released Edge Version 114. For most people, Edge is working well when accessing web pages with all versions of JAWS; but symptoms like those outlined on Friday have occurred with JAWS versions in Microsoft apps like Teams and OneDrive where Edge is used to display data. The content displayed in the JAWS Virtual buffer cannot be accessed with the JAWS Virtual PC Cursor, resulting in silence when navigating with the arrow keys.
This issue may also occur in Microsoft Office 365 applications where Edge displays data. When using Teams Preview (an option that allows users to test and explore upcoming features), the Virtual PC cursor is not active by default. When you press the TAB key or use keystrokes like CTRL+1–6 on the number row to navigate in Teams, you will not receive spoken feedback.
Here’s What to Do
The best workaround is to activate the JAWS Cursor, then activate the Virtual PC Cursor using one of the following methods:
Note: When in an app screen or when using a feature that displays content like a web page in the JAWS Virtual Buffer that cannot initially be accessed by the Virtual PC Cursor, the PC Cursor will be active.
- If you are using a keyboard with a numpad, press NUMPAD MINUS to activate the JAWS Cursor, then press NUMPAD PLUS to activate the Virtual PC Cursor.
- If you are using a laptop without a numpad, press CAPS LOCK+P to activate the JAWS cursor, then CAPS LOCK+SEMICOLON to activate the Virtual PC Cursor.
The page content should now be readable with the Virtual PC Cursor, though you may need to press the TAB key once to access it.
This workaround will remain in effect for each app until you restart it.
We will continue to post updates as they become available. If you have any questions or need assistance, access this Technical Support Bulletin for the latest details, or send an email to firstname.lastname@example.org.