Re: Creating an accessible Table of Contents

a large percentage (but of course not all) linux users are comfortable 
with command line and as long as it could be used with whatever other 
software they are using (eMACspeak is mostly command line) it would 
probably work and be appreciated.

Bob

On Fri, 1 Mar 2013, [iso-8859-1] Olaf Drümmer wrote:

> Date: Fri, 1 Mar 2013 10:48:21 +0100
> From: "[iso-8859-1] Olaf Drümmer" <olaflist@callassoftware.com>
> To: accessys@smart.net, "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>
> Cc: "[iso-8859-1] Olaf Drümmer" <olaflist@callassoftware.com>,
>     Karl Groves <karlgroves@gmail.com>,
>     "[iso-8859-1] Ramón Corominas" <listas@ramoncorominas.com>,
>     Ginger Claassen <ginger.claassen@gmx.de>
> Subject: Re: Creating an accessible Table of Contents
> Resent-Date: Fri, 01 Mar 2013 09:49:14 +0000
> Resent-From: w3c-wai-ig@w3.org
> 
> We at callas might be interested in creating a free tool for Linux (based on pdfGoHTML, which we are already offering for Mac and Windows), that converts tagged PDF (and only tagged PDF!) into HTML (and this will only work well, if the tagged PDF is well tagged). As we hardly ever do development of tools with a user interface on Linux, but rather only command line tools and SDKs, I wonder whether a command line tool for converting tagged PDF to HTML would be of any use to anyone. The tool would run on the command line, and would not require additional components (i.e. it would run independent of something like Adobe Reader).
>
> Olaf
>
>
> Am 1 Mar 2013 um 04:09 schrieb accessys@smart.net:
>
>>
>> uh huh.  what else free on open source will work with eMACspeak or similar
>>
>> Bob
>>
>> On Thu, 28 Feb 2013, Karl Groves wrote:
>>
>>> Date: Thu, 28 Feb 2013 17:38:22 -0800
>>> From: Karl Groves <karlgroves@gmail.com>
>>> To: "accessys@smart.net" <accessys@smart.net>
>>> Cc: "[utf-8] Ramón Corominas" <listas@ramoncorominas.com>,
>>>    Ginger Claassen <ginger.claassen@gmx.de>,
>>>    "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>
>>> Subject: Re: Creating an accessible Table of Contents
>>> Ugh not this again.
>>>
>>> Karl Groves
>>> www.KarlGroves.com
>>> @karlgroves
>>> http://www.linkedin.com/karlgroves
>>> +1 410-541-6828
>>>
>>>
>>> On Feb 28, 2013, at 4:31 PM, accessys@smart.net wrote:
>>>
>>>>
>>>> won't work at all on Linux/Lynx
>>>>
>>>> Bob
>>>>
>>>>
>>>>
>>>> On Thu, 28 Feb 2013, [UTF-8] Ramón Corominas wrote:
>>>>
>>>>> Date: Thu, 28 Feb 2013 23:02:36 +0100
>>>>> From: "[UTF-8] Ramón Corominas" <listas@ramoncorominas.com>
>>>>> To: Ginger Claassen <ginger.claassen@gmx.de>
>>>>> Cc: "w3c-wai-ig@w3.org list" <w3c-wai-ig@w3.org>
>>>>> Subject: Re: Creating an accessible Table of Contents
>>>>> Resent-Date: Thu, 28 Feb 2013 22:03:08 +0000
>>>>> Resent-From: w3c-wai-ig@w3.org
>>>>> Hi, Ginger and all,
>>>>>
>>>>> I am not talking about the possibility of just reading the text of a PDF document, but about the possibility to read it in an accessible way. I've prepared a simple example of an "accessible" PDF document to illustrate the issue. You can access it here (I apologise in advance if I missed something and it's not completely accessible):
>>>>>
>>>>> http://ramoncorominas.com/stellar_classification.pdf
>>>>>
>>>>> This document has a 2-level heading structure, 2 links, an image with alternative text, several lists and a data table. Now, using MacOS:
>>>>>
>>>>> - Can you navigate the PDF structure using the headings?
>>>>> - Can you obtain a list of links? Can you activate those links?
>>>>> - Can you read the alternative text of the image? Do you even know that there is an image?
>>>>> - Can you navigate through lists and list items? Do you even know that there are lists?
>>>>> - Can you navigate the table and understand its data? Do you even know that there is a table?
>>>>>
>>>>> If the answer is "yes", please tell me how you do it. I'm sincerely interested on that, since I've not being able to find a tool that reads the PDF accessibility tagging on MacOS.
>>>>>
>>>>> If the answer is "no", then I cannot say that PDF accessibility features are "accessibility supported", unless they are only available in a closed environment only Windows platforms are used.
>>>>>
>>>>> Regards,
>>>>> Ramón.
>>>>>
>>>>> Ginger wrote:
>>>>>
>>>>>> Thanks for your input but you are quite wrong here. For blind MacOS users it is not necessary to spend any money on any kind of software in order to read a pdf document unless our Mac here in the office was magically equipped for us because they had a glass ball at Apple and knew that we are blind here. It is no problem at all to read those documents as long as they are readable i.e. are not composed out of graphics which would be the same for Windows users.
>>>>>> So, unless you ment something completely different which I did not understand you are wrong here.
>>>>>
>
>
>
>