W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013

Re: Creating an accessible Table of Contents

From: <accessys@smart.net>
Date: Mon, 25 Feb 2013 15:51:32 -0500 (EST)
To: Olaf Drümmer <olaf@druemmer.com>
cc: "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>, Devarshi Pant <devarshipant@gmail.com>, Vivienne CONWAY <v.conway@ecu.edu.au>
Message-ID: <Pine.LNX.4.60.1302251542350.24221@cygnus.smart.net>

thought I mentioned USA since that is what I am most familiar with but 
many other countries have similar provisions.

the law doesn't say what you can or can't use, only that a person with a 
disability can not be required to spend any money that a non disabled 
person would be required to spend to use that site.

so if the site can ONLY be accessed by someone running windows then the 
windows OS would be acceptable (wrong but legal) however there would need 
to be a free screen reader avaliable.

since PC's can dual boot linux/windows making it usable in linux under 
eMACspeak would probably be "legal" if not the right way to do something.

(more below)

On Mon, 25 Feb 2013, [iso-8859-1] Olaf Drümmer wrote:

> Date: Mon, 25 Feb 2013 21:12:02 +0100
> From: "[iso-8859-1] Olaf Drümmer" <olaf@druemmer.com>
> Resent-From: w3c-wai-ig@w3.org
> Hi Bob,
> you fail to mention who your government is, but I don't think it is 
> Olaf
> PS: When was the last time your government purchased something other 
> than Windows and Windows based programs/assistive technology?

I know several state and local governments running Linux and/or Macs  but 
that is not the point, it is what is the user using, if the site is 
intended for public use (public accomodation) then what it is written on 
is irrelavant it is what is the "user using" that is the point.


> Am 25 Feb 2013 um 19:18 schrieb accessys@smart.net:
>> 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/>(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:52:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:47 UTC