|
New Accessibility Guidelines Part IV: Robustness |
 |
 |
 |
|
Published by: PracticaleCommerce.com Date: May 22, 2009 by Joseph C. Dolson URL: http://www.practicalecommerce.com/articles/1114-New-Accessibility-Guidelines-Part-IV-Robustness "...Validation Does Not Make a Document Accessible There are many accessibility suggestions that state you should validate your document in order to improve accessibility. This is not, however, precisely true. Validation does not, in itself, ensure any level of accessibility. Validation does not equal accessibility and invalid code does not automatically lead to an inaccessible site. While it's certainly true that authors who take the effort to validate their documents are probably more attentive to issues that impact accessibility, it's by no means a guarantee.... Why Validate HTML Code? ...HTML is an accessibility-supported technology. As long as you're using valid HTML, you're able to use that language to create an accessible website... Conclusion...Although validation isn't actually required, it's a good way of checking to see whether there are any errors in your page that will cause problems for your customers with disabilities. You can play it safe by using highly-supported technologies such as HTML and CSS... "
Read and comment on this article at: http://www.practicalecommerce.com/articles/1114-New-Accessibility-Guidelines-Part-IV-Robustness
|
Website Accessibility - Structural Sufficiency
