JAWS reads stale content from a web page that does not exist
Job Access With Speech (JAWS) software continues to read data from previously visited web pages when it is on an entirely different web page.
Steps to Reproduce
1. In an application flow, create several UI screens with buttons. Button 1,2,3 on screen 1 and buttons 4,5,6 on screen 2.
2. Create a work object at runtime. Arrive at screen 1.
3. Have JAWS reader show buttons with INSERT + F5.
4. You should see...Buttons 1,2,3 in JAWS.
5. Create a new work object. Go through the flow normally to screen 2.
6. Run JAWS on screen 2....: INSERT + F5.
7. JAWS should read buttons 4,5 and 6 only. Instead it is reading buttons 1,2,3, as well.
The root cause of this problem is software use/operation error. JAWS provides access to web pages by taking a copy of the DOM of the page displayed in the web browser and storing it in a “virtual buffer”. It is this copy that the user interacts with when browsing. This buffer needs to be refreshed manually while navigating from screen to screen to avoid stale web page data. If the PegaWAI framework is used, there is logic in place which prompts the user through a popup message to refresh the buffer when navigating from screen to screen.
This issue is resolved through the following local change:
User needs to remember to flush out the JAWS buffer from screen to screen to avoid getting into such an issue by hitting INSERT + ESC.