Whoever wrote that article is clueless!
Facts:
* Websites look the same to search engines as they do to screen readers. By moving positioning to CSS and minimizing your (X)HTML, you not only make it easier for people with disabilities to view your site, but you make it easier for search engines to properly place your site. This is a benefit that many overlook and inevitably pay for in SE ranking and SERPs.
* Millions of users have switched to browsers that respect standards, like Firefox. Sites that do not respect standards usually look like crap in these browsers. The site that was linked is a good example.
* Just because you designed a layout doesn't mean you'll always be the person working with that layout. When designing for someone else, you may only be one peice of the puzzle. Others have to work with your code too. Well formed code that is standards compliant allows others to quickly and efficiently modify your work when needed.
There have been numerous "credible" articles writen that discuss the pros and cons of standards compliance in web design. Standards compliance is not only a matter of "best practices" and consideration to those with disabilities, but there is also a tremendous benefit to your wallet as well.
If you would like to learn more about the subject, I invite you to visit my site where you will find several good articles on the subject.
Link:
http://mywebresource.com/Disclaimer:
1. Nowhere on my site will you find advertisements for my services. It is a free site I've published for the benefit of the Internet community.
2. No, not every page of my site is standards compliant. Why? Because it's a XOOPS site and there are some modules I have yet to be able to bring into compliance, but it is something I am working on as time permits.
Note: A default install of XOOPS easy to bring into standards compliance. It's the modules that make publishing a compliant site tough.
Just my 2 cents as a designer.
James
============================================================
EDIT: How does all of this relate to the original topic?
When creating the layout and design for the "new and improved" XOOPS.org, we need to pay special attention to standards compliance, usability, and search engine optimization. Not so much for the sake of XOOPS.org itself, but for the end users and designers who use XOOPS.
Many potential users of XOOPS want an accessible website, but may not have the skill to make XOOPS accessible. Do we turn our noses up at these users and say "Tough, learn how to code"?
Just about everyone wants a SE friendly site. Much of this is controlled by modules and the core. Do we tell these user s "Tough, learn how to code and become an SE expert"?
Furthermore, many developers use XOOPS as a framework to "wrap" their applications. This streamlines administration for them and allows them to reduce the amount of redundant coding necessary to produce applications for their clients. Do we tell these users "Tough, you'll just have to get use to working with sloppy code"?
The answer to those three questions should be a resounding NO! If we want to build a reputation of being an enterprise class content management framework, we cannot afford to shoot ourselves in the feet by ignoring standards compliance and usability!
Ok, I'll stop now. This subject just hits a sensitive nerve with me.
Best Regards,
James
Insanity can be defined as "doing the same thing over and over and expecting different results."
Stupidity is not a crime. Therefore, you are free to go.