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
Windows Update in Windows XP some links not spoken as links or in elements list #1330
Comments
Comment 1 by jteh on 2011-01-22 22:14 If we want to act like Firefox, we should also treat the presence of the onClick attribute as indicating that this is a link. |
Comment 2 by briang1 on 2011-01-23 12:50 Here is what I think is going on here. In the corrective action for spurious link indication the spurious indication of a link at these points was removed. it was this indication that made it look like it was working in 2010.2. Here is a log fragment from 4014 IO - speech.speakText (11:54:20): Here is the same for a current snap 4036 I've expanded the key pressings to show the elements list has no links for the missing ones and also to show on IE that the links do not register. They do work but nothing is spoken apart from their list info. IO - speech.speakText (12:13:06): If its of any use this snap looks like this when cursored onto the hardware link. INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (12:21:12): I did not do this for snap 4014, sorry, but 2010.2 looked like this. Interestingly, link is spoken on the first character of the word in 2010.2, hardware in this case, but its really hard to tell what its actually seeing as I said in my intro. Any other tests I can do? But I suspect that only really works for XP and of course not in Firefox! |
Comment 3 by jteh on 2011-01-23 13:24 |
Comment 4 by jteh on 2011-01-23 16:33 |
Comment 5 by briang1 on 2011-01-23 17:56 Changes: |
Comment 6 by briang1 on 2011-01-23 18:07 IO - speech.speakText (18:00:28): |
Comment 7 by jteh on 2011-01-23 18:09 Now, if they showed up as clickable, we could work around this one too, but they don't, so there's probably nothing we can do. Do you have another screen reader you can test with (even if a demo)? Do they show up as links there? Tech note: if they are in the tab order, maybe they're setting the tabindex attribute. Need to check this. |
Comment 8 by briang1 on 2011-01-23 18:24 |
Comment 9 by briang1 on 2011-01-23 18:40 Webbie output. which seems to be able to see the links.. Link: Microsoft Update Home However, Web formater cannot it seems.. Page Microsoft Update http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us ] Beta Software ] Find hardware support ] I'm saying nothing about IE seems to have some strange, features... |
Comment 10 by jteh (in reply to comment 9) on 2011-01-23 18:47
And I'll wager it also sees links where there aren't really links in some cases, just like NVDA did before we fixed it. :) The User Guide ones may not show up, as they were empty, but there are ways to make those weird not-links not empty. |
Comment 11 by briang1 on 2011-01-23 19:39 |
Comment 12 by jteh on 2011-02-04 06:55 If a way can be found to distinguish these from other spurious links, this can be reopened. However, it probably won't be fixed for 2011.1. |
Attachment links not being recognized by NVDA in some emails.eml added by briang1 on 2011-02-13 19:27 |
Comment 13 by jteh on 2011-02-16 02:53 |
Comment 14 by briang1 on 2011-02-17 18:30 Changes: |
Comment 15 by mdcurran on 2011-02-18 05:20 |
Comment 16 by jteh on 2011-02-20 20:11 |
Reported by briang1 on 2011-01-22 16:36
Ahem, suspect this regression introduced by fix for my mshtml ticket a few days ago.
Basically, to reproduce.
Go to windows update in windows xp (I used ie7) select custom and wait for it to resolve the page. Go to top of page and cursor odown till you encounter the list of updates either under software or hardware, or by type further down. These are links, and work as links but link is not spoken even if you tab there or cursor over them or look in elements list.
This works in 2010.2.
The text was updated successfully, but these errors were encountered: