This project is read-only.

HiSoftware AKS

Microsoft paid HiSoftware to put together a solution that would make SharePoint 2007 more accessible. HiSoftware released Accessibility Kit for SharePoint (AKS) 1.0 in Nov 2007 and 2.0 in Mar 2009. The primary goal for this effort seems to be education on how to achieve compliance with the various accessibility standards out there.

In the Box

HiSoftware AKS comes with the following pieces: Additionally, references are made to CSS Friendly Control Adapters, but they are not included within the solution.

All-in-all, the setup process is a very manual, very tedious, and very frustrating. We felt the need to take this concept to the next level.

Additional Tools

As we've mentioned before, Accessibility isn't as easy as flipping a switch. Third-party content and controls can ultimately break any level of accessibility compliance you may have. To combat this, HiSoftware offers tools to better ensure/enforce accessibility standards.

We have no intention to break compatibility with AKS 2.0, so they should continue to work with future uAKS releases. With that said, we are not testing these tools with uAKS. If you run into any issues, please let us know. NOTE: uAKS does not currently attempt to or plan to extend or re-create these additional HiSoftware tools. HiSoftware spent a significant effort on these offerings and we believe those interested in that level of compliance should invest their time in understanding what HiSoftware has available.

The Rest of the Story

Why [unofficial] Accessibility Kit for SharePoint (uAKS) is necessary

We sincerely appreciate the tremendous effort HiSoftware put together to create AKS; however, we do not feel their effort is open enough for the following reasons.
  1. Registration is required to download the software
  2. Registration is not automated, meaning you may never get your registration confirmation
  3. Email communications also seem to be a failure, as emails are seemingly ignored
  4. Despite the published, open nature of the effort, there is no publicized means for contributing
  5. There is no published issue tracker or list of known bugs
  6. The discussion board is read-only without registration, which can be a failure if you fall victim to #2 and #3
  7. There are no published plans for future versions
Given these issues and the significant number of problems run into with AKS, we created this project to open AKS up to the community as uAKS. Enjoy!

Last edited Nov 18, 2009 at 12:52 PM by flanakin, version 4

Comments

No comments yet.