Thread Subject: Re: Group D: 22(d) Readable without stylesheets
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Loretta Guarino Reid
Date: Wed, Dec 27 2006 5:10 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: David Poehlman: "Re: Group D: 22(d) Readable without stylesheets"
- Previous message in thread: David Poehlman: "Re: Group D: 22(d) Readable without stylesheets"
- Messages sorted by: Author | Thread | Date
To use PDF as an example, the reading order of a PDF file is
programatically determined if it is a Tagged PDF file; if the PDF is
not tagged, then heuristics must be used to decide on a reading order.
However, just having a programatically determined reading order is not
sufficient, since it is possible to tag a PDF file in a way that
doesn't reflect its contents logically or to use layout tables to
create HTML files where the source order does not read logically.
The proposal requires both that the reading order be programatically
determined, and that the reading order "make sense".
On 12/27/06, David Poehlman < = EMAIL ADDRESS REMOVED = > wrote:
> Sorry, I understood that if the reading order where programatically
> determinable that I'd see it reflected possitively in apps which take
> that approach.
> On Dec 27, 2006, at 3:05 PM, Andrew Kirkpatrick wrote:
> I need examples and assurance that the reading order can be
> programatically determined. I believe adobe have tried this and not
> done well.
> I'm not sure what you mean. I believe that Adobe has done this with PDF
> and with Flash -- if you experience issues with the reading order for a
> document or application in either of these formats it is _because_ the
> reading order can be programmatically determined that you are able to
> make that determination. You may not like the reading order that is
> provided, but this is an issue with the document or application, not the
> This is the exact point that this standard is attempting to address, I
- Next message in Thread: David Poehlman: "Re: Group D: 22(d) Readable without stylesheets"
- Previous message in Thread: David Poehlman: "Re: Group D: 22(d) Readable without stylesheets"