>I agree entirely with Rachel, web standards are (or should be) independent >of server-side technology. It's the HTML/CSS that gets outputted to the
>browser that matters, regardless of what creates that output. I agree too. It's a puzzling attitude. I've seen people speak about web standards before, identify a piece of inaccessible or problematic code, say dismissively that "the content management system does that" and move on. A CMS does what you tell it to, and it doesn't matter what's on the back end. Or, to put it the other way around, if you can't output valid standards-based code with your system, then it's not a CMS. ============================================================================== The information contained in this email and any attachment is confidential and may contain legally privileged or copyright material. It is intended only for the use of the addressee(s). If you are not the intended recipient of this email, you are not permitted to disseminate, distribute or copy this email or any attachments. If you have received this message in error, please notify the sender immediately and delete this email from your system. The ABC does not represent or warrant that this transmission is secure or virus free. Before opening any attachment you should check for viruses. The ABC's liability is limited to resupplying any email and attachments ============================================================================== ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
