Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: ergophobe
Index of HTML elements and attributes
Before we sink our teeth into topics surrounding Accessibility and Usability, I think it is important that we familiarize ourselves intimately with the Index of HTML elements and attributes above. Much of what we will discuss and dissect will be based on those.
Once you familiarize yourself with the Index of HMTL elements and attributes, we can then discuss each one in depth. We're going to take the most common ones and discuss those first. The lesser used elements and attributes we'll save for last. You may not have a need for them or, you may not realize you do have a need for them. ;)
We're going to discuss the proper use of the elements and how to utlize the attributes for those elements in making your websites accessible and also usable. And, let us not forget that everything we are going to do is exactly what the search engines want us to do - follow the guidelines, it's that simple. We'll be building accessibly user friendly sites while attracting the spiders in droves! :)
There won't be any secrets shared, nor will there be any hacks, cheating, bending the rules, etc. Everything is pretty much written in stone in the guidelines. There is typically an answer for every question. I say typically because sometimes the answers may be somewhat difficult to find. But, we will find them for you!
Don't use <abbr> for acronyms, or <acronym> for abbreviations.
Problem - Internet Explorer ignores <abbr>.
Older versions of Internet Explorer (version 6 and older) do not understand the
element at all. It is treated no different than a made up element such as <jedi>.
Do not, however, resort to using the
element everywhere in place of
simply because IE lacks support. Instead, utilize one of the methods available for tricking IE into understanding <abbr> while not changing the HTML source itself.
This thread [webmasterworld.com] contains some interesting discussion on the problem, along with a few possible solutions.
Disclaimer: The accessibility level for any of the solutions discussed in the aforementioned thread cannot be guaranteed, nor has it undergone accessibility testing.