The same goes with websites. Just because you add things in like skip nav and access keys, you shouldn't automatically assume that everybody will use them, or even know what they mean.
I don't necessarily think it's a naming issue, although as a number of people have pointed out, JAWS pronounces content differently depending on context. I think it's just that, while in the web accessibility community skip nav is a recognised convention, it hasn't seeped into the screenreader community at large yet.
It's a bit like adding a home link to the logo of a site. Most web designers do this by default, but even now, there are loads of web users who are unaware of this convention. If a more experienced web user was to show then this convention they would no doubt start using it. However generally web users stick to their own patters until there is a compelling need to deviate from them.
Maybe we should start putting a para about skip nav links in our accessibility statements along with a description of our accesskeys, compliance goals etc.
Andy Budd
http://www.message.uk.com/
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
