Helping ordinary people create extraordinary websites!
| |
Helping ordinary people create extraordinary websites! |
10 Common Errors When Implementing AccessibilityBy Trenton Moss2008-01-29 
Don't use the table summary (unless it actually adds value)
The table summary can be inserted on to any HTML table and is essentially a summary of what the table is. Screen readers read aloud table summaries before reading through the table, providing them with a summary of the table content prior to listening to the whole table. The table summary should always be omitted from a layout table. Websites using a tabular layout sometimes have table summaries of ‘layout table’ which of course add no value at all. Even with data tables, a table summary is only needed if there's insufficient information provided about the table on the page (which isn't usually the case). 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
|
 |