RE: Creating an accessible Table of Contents

I often use CommonLook to remediate complex tables and it is indeed
effective, but not to create T O C.

Andy Keyworth <akeyworth@tbase.com> wrote:

Our communications professionals, who understand MS Word and its
accessibility features well, encountered the same kinds of problems that
Vivienne originally described. CommonLook was a worthwhile investment.



*Andy Keyworth
*Senior Web Accessibility Specialist | T-Base Communications
Inc.<http://www.tbase.com/>
19 Main Street │ Ottawa, ON │ K1S 1A9
telephone. 613. 236. 0866 Ext. 256 │ fax. 613. 236. 0484
email. *akeyworth@tbase.com*



*From:* Devarshi Pant [mailto:devarshipant@gmail.com]
*Sent:* February-25-13 4:25 PM
*To:* Andy Keyworth
*Cc:* Vivienne CONWAY; w3c-wai-ig@w3.org
*Subject:* Re: Creating an accessible Table of Contents



There is no need for any plugin to make T O C 'accessible.' It just needs
to be done correctly in the source Word document before converting.



On Mon, Feb 25, 2013 at 4:01 PM, Andy Keyworth <akeyworth@tbase.com> wrote:

Hi Vivienne,



Our company regularly produces accessible PDFs for our clients- we have to
avoid exactly the problems you describe below.



We use the following process:



1.       Create the original document in Microsoft Word 2010;

2.       Add the Table of Contents in MS Word, by using the References >
Table of Contents feature. We use “Automatic Table 2” to set the format of
the table.

3.       Use CommonLook PDF <http://www.commonlook.com/CommonLook-PDF>, a
plugin for Acrobat, to do the actual conversion. We’ve found that it
produces screen reader-friendly, consistent Tables of Contents.



I’ve tested the results in JAWS 10: the dots are not read out.



*Andy Keyworth
*Senior Web Accessibility Specialist | T-Base Communications
Inc.<http://www.tbase.com/>
19 Main Street │ Ottawa, ON │ K1S 1A9
telephone. 613. 236. 0866 Ext. 256 │ fax. 613. 236. 0484
email. *akeyworth@tbase.com*



*From:* Vivienne CONWAY [mailto:v.conway@ecu.edu.au]
*Sent:* February-22-13 9:39 PM
*To:* w3c-wai-ig@w3.org list
*Subject:* Creating an accessible Table of Contents



Hi all



I'm wondering if anyone has discovered how to create a Table of Contents in
Word that reads properly with a screen reader when the document is put into
PDF..  Using the automatic TOC function you get a disaster for reading -
some styles read all the dots in the dot leader, others read something like
89 dot and then the page number.  At best if you choose the option for the
solid line which is recommended you get "Chapter one one (page
number)" with no pause - and that's only if you have the punctuation
reading turned right down to minimal setting. As soon as you set the screen
reader to read 'most' punctuation it reads either the dots or the number of
dots etc.



I'm working with a local government who create a lot of large documents
such as council meetings which are put into PDF that they need to make
accessible and are accessed throuigh their website.  At present the TOC
function is causing real headaches.  We've tried all kinds of options in
Word they none of them read nicely from the PDF document that is created
after tagging the Word document properly.



Any ideas?





Regards



Vivienne L. Conway, B.IT <http://b.it/>(Hons), MACS CT, AALIA(cs)

PhD Candidate & Sessional Lecturer, Edith Cowan University, Perth, W.A.

Director, Web Key IT Pty Ltd.

v.conway@ecu.edu.au

v.conway@webkeyit.com

Mob: 0415 383 673



This email is confidential and intended only for the use of the individual
or entity named above. If you are not the intended recipient, you are
notified that any dissemination, distribution or copying of this email is
strictly prohibited. If you have received this email in error, please
notify me immediately by return email or telephone and destroy the original
message.


------------------------------

This e-mail is confidential. If you are not the intended recipient you must
not disclose or use the information contained within. If you have received
it in error please return it to the sender via reply e-mail and delete any
record of it from your system. The information contained within is not the
opinion of Edith Cowan University in general and the University accepts no
liability for the accuracy of the information provided.

CRICOS IPC 00279B