(unknown charset) Re: Creating an accessible Table of Contents

but as mentioned federal (USA) law requires platform neutrality the only 
way around this is to give (free) any software needed to use the document. 
I understand adobe is more or less free but has problems in the 
accessibility end.

people using Macs, linux and other OS must also be able to access the 
document if it is a publically avaliable gov site.

many including myself fought long and hard to get this in the laws, access 
cannot require spending any user funds for accessibility that in and of 
itself is a basic tennant of the ADA.  (28CFR36.301(c) )

Bob

On Mon, 25 Feb 2013, Devarshi Pant wrote:

> Date: Mon, 25 Feb 2013 14:04:20 -0500
> From: Devarshi Pant <devarshipant@gmail.com>
> To: accessys@smart.net
> Cc: Vivienne CONWAY <v.conway@ecu.edu.au>,
>     "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>
> Subject: Re: Creating an accessible Table of Contents
> Resent-Date: Mon, 25 Feb 2013 19:04:55 +0000
> Resent-From: w3c-wai-ig@w3.org
> 
> How many variables should we account for during testing? I wouldn’t stress
> if T O C works or not in an XYZ platform if the process to convert to PDF
> is correct. Apparently, for me it worked with JAWS / Windows / PDF, and the
> conversion process was correct. For example, did the word document (that
> was converted to PDF) use correct styles (as in headers) to create the T O
> C or not? If a screen reader works on the Word document, but does not
> anymore on PDF after conversion, what then?
> Going back to the original post, if the T O C is created off of styled
> headers and then converted to PDF, you can use the screen reader's headings
> list in PDF to replicate the T O C. That is besides using the bookmarks. So
> you have two different ways to get to the content if T O C fails for some
> reason.
>
>
> On Mon, Feb 25, 2013 at 1:18 PM, <accessys@smart.net> wrote:
>
>>
>> you are aware that if it is a government website the content must be
>> accessible via all operating systems not just windows.
>>
>> Bob
>>
>>
>> On Mon, 25 Feb 2013, Devarshi Pant wrote:
>>
>>  I have never had issues while converting a T O C in Word to PDF. It could
>>> be the settings. In JAWS 13, under text processing, you may want to look
>>> into the ‘filter repeated characters’ and tone it down to ‘say first 3
>>> repeated characters.’
>>>
>>> On Fri, Feb 22, 2013 at 9:39 PM, Vivienne CONWAY <v.conway@ecu.edu.au
>>>> wrote:
>>>
>>>>
>>>> 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
>>>>
>>>> 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/> <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
>>>>
>>>>
>

Received on Monday, 25 February 2013 20:37:24 UTC