Ted Drake wrote:
> Here's something else I noticed, I use teh [s} to signify the access > key. It looks stupid in fangs, openbracket s close bracket which is what > Jaws would do. So, I think I'm going to change it to "Access Key = S"
Don't forget that a lot of JAWS' output depends on the user's chosen verbosity settings. Don't take fangs' - or any other tool's - output to be the most accurate representation of how real screenreader users would experience your site.
In an ideal world, screenreaders would tap into the markup (or whatever the web browsers makes available - in many cases even the complete DOM) and expose them to the user in a sensible manner...and, surprise surprise,many of them already do. Again possibly dependent on specific user settings, JAWS will announce accesskeys based on the accesskey attribute. No need to make it doubly explicit in things like the link title (for screenreader users , anyway; those who don't have a screenreader, but could benefit from accesskeys - e.g. users with mobility impairments, or in many cases *all* users that frequent the site regularly and could do with smarter ways to go about their business in a more efficient manner - will still need some mechanism that exposes the accesskey to them...CSS-generated content, for instance.
Patrick H. Lauke p.s.: this should really be a new thread... -- _____________________________________________________ re�dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.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 ******************************************************
