David Poehlman wrote: "I wonder if following the guidelines for coding pages for safari would make a difference."
With an issue of this type, you are not going to get traction asking for browser specific coding. Even coding for a particular screen reader is not a good idea, both should follow the standards.
As Access Curmudgeon suggested, Safari is a very standards aware browser, but the weak link in the accessibility chain here is Voiceover. It could be that Safari doesn't provide the hooks Voiceover needs, but either way it is something for Apple to sort out, not web authors.
Kind regards, -Alastair
