New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NVDA does not see document contents in Reader metro app #2498
Comments
Comment 1 by mdcurran on 2012-06-27 22:50 |
Comment 2 by erion (in reply to comment 1) on 2012-06-27 23:03
As far as I know Narrator is able to retrieve text with its own cursor. |
Comment 3 by jteh (in reply to comment 2) on 2012-07-09 05:15
My understanding is that not all Metro apps are HTML, but I could be wrong about this. Certainly, if the app is HTML based, it should already be rendered in browse mode. |
Comment 4 by erion (in reply to comment 3) on 2012-07-09 07:37
According to http://www.developer.com/net/considerations-for-building-windows-8-metro-applications.html a metro app can be developed also in XAML. I'm not sure if this is rendered to html though. I seem to recall that this is also used in WPF apps where it is. |
@josephsl, do you know if Metro apps have been officially superseded by UWD apps or whether they are still supported by Microsoft? |
I am closing this issue as abandoned, probably metro apps have significantly changed since this issue has been reported, and we don't have any updates on the current situation since years. Microsoft officially announced that that technology is now integrated into the UWP app environment. Many old metro apps have been discontinued and replaced by UWP apps, see for example metrotweet. Please open a new updated issue if there is any issue with a specific app and we can start the discussion from there. |
Reported by pitermach on 2012-06-27 20:27
Just open any PDF file in the new reader app in Windows 8. NVDA will say the document has focus, but will not read anything. This does work fine with Narrator, which suggests an issue with NVDA.
The text was updated successfully, but these errors were encountered: