Our new SharePoint Report explains how one of the core challenges with the platform -- dating from inception through to MOSS 2007 -- is that the needs of a collaboration service often conflict with the requirements of other information services, particularly around website publishing.

One example: like many other portal vendors, by default MOSS wants to insert a lot of extra code and non-standard mark-up on every page to create an interactive collaboration dashboard. As this MSDN brief on how to performance-tune a MOSS 2007 WCM site warns, "Office SharePoint Server, by default, is not XHTML compliant." This has manifold implications for website publishing, not the least of which is accessibility.

Can you fix this? Yes, with an experienced developer carefully going into the innards of the tool at various levels to replace code. Not particularly friendly.

Of late, Redmond has been touting its "Accessibility Kit for SharePoint." At least one avid researcher points out that the fix remains incomplete. (Link thanks to Martin White.)

As Web CMS Report readers know, some competing web content management packages quietly suffer the same problem. At least with SharePoint you can read all about it publicly. But Microsoft casts a huge shadow on this space, and their relative disregard for core web standards just lowers the bar for everyone else.