We have moved a lot into .net stuff while still keeping it css layout, and although yes it did take time, our programmer now does this as normal practice. So it is possible!! It does take more time and effort for the programmer. You just have to make sure that they don't use the pre-built .net modules because visual basic puts in tables and junk around it all.
The other thing to be aware of is that sometimes they will need to use visual basic's id values which sometimes forces you to use classes even where id's would be more appropriate. However our process usually works where I design and build the front-end code, then the programmer integrates this code into the .net stuff, so I might have more control over the xhtml + css than you might? Perhaps it would be worth trying to get the rights to build the front-end code too? The way the css layouts look in visual basic is much like the design view of dreamweaver - not hot and so you can't use it as an indication of what it will look like in the browser. Yes some stuff does generate tables, such as the pre-built modules (which they can change, but usually don't...) and database generated content. However now our programmer understands standards stuff I haven't had a problem with tables turning up where they shouldn't be or anything. Sometimes the data tables that it does generate are extraneous - empty cells and such. Best of luck!! It will likely be something that will develop over time while the programmers understand the importance and get used to working with standard and accessible code. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of kvnmcwebn Sent: Thursday, 3 November 2005 9:00 a.m. To: [email protected] Subject: RE: [WSG] standards, accessability and validation? props to everyone who provided feedback on this post earlier. (regarding designing accessible sites for non standards savy programmers to mark up) I spoke with programmers today. They were more receptive than i'd expected. They agreed give standards a go by easing into css based design one step at a time. I think out of all the great advice i got just being humble and not making them feel inferior was the most important. The conversation would have been a lot shorter if i had tried to preach. Also the accesibilty points/screen reader argument were huge. The big concern is how non-table layouts will show up in visual studio during database/form development...also that some of the dynamic content generation creates tables. Anyway were off to a good start. -best kvnmcwebn ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
