New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 649628 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

JAWS doesn't read dynamic Html in chrome

Reported by sudhir.p...@gmail.com, Sep 23 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36

Steps to reproduce the problem:
1. Create simple html contains button
2. On click of button which will add another simple HTML(dropdown with div) in DOM.
3. Follow this when JAWS is running.

What is the expected behavior?
It should read the content focused.

What went wrong?
Its not reading the content, as it only reads the key pressed.

Did this work before? N/A 

Chrome version: 53.0.2785.116  Channel: stable
OS Version: 6.2 (Windows 8)/Window 10
Flash Version: Shockwave Flash 23.0 r0

Tried with JAWS 16 and 17.
Added sample file.
 
New Text Document.html
696 bytes View Download

Comment 1 by tkent@chromium.org, Dec 9 2016

Components: UI>Accessibility
Cc: lpalmaro@chromium.org nek...@chromium.org chaok@chromium.org
Status: Available (was: Unconfirmed)
Thanks for reporting this.
I am not sure if this is the bug that is described, but if I use the following HTML snippet and I press the button, the div's text doesn't appear in Jaws' virtual buffer. In order for it to appear, I have to refresh the buffer using JawsKey+Esc.
data:text/html,<button onclick="var div = document.createElement('div'); div.textContent = 'focus'; document.body.appendChild(div);">button</button>
Please correct me if you are envisioning something more complex than what the above code does.

Labels: NewComponent-Accessibility-Compatibility
Labels: NewComponent-Accessibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Labels: triage-nektar

Comment 8 by leberly@google.com, Aug 24 2017

Chrome Version: 60.0.3112.101 (Official Build) (64-bit) (cohort: Stable)
OS: Win 10 Enterprise Version 1607 build 14393.1593
Screen reader: JAWS 18.0.4101

Hi, I was not able to reproduce your bug under the above conditions. I am recommending that this be resolved. Please reopen this issue if you have any questions or concerns. I used these steps: 

Create simple html contains button per your example code that you attached
Jaws says “Click here to open Button”
Press enter to invoke button, text appears
JAWS reads “First option” as expected
Repro rate: 0/5 times

Labels: -Via-Wizard -triage-nektar
Status: WontFix (was: Available)

Sign in to add a comment