10 Common Errors When Implementing Accessibility
By Trenton Moss2008-01-29
Don't agonise over acronyms and abbreviations
|
|
Declaring whether something is an acronym or abbreviation is easy to do in the HTML, simply by using the <acronym> or <abbr> tags. The full acronym or abbreviation can then be expanded upon within this tag.
Screen readers don't support these tags though so they don't really offer much of a benefit to these users. The users they benefit are sighted, mouse-using web users - when they mouse over one of these items the full expansion of the acronym or abbreviation appears as a tooltip. This can certainly be viewed as a small usability enhancement but doesn't really count as an accessibility benefit.
Tutorial Pages:
» Introduction
» Don't use verbose ALT text
» Don't use random characters to separate links
» Don't insert text into empty form fields for the sake of it
» Don't use access keys
» Don't use the table summary (unless it actually adds value)
» Don't forget about the content
» Don't worry too much about accessibility statements
» Don't agonise over acronyms and abbreviations
» Don't change the tab order (unless you have a very good reason to do so)
» Don't forget to listen with a screen reader
|
