As for the Web Parts: you can fix the tables issue by simply removing them using a Control Adapter. Please note that such Control Adapter breaks the Web Part Page Script Component (WPSC).
In all the WCM solutions I've been working on, I'm trying to use the standard SharePoint functionality unless it's really impossible to do. On the other hand I haven't tried every available Web Part and not all customers require a fully accessible web site.

Is the Imtech SharePoint Enhancement Toolkit still going to be released to the community? Would be great if so.

I'm also keen to pick your brains on a problem I have. We have a heavily customised SharePoint 2007 website which must (and indeed does) achieve WCAG 1.0 AA standards. However in order to achieve this the site users entirely custom controls – no web parts. We've noticed that no search statistics are being generated and have investigated this to the point where we now realise that the SharePoint Search web parts do a lot more than just output the results. They also generate javascript based web service calls that log queries and clickthroughs for the search statistic reports found in the SSP.

I see that accessibility in SharePoint is something that you're particularly knowledgable on. How have you got around this problem? Do you continue to use the standard web parts? Don't they break the AA rule of using tables for layout? Or is there another way to generate the statistics that I'm unaware of?

Thanks for your help with this.

James.

Thank you for your comment. Perhaps I could be of any help before I write the step-by-step guide? I'm curious what your challenges are and what have you already tried.