Tested in chrome # 56.0.2924.87 and Canary #58.0.3026.0 on win 10.0.Tested with chrome vox and its working fine. Please find the screen cast for your reference.

@ mblsha: Could you please let me know if i have missed anything and if possible, provide us with a NVDA screen reader extension URL of the issue which would help us to triage the issue further.

Thanks in Advance.

Deleted: 694605.mp4 2.3 MB

	694605.mp4 2.3 MB View Download

NVDA is not an extension, it's an app for Windows: https://www.nvaccess.org

I tried to record a screencast, but it's kinda difficult to capture application's sound. If you would be unable to reproduce, please advise which app should I use to record a screen cast.

As per comment #4 installed the NVDA Reader and tested in chrome # 56.0.2924.87 and Canary #58.0.3026.0 on win 10.0 and not able to reproduce the issue.Please find the screen cast for your reference.

@ mblsha: Could you please let me know if i have missed anything and if possible, please create new profile without extension and apps.Recheck once and let us know the observation of the issue which would help us to triage the issue further.

Thanks in Advance.

Deleted: 695605.mp4 1.6 MB

	695605.mp4 1.6 MB View Download

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b1d3174a5e465867b3ae541ba545a47e11ace4b2

commit b1d3174a5e465867b3ae541ba545a47e11ace4b2
Author: dmazzoni <dmazzoni@chromium.org>
Date: Mon Mar 20 18:09:53 2017

Accessible bounds should include device scale factor on Windows.

When reporting the bounding box of an object from the web
via an accessibility API on Windows, we need to take the device
scale factor into account. Other platforms either don't need this
(Mac) or already take it into account elsewhere (Android).

BUG= 694605 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2759903002
Cr-Commit-Position: refs/heads/master@{#458120}

[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/accessibility/browser_accessibility.h
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/accessibility/browser_accessibility_manager.cc
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/accessibility/browser_accessibility_manager.h
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/accessibility/browser_accessibility_manager_unittest.cc
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/accessibility/browser_accessibility_win.cc
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/accessibility/browser_accessibility_win.h
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/accessibility/hit_testing_browsertest.cc
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/frame_host/render_frame_host_impl.cc
[modify] https://crrev.com/b1d3174a5e465867b3ae541ba545a47e11ace4b2/content/browser/frame_host/render_frame_host_impl.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a62e4692a41ec371137ad9bd94b1b51b91e7192b

commit a62e4692a41ec371137ad9bd94b1b51b91e7192b
Author: dmazzoni <dmazzoni@chromium.org>
Date: Mon Apr 03 21:51:50 2017

Accessible bounds should include device scale factor on Windows (again)

The previous patch (https://codereview.chromium.org/2759903002)
attempted to fix this bug, but I unknowingly tested it with buggy AT.

I've now determined that inspect.exe, Narrator, and ZoomText all seem
to be doing the right thing. This patch fixes the bounding boxes for
those three tools.

Others, including NVDA with the focus highlight add-on, and
accExplorer, show the wrong bounding box and should be fixed to
be dpi-aware.

BUG= 694605 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2789963002
Cr-Commit-Position: refs/heads/master@{#461547}

[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/content/browser/accessibility/browser_accessibility_manager.h
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/content/browser/accessibility/browser_accessibility_manager_win.cc
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/content/browser/accessibility/browser_accessibility_manager_win.h
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/content/browser/accessibility/browser_accessibility_win.cc
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/content/browser/accessibility/browser_accessibility_win.h
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/content/browser/accessibility/hit_testing_browsertest.cc
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/ui/views/accessibility/native_view_accessibility_base.cc
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/ui/views/accessibility/native_view_accessibility_base.h
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/ui/views/accessibility/native_view_accessibility_win.cc
[modify] https://crrev.com/a62e4692a41ec371137ad9bd94b1b51b91e7192b/ui/views/accessibility/native_view_accessibility_win.h

Removing the Needs-Bisect as the fix has landed.

dmazzoni@: Could you please mark this as Fixed if there is no further work to be done here.