Welcome to MSDN Blogs Sign in | Join | Help

Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

During the SharePoint Conference last week, HiSoftware announced the general availability of AKS 1.1 (free and open source) and Compliance Sheriff for SharePoint (commercial product that rounds out HiSoftware's end-to-end solution for accessibility and other forms of content policy compliance).

AKS 1.1

AKS 1.1 provides 21 new control adapters that improve the accessibility of SharePoint 2007's blog and wiki features, and it's downloadable from http://aks.hisoftware.com. AKS 1.1 adds to the 24 control adapters, master pages, CSS files, and documentation that were released as part of AKS 1.0 a few months ago.

AKS 2.0

While AKS 1.0 and 1.1 should reduce the level of effort and knowledge needed by customers and partners to improve the accessibility of SharePoint-based sites/applications, we have received plenty of feedback that there's a need for more. Although taking open source contributions from the community remains a core part of our strategy for AKS, we realize that a growing number of customers simply cannot wait for that to happen. Hence, we've "double-downed" on our commitment to subsidize HiSoftware's continued development of the AKS.

AKS 2.0, to be released in Q3CY2008 will consist of the following:

  • Smart Adapters – automation of control adapters through install settings
  • Additional control adapters and remediation examples
    • Web part zone control
    • XHTML 1.0 Strict page level validation example – brute force approach
    • Another page level validation example against a standard DOCTYPE Declaration (DTD)
    • Additional requirements under Canadian Common Look and Feel 2.0 (CLF 2.0) guidelines
    • Improvements to accessibility and usability of SharePoint's Document Library functionality
  • Examples of remediation to comply with WCAG 2.0 Level AA
  • French language version of AKS 1.0 components

Accessible Rich Text Editor (aRTE)

Separately, we've reached an agreement to license a fully accessible rich text editor that HiSoftware has been developing for the past several months so that it can be used for free by SharePoint customers similar to the way that Telerik's cross-browser compatible "MOSS Lite" RTE is free. The aRTE will have all of the basic content editing and formatting functionality and will be accessible for both the content author as well as the content viewer. The aRTE will be available in Q3CY2008 and sooner for select beta testers. Members of HiSoftware’s Technology Partner Program will have the ability to modify and extend the aRTE's source code as part of their custom SharePoint implementations.

The aRTE will have the following features:

  • Accessible Output – XHTML 1.0 compliant
  • Accessible Input – validates accessibility of content entered into the RTE
  • Character formatting
    • Bold
  • Paragraph formatting
    • List bullet
    • List number
    • Quote/Indent
    • Table of figures inc row and/or column headings
    • Hyperlink
    • Headings – levels 1-4
    • ALT text for pictures
    • Caption for pictures
    • HTML source editing
  • Table repair utility – assists in the creation of accessible data tables within the RTE
  • Form creation and remediation

SharePoint vNext

It's still too early for me to disclose any details about our accessibility plans for the next version of SharePoint, but I can tell you that we've listened and learned a lot from all of the feedback that we've received from around the world regarding the need for accessibility both in terms of cross-browser compatibility and in the form of improved usability for vision impaired and physically challenged users. Overall, we are deeply committed to the Interoperability Principles recently announced by Steve Ballmer and Ray Ozzie, and in particular, Principle II: Support for Standards. Hence, from SharePoint's point of view, we are monitoring the ongoing standards work of the W3C's Web Accessibility Initiative very closely. I look forward to providing more details about our accessibility plans for SharePoint vNext (and getting your feedback) on this blog later this year.

 

<Lawrence />

Published Wednesday, March 12, 2008 4:34 PM by sptblog

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap | Technology

# re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

I understand that accessabuility is important to MS, but is it really the #1 priority for vNext?

We are launching SPS and evangilizing it for the business world, and hoping the shortcomings (blog, wiki, tagging, rating, forums, <insert anything to do with social computing here>) will be addressed in vNext before they start to call us on it:

"Why can't the wiki do this"

"Why can't the blog do that"

"Why can't we rate content"

"Why isn't there decent forum support"

Ballmer says this is the next "OS" for the future, but why should anyone "switch" to it unless you give us what "the other guys" offer?

For reference, look at your own "Live Workspaces Forum" which uses CommunityServer instead of your own internal SharePoint product!

This is the epitome of what we need: social networking that will attrack, engage, involve, and energize a community of users that WANT to use the product.

Thursday, March 13, 2008 1:19 AM by Confused?

# re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

To Confused?: We are investing generously towards improving all of our social computing capabilties. See my personal blog entry (http://sharepoint.microsoft.com/blogs/lliu/Lists/Posts/Post.aspx?ID=19) for a hint. :-) However, no matter how cool/useful those features will be, if they are not accessible to *everyone*, SharePoint will not be allowed to be purchased or deployed in the growing number of companies and entire countries that have stringent accessibility requirements. Accessibility is fast becoming as important as security -- i.e. it's a "P0" feature.

Thursday, March 13, 2008 2:56 PM by LLiu

# re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

Lawrence, I have a somewhat random question, maybe you're allowed to answer it:

What are you calling SharePoint vNext internally, besides "vNext"? SharePoint 14? WSSv4? MOSS 2009? We need to agree on one tag, so I can get with the tagging.

Also re: Confused, I think a lot of the features you ask for are geared towards consumer portals and consumer social networks. I don't think in the corporate world, that online communities should look anything like online communities you'd find on the internet. Maybe I'm not buying into the social networking vision; maybe I'm misinterpreting. But I don't think, for example, that implementing vBulletin-style forums will encourage corporate adoption...

-Peter

Thursday, March 13, 2008 4:22 PM by pseale

# re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

Regarding the RTE, one of the bigger issues with it, from an accessibility standpoint, is that it "steals" focus. In other words, entering the RTE with a screen reader in forms mode, it is basically impossible to navigate to other elements in the form.  Is there anything being done to remediate this?  If so, what?

Friday, March 14, 2008 1:47 PM by accessibility consultant

# Accessibility in SharePoint using AKS

I have been really busy over the past few weeks and something I missed last week I thought was worth

Sunday, March 16, 2008 8:07 PM by CodeJedi.NET

# re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

How about tool support!!  

SharePoint Designer does not work with TFS.  There is no way (without writing code) to move things like content types between servers.  

There is *sloppy* stuff in core.css.  There is a lack of support for multilingual sites (yes you have variations, but it doesn't support the basic stuff you would expect).  

I'd be happy to help out/give lots of feedback with vNext (or whatever it will be called) as would 99% of the people who look at this blog!!!

Give us a voice please!!

Monday, March 17, 2008 2:55 AM by Paul Turner

# TechDays – Dia 1

Decorreu na passada semana entre os dias 12 e 14 de Março a edição deste ano do TechDays , o maior evento

Monday, March 17, 2008 5:10 PM by Miguel Isidoro

# TechDays – 1º Dia

Decorreu na passada semana entre os dias 12 e 14 de Março a edição deste ano do TechDays , o maior evento

Monday, March 17, 2008 5:42 PM by Miguel Isidoro

# WSS 3.0 & MOSS: Recopilación de enlaces interesantes (XVI)

Después de un mes desde el último recopilatorio de enlaces sobre SharePoint , y teniendo en cuenta que

Sunday, March 23, 2008 5:14 PM by Blog del CIIN

# re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

I missed last week I thought was worth

Friday, March 28, 2008 6:18 PM by http@uzct.com

# re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

Hi,

Like Paul Turner stated- "Give us a voice"! We have lots of input, where can we give it?!?

My personal (which seems to be shared by many) input is to allow us to customize things even further, especially the tables-based web parts framework is extremely frustrating.

Please read the following blog posts by Emil, which give very good feedback regarding moss development:

http://friendlybit.com/css/sharepoint-2007-from-an-interface-developers-view/

Thanks.

http://friendlybit.com/html/default-html-in-sharepoint-2007/

Tuesday, April 01, 2008 4:36 AM by Henrik Weimenhög

# The browser or gateway element with ID 'SKTDevicesSamSung' cannot be found

Hi, You may face this error when registering Custom Control Adapters in your environment. I did, and

Monday, April 28, 2008 12:54 PM by Imagine Think Create Share

# Accesibilidad en MOSS, AKS, Cumplimiento AA

Hola como estas, con la ayuda de un par de compañeros, te pongo un post que resume la información relativa

Saturday, June 14, 2008 11:45 AM by compartirypunto

# Regarding aRTE and ambiguous features

Hi,

A couple of quick questions about the aRTE.

1) Quote/indent - These aren't the same thing, and shouldn't be presented to the user as the same thing.

Do you mean quote/blockquote? Using blockquote elements to indent text is semantically incorrect. Even though in most browsers indenting the text will be the default style, it should still be referred to as blockquote in the interface.

I have seen this done incorrectly on just about every text editor available. Maybe "short quote" and "longer quote" would be easier for people using the interface to understand.

2) Caption for pictures - how is this done? As far as I am aware the only way to associate a caption with an in image is using HTML5, and that isn't ready yet.

If you mean using the title element, this isn't really an accessible way to provide information as the way it is displayed in various assistive technologies is inconsistent at best.

Tuesday, July 01, 2008 11:44 AM by David Owens

# Sharepoint Technologies and XHTML

Recently I've had some discussions with some folks inside MS with this subject. So, I decided to write

Monday, September 08, 2008 2:50 PM by A consultant's perspective on SharePoint Technologies

Leave a Comment

(required) 
required 
(required) 
 
Page view tracker