Why doesn't narrator report itself as a screen reader to windows?
Hi, I'm trying to detect if a screen reader is attached to my application so that I can improve the experience for blind and low vision users. I'm using this win32 api (http://msdn.microsoft.com/en-us/library/ms724947%28VS.85%29.aspx), and specifying SPI_GETSCREENREADER as the uiAction. Call looks something like this: bool isScreenReaderActive() { int iAction = 70; // SPI_GETSCREENREADER constant; int iParam = 0; int iUpdate = 0; bool result = false; bool bReturn = SystemParametersInfo(iAction, iParam, &result, iUpdate); return (bReturn && result); } If JAWS is running, or for that matter the magnification utility, this API reports that a screen reader is attached. However, if I only have the built in screen reader running (MS Narrator), this API reports that no screen reader is attached. Is this really happening? Did you guys really decide not to report the built in screen reader as a screen reader?
September 28th, 2010 9:11pm

Hi Andrew, I think MSDN Windows Native Development Forums is the better resource to post this question. JPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2010 3:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics