Helping ordinary people create extraordinary websites!
| |
Helping ordinary people create extraordinary websites! |
10 Common Errors When Implementing AccessibilityBy Trenton Moss2008-01-29 
Don't insert text into empty form fields for the sake of it
Another old and outdated guideline states that any empty form field should have placeholding text inside of it. This guideline originally existed as very old screen readers weren't always able to pick up empty form fields. All major screen readers now pick up empty form fields (and have done so for some time now) so it's safe to ignore this guideline and not insert pointless text into a form field. Indeed, screen readers often don't announce this placeholding text so screen reader users may enter their text in addition to the placeholding text without realising it. 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
|
 |