W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2011

Re: PDF Technology Notes -- Re: 9 June 2011 Agenda ==============================

From: Chris Beer <chris@e-beer.net.au>
Date: Fri, 10 Jun 2011 06:00:23 +1000
Message-Id: <C76BBC00-8161-47AF-B046-AB61ABCD7411@e-beer.net.au>
Cc: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
To: Shawn Henry <shawn@w3.org>
<snip>
>> 
>>> 
>>> 3. Current wording: "An accessibility application can extract the content
>>> of a document for presentation to users with disabilities by traversing
>>> the structure hierarchy and presenting the contents of each node."
>>> 
>>> Issue: What is an "accessibility application" here? Really, you mean
>>> screen reader, yes? Given that user agents and assistive technologies do
>>> not currently provide the customization needed by some people with low
>>> vision, I think it’s not appropriate to say "for presentation to users
>>> with disabilities".
>>> 
>>> Suggested re-wording: "For example, screen readers can extract the content
>>> of a document by traversing the structure hierarchy and presenting the
>>> contents of each node."
>>> (I tried "For example, screen readers can extract the content of a
>>> document for presentation to users who are blind by traversing the
>>> structure hierarchy and presenting the co,ntents of each node." but that
>>> leaves out sighted people who use screen readers because of cognitive
>>> disabilities – but maybe OK since it starts with "For example". Also tried
>>> "For example, screen readers can extract the content of a document by
>>> traversing the structure hierarchy and presenting the contents of each
>>> node auditorilyy." but that leaves out dynamic braille. If really don't
>>> want to say screen readers, could say "some assistive technologies"...)
>>> 
>>> 
>> How about: "PDF includes several features in support of accessibility of
>> documents to users with disabilities. The core of this support lies in the
>> ability to determine the logical order of content in a PDF document,
>> independently of the content's appearance or layout, through logical
>> structure and Tagged PDF. For this reason, producers of PDF files must
>> ensure that all information in a document is reachable by means of the
>> structure hierarchy. In doing so, assistive technologies can be used to
>> present PDF to users in the much the same manner as they would access
>> other formats such as HTML markup or document files."
> 
> SLH: First part seems good. However, "assistive technologies can be used to present PDF to users in the much the same manner as they would access other formats such as HTML markup or document files" does not work at all because of the low vision issue. It implies that people with disabilities can have PDF presented like HTML and document files, but we can't -- the latter two offer extensive flexibility in text customization but PDF currently offers insufficient text customization for many people. Could say, "some assistive technologies can provide information about the structured hierarchy of the document." or "people using some assistive technologies can get information according to the structured hierarchy of the document" or such (that includes "some"!).
> 
> Regards,
> ~Shawn
> 
> 

ceb - Good point - some is needed there.


>> 

Chris
Received on Thursday, 9 June 2011 20:00:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 June 2011 20:00:30 GMT