Ah, see, this is why I do usability, not accessibility; you'd have thought by now they'd combine, but apparently not.
I had no idea screenreaders didn't automatically read title text, and was also unaware of keyobard navigation not displaying it; that's a weird issue I'd have thought would be resolved.
Definitely agree it should be explained in some way, and we'd need to ensure that people don't assume it'll be read. But it's there to give extra info for those interested; it displays on mouse hover, something I do before clicking in order to see where the link's going. I suspect that might partially be because I've always been aware it's there, and always try to code it in for my links whenever possible, because it is a recommendation.
But, given it's just extra, optional, data, it isn't actually an accessiblity problem unless the person using the feature is an idiot, right? Or am I missing something?
no subject
I had no idea screenreaders didn't automatically read title text, and was also unaware of keyobard navigation not displaying it; that's a weird issue I'd have thought would be resolved.
Definitely agree it should be explained in some way, and we'd need to ensure that people don't assume it'll be read. But it's there to give extra info for those interested; it displays on mouse hover, something I do before clicking in order to see where the link's going. I suspect that might partially be because I've always been aware it's there, and always try to code it in for my links whenever possible, because it is a recommendation.
Nielsen recommended it in Jan. 1998 and reinforced it when he did a study on blogs/journals specifically.
But, given it's just extra, optional, data, it isn't actually an accessiblity problem unless the person using the feature is an idiot, right? Or am I missing something?