As for changing factory settings, well, you got me there, no idea, I always like to look under the hood…probably why I get into trouble a lot.

This might interest you – back to the notion of “footnotes” – in view ones this time, not hidden and with JQuery. Have a look at this.

http://www.cssnewbie.com/generating-automatic-website-footnotes-with-jquery/

I’ll keep checking back.

You’re correct in your assumption – what’s accepted by W3C does not necessarily work for accessibility.

Title attributes on form elements might be read by screen readers, but title attributes on images might be ignored. Some screen readers actually have settings where users can select if title attributes on certain HTML elements are read, but then again, how many people actually change factory settings?

I can think I follow what you have done here. However, and you can correct me if I am wrong, by using the “title” property and NOT using the longdesc – will a screen reader pick up on it being there?

I was under the impression (potentially wrongly..) that the screen reader picks up on the “longdesc” tag and offers the “viewer” the option of having the caption read to them.

So, would the “description” appearing as part of a title tag cause:

The screen reader to read the text outside of context/flow?
Would the “viewer” have the content read to them regardless – not have the option of skipping by.

By omitting the longdesc altogether, is that classed as accessible?

It sure is all confusing for me.

Your first example does pass the WAVE or Cynthia test – BUT the second one does not – it is flagged for not having a longdesc….

This leads me to conclude, that what is acceptable by W3c, does not necessarily work for accessibility.

Must say, I am on a learning curve here… quite enjoying the trip. Just wondering what else you have up your sleeve.