I was reading an article over at Provoke about SharePoint and WCM. The main discussion was around what knowledge you need to implement this and the post does a great job of breaking these things up. We have a designer at our work that understands CSS better than anyone I've met and he's currently working on a RedDot CMS implementation. I think he'll be able to switch products with no problems and will really like the SharePoint Designer interface for editing templates etc.

I guess the main thing to bear in mind, as the post also states, is that each WCM has it's own funky way to do the same thing. For example, if you wanted to render a list of sub pages with an extract, and thumbnail image etc. in SharePoint you'd probably be using the Content Query Web Part. This requires knowledge of XML, XSLT and also knowledge of SharePoint Lists as a minimum.

If you're going down the Accessibility path then it's a completely different kettle of fish! Speaking with Sezai from Vivid Group, he was highlighting the agony he goes through to make sure everything renders correctly and to standards. He basically doesn't use any of the out of the box web parts and custom writes all of his. Not really a good story for SharePoint. There is work in the pipeline going on as Clayton explains.