Screenreaders and internal links?
Home / Site Building & Testing / Screenreaders and internal links?
Anybody have experience with screen readers not reading the target text after clicking an anchor link to an element with an ID?
For example, I have a page with "skip to content" link. The link is:
| Code: |
| <a href="#maincontent">Skip to main content</a> |
The element it point to is this:
| Code: |
| <p id="maincontent">I am the main content</p> |
I find with all combinations of browsers and screenreaders that I get intermittent results. Sometimes the screen reader reads "I am the main content" after clicking the link and sometimes not.
I have tried IE8/JAWS10, IE8/NVDA, FF/JAWS10, FF/NVDA.
What's going on?
Share: 
It's an hasLayout issue in IE. Only elements having this occult property will receive focus in IE.
Share:
In Firefox, we have a known bug that, if you activate a Same Page link twice on the same page, screen readers will only be notified of this focus jump the first time. This has been fixed in Firefox 3.next, and we've requested that this be allowed to also land in Firefox 3.6.x soon, but no final decision has been reached. You should see this working once we have fixed this issue, with both JAWS and NVDA.
Sorry for the inconvenience!
Share:
Thanks for the responses Martin and Marco, and a warm welcome to the forum!
Hope this has answered your query kahunacohen - welcome to you too
_________________
James Coltham - Local gov web manager by day, web and accessibility blogger at lunchtime, freelancer by night. Tweets at @prettysimple.
Share:
Thanks for the info! Glad to be on this site now. I have spent some time in the ARIA google group before, but nice to find this more general forum.
Share:
| MarcoZehe wrote: |
| In Firefox, we have a known bug that, if you activate a Same Page link twice on the same page, screen readers will only be notified of this focus jump the first time. This has been fixed in Firefox 3.next, and we've requested that this be allowed to also land in Firefox 3.6.x soon, but no final decision has been reached. You should see this working once we have fixed this issue, with both JAWS and NVDA. |
MarcoZehe,
Do you have the bug number for that, by chance? (I was just thinking that I might add myself to the CC list on that bug so as to follow along with its progress.)
Share:
| Alex Bischoff wrote: | ||
Do you have the bug number for that, by chance? (I was just thinking that I might add myself to the CC list on that bug so as to follow along with its progress.) |
Sure! It's bug 437607. As you can see, the patch for Firefox 3.6 has an approval flag for platform version 1.9.2.3, which translates to Firefox 3.6.3, which is currently in development.
Marco
Share:
Page 1 of 1
All times are GMT
You cannot post new topics in this forumYou cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum