I suspect you are correct. I’ve noticed that some pages experience the problem worse than others. some pages have links that can take multiple attempts of arrowing or tabbing on and off before Window Eyes reads the link properly. While it isn’t absolute, I’ve noticed that pages with a lot of scripts are more problematic, even using Firefox and No Script rather than IE without No Script which are the only browsers I have to work with doesn’t seem to improve things, no matter how many scripts I forbid.
Thanks, chris From: Dave Bahr Sent: Sunday, December 21, 2014 3:47 AM To: Chris ; [email protected] Subject: Re: Odd quirk, beta not reading first link when arrowing down or tabbing Yes, I have noticed all the same issues you report. I think it also has to do with the acessibility features of the coding of the page, but that's a pure guess since I have no expertese in that area. On 12/21/2014 2:50 AM, Chris wrote: Has anyone else noticed this? Window Eyes beta 2 is often not speaking the first link encountered when I navigate to a heading, table or list and start down arrowing or tabbing. For example, at Amazon, I navigate to the heading Amazon Prime to click on the link that will filter out all non Prime eligible items. If I arrow or tab past it and then up arrow or shift tab back, it reads fine. If the first link is the first item in a heading or other group, like search results in Google, the links will be read. But in these cases, arrowing through the items doesn’t read the link. If I down or up arrow through the search results I only get URLs when encountering links. I think they are the URLs corresponding to the links read when navigating by heading, but have not tried clicking on one to try. I have been experiencing a major tendency of Window Eyes to read URLs instead of links pretty much all of the time since beta 1, I get the link read by arrowing or tabbing off and back o n the link. Perhaps the latter Google issue is part of that problem. If so, Google is actually performing better since this only occurs with navigating with arrow keys while everywhere else, it happens with use of arrow keys and tab. With the URL reading issue I have tried turning off reading of tool tips with no effect. Perhaps another setting is responsible, but I don’t know what setting that might be. Neither of these are major bugs. They are more irritants than anything else, but I am still hoping that they might be fixed or that I might figure out the right setting to change. I have had mixed results fixing minor annoyances by changing settings. I still haven’t been able to figure out a way to get tables read the way I preferred them read with past versions of Window eyes. I cant get it to read “table 1”, “table 2” and so on as I navigate instead of “table 3 rows 2 columns” or whatever number of rows and columns. Anyway, I am really liking a lot of the changes so far and am looking forward to the release version. I just am still hoping that, in addition to all of the big bugs getting squashed, perhaps some of the annoying gnats might get knocked out of the air before that release happens. Regards, chris If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
