There have been two recent announcements relating to document formats and they will have an impact on the accessibility market:

• September 2nd 2007, the second ballot on the ISO/IEC ratification of Open XML show strong support for the standard but not sufficient for it to become a standard.
• September 10th 2007, the OpenOffice.org community announced that IBM will be joining the community to collaborate on the development of OpenOffice.org software.

To understand the implications of these announcements needs some background information.

In November 2003 Microsoft announced that Office 2003 had been extended to support XML input and output. Microsoft defined a schema for this interchange commonly known as WordML see my articles /technology/content.php?cid=6620 and /technology/content.php?cid=7733. The purpose of WordML was twofold:

• To provide easier integration of Office with other applications. The applications would be able to consume and generate WordML much more easily than create the internal doc format.
• More importantly it was a way of archiving Office documents in a format that would still be readable in years to come and without needing Microsoft Office products. We can still read a thousand year old book, but there is a real danger that we will not be able to read some computer documents in a hundred years time or even less.

Microsoft initially announced WordML as a format that would be controlled and extended by Microsoft but freely licensed to anyone who wished to use it. This made it interesting to vendors who wanted to integrate with Microsoft Office; it was of no real interest to anyone who wanted to develop an alternative to Office. Later Microsoft offered it as a draft standard to Ecma International. This draft is the basis of Office Open XML that has just had its second ISO/IEC ballot.

In 2000 Sun founded the OpenOffice project, to develop an Open Source office suite. The format of the documents was XML from the start. Starting from a more or less blank sheet the project could concentrate on creating a standard to support future document requirements. In 2002 the Oasis Open Office Technical Committee was set up to create a standard document format. In May 2005 the OpenDocument Format (ODF) was approved as an OASIS standard. In May 2006 ISO approved ODF as ISO/IEC 26300. The creation of ODF as an open standard has meant that several organisations have developed tools and editors to create and consume ODF, without any issues of compatibility; amongst them are Sun, OpenOffice.org, Google and IBM Lotus.

IBM did not become a member of the OpenOffice Project when it started. However, IBM has been actively involved including announcing in May 2006 that Lotus Notes would use ODF and the announcement in December 2006 of IAccessible2, see my article. IAccessible2 defines an interface between assistive technologies and applications such as OpenOffice.

IBM joined OpenOffice.org in September 2007 and will be making initial code contributions that it has been developing as part of its Lotus Notes product, including accessibility enhancements, and will be making ongoing contributions to the feature richness and code quality of OpenOffice.org. Besides working with the community on the free productivity suite's software, IBM will also leverage OpenOffice.org technology in its products.

So we now have two competing standards: Office OpenXML which is not yet, and may never become, a standard driven by Microsoft, and ODF which is a standard and which now has IBM support. How will this effect accessibility? The answer, I am afraid, is that having two standards is not good. The problem is that creating assistive technologies is a specialised task and the market is relatively small. Supporting both standards is going to be expensive and likely to lead to delays in implementing and supporting new functions.

Office OpenXML is a big standard. It is big because it needs to be able to support the long history of office suites. A significant amount of the standard should not be used in modern documents. One of the challenges will be to decide what part of the standard is relevant to new documents. My suggestion would be that assistive technologies only support the 'modern' part of the standard. If a user of an assistive technology has to access a document which includes any of the 'archive' parts then the document can be converted into a modern version. The conversion may result in a loss of some formatting, and the ability to edit in the way the original was edited, but this is unlikely to be an issue for the AT user as some formatting is lost/modified when accessing through assistive technologies anyway.

There are already tools available that can transform OpenXML into ODF and vice versa. They do a good enough job for most users, there is no loss in the content, or meaning, of the document—just a possibility of small differences in the formatting.

ODF is already a standard and has shown that it is robust and extensive enough to support the creation and distribution of new documents. ODF has not attempted to support all the 'archived' documents that OpenXML is designed to support. OpenXML will provide a mechanism for the long term archiving of old documents but it appears not to have any benefits over ODF for the creation and storage of new documents. This is not surprising given the background of each.

For AT developers in particular, and many other tool creators in general, it would be a great benefit if there was just one format for new documents. This would enable all the effort being used in the creation of robust and function rich tools rather than having to support two competing standards.

Given the support ODF is now getting it would be sensible if the OpenXML committee decided to align the standard with ODF so that OpenXML concentrated on the archiving issue rather than defining a new standard for all documents.