Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap | Technology

Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap | Technology — Thu, 13 Mar 2008 03:24:27 GMT

PingBack from http://moderntech.thegeekyblog.com/2008/03/12/announcing-accessibility-kit-for-sharepoint-11-and-future-roadmap/

re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

Confused? — Thu, 13 Mar 2008 08:19:17 GMT

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.

re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

LLiu — Thu, 13 Mar 2008 21:56:18 GMT

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.

re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

pseale — Thu, 13 Mar 2008 23:22:57 GMT

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

re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

accessibility consultant — Fri, 14 Mar 2008 20:47:32 GMT

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?

Accessibility in SharePoint using AKS

CodeJedi.NET — Mon, 17 Mar 2008 03:07:20 GMT

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

re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

Paul Turner — Mon, 17 Mar 2008 09:55:45 GMT

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!!

TechDays – Dia 1

Miguel Isidoro — Tue, 18 Mar 2008 00:10:46 GMT

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

TechDays – 1º Dia

Miguel Isidoro — Tue, 18 Mar 2008 00:42:04 GMT

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

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

Blog del CIIN — Mon, 24 Mar 2008 00:14:46 GMT

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

re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

http@uzct.com — Sat, 29 Mar 2008 01:18:44 GMT

I missed last week I thought was worth

re: Announcing Accessibility Kit for SharePoint 1.1 and Future Roadmap

Henrik Weimenhög — Tue, 01 Apr 2008 11:36:17 GMT

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/

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

Imagine Think Create Share — Mon, 28 Apr 2008 19:54:46 GMT

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

Accesibilidad en MOSS, AKS, Cumplimiento AA

compartirypunto — Sat, 14 Jun 2008 18:45:38 GMT

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

Regarding aRTE and ambiguous features

David Owens — Tue, 01 Jul 2008 18:44:07 GMT

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.

Sharepoint Technologies and XHTML

A consultant's perspective on SharePoint Technologies — Mon, 08 Sep 2008 21:50:18 GMT

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

web tasarım

web tasarım — Sat, 01 Aug 2009 15:10:15 GMT

miracle http://www.parcakontorbayiniz.com