Quoting Andrew Ingram <[EMAIL PROTECTED]>:
One of the points in accessibility checks is that information conveyed using colour is also conveyed without. The most common way of doing visited links is to have them be a slightly different colour. It's my opinion that in a purely visual sense (because I don't know how screen readers announce visited links) this approach is inaccessible.
Screen readers would normally announce whether a link is "link" or "visited link" (at least I recall my old version of JAWS doing so).
I'd tend to agree in principle, but I would suggest that, unless a site is monstrously large and uses cryptic link text that differs from page to page, it wouldn't be a complete accessibility hurdle for a user if they didn't perceive the difference between visited/non-visited links. It's more of a nice usability feature than an accessibility one...though, if your design allows for it, it's certainly something that you could look at working around, going the extra mile to accommodate users with colour blindness or similar.
I'd imagine there'll be some votes for bold/normal
problem here is that, if these links are part of the main page content, inline in a paragraph for instance, the change from bold to normal may trigger some content reflow as the link gets activated. If it's an in-page link, this will be even more visible (as the bold link text is switched to normal, it takes up less space, so the rest of the paragraph and following content "butt up" to fill the space).
underline/normal
Shouldn't really remove the underline if, again, the link is part of a para of text or similar
inversion of background and foreground colour accessible?
That could work, but might look a bit heavy-handed.
fancy checkbox images (but obviously requires images which raises another issue)
Not for colour blindness. As mentioned above, screen readers would cope fine on their own either way. So, the only potential issue is the usual "css on/images off" scenario which, frankly, I have got little time for (if "power users" decide to go for that, then they should expect their experience to be slightly different and some possible usability features lost)
P -- Patrick H. Lauke __________________________________________________________ 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 __________________________________________________________ Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __________________________________________________________ ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
