[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-accessibility] Re: Jaws accessibility of open officeauthored document.
Hi Dave, Into what version of MS-Word did you save this file? "Word 6.0", "Word 95", or "Word 97/2000/XP"? If it is a single version of the MS-Word file format that is working on Word 2003 & 2000 and failing in Word '97, then I'd rather suspect the problem is with Word '97 + JAWS, and has nothing to do with either ODF or the OOo translation code. Have you tried creating a table of contents from scratch in Word '97 and seen how that works with JAWS? Regards, Peter Korn Accessibility Architect, Sun Microsystems, Inc. > On 22/01/07, Dave Pawson <dave.pawson@gmail.com> wrote: >> Scenario. >> I write a document in Open office Writer. (Shows as 2.1) on Windows 2k. >> >> I save as MS office and send to a blind colleague who uses Jaws. >> >> The response I get, after export as html is: >> >> quote. I can read it now thanks. The word version seems to jump >> around the pages and wraps from page 1 to 6 etc. Steve replicated >> this when I showed him, so not sure if it's something in how you're >> creating the file. end quote. > > Managed to narrow it down a little. > Its the auto generated table of contents. > In Word 2003 it's fine. > In Word 2000 it's fine. > In Word 1997 it shows as a sequence of codes. Jaws can't get access to > it. > Since the toc is set to display on its own page, the reader can interpret > it as if content has been skipped. > Either way, it's confusing and inaccessible in those conditions. > > regards > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]