WCAG Compliance
I know its an old chestnut, but this is of great importance to us in the Public Sector and with many commercial clients too. How close will the kit be to compliance with the current WCAG 1.0 AA level of the standard?
All Replies
I've just attented the AKS presentation @TechEd Barcelona. What appears is that AKS focuses on the out of the box available Web Parts and CSS. So if you would like to create a totaly custom Internet facing site and not using any of the SharePoint controls/Web Parts it won't help you a lot except for providing a few guidelines about how to do certain things when it comes to accessibility in SharePoint. ASK doesn't do anything about the rendering engine what is the main cause of the compliancy problems.
I've suspected that kind of twist about the ASK and that's why I've started my own project to make SharePoint accessible. It's definitely aimed at developers and it will stay that way, but it allows you to achieve 100% WCAG compliancy. The code isn't available yet but I really hope it will change soon. For the time being let me know if it answers your questions and if it's all clear to you.
- Regarding WCAG compliance, we have quite a bit of experience with this.
We (Content and Code) have developed an Intranet application for the RNIB (which launched in January 2009) which was WCAG 1.0 AAA compliant (yes ... thats AAA not AA)
We also developed a Website for the RNIB (which launched September 2009) which is WCAG 2.0 AAA compliant.
If you find that other toolkits are not suitable then please get in touch, our WCAG 2.0 solution has been built around re-usable architecture, with the aim to making it portable to other SharePoint systems.
We are planning to launch our SAS (SharePoint Accessibility Solution) framework soon which takes all of the components from this architecture into a deployable package.
regards
Martin Hatch
MCPD .Net Web Development
MCTS WSS 3.0 | MOSS 2007
Visit my Blog
