I'm trying to figure out a way to create a more accessible map, and I'm using a subway map because it's less complicated than a metropolitan map. It seems to me that if the image for a document is the primary reason for using said document, then it would stand to reason that the image should also be accessible.
I opted to use a list to create the subway, and I don't know if it's any more or less usable to someone with a visual impairment. My other problem is the fact that trains go from point 'A' to 'Z' and then back again. I wasn't sure how to go around that, but I tried to number the stops so they could be more identifiable.
My other problem is that I don't have JAWS or Window Eyes to see what it looks like in those programs. Adobe's Read Out Loud doesn't seem to be able to skip content, so I'm not finding it very useful.
I'm just doing this to see if it can be done, and I'm wondering if anyone can provide some insight to doing this. I haven't found much help out there in terms of creating an accessible map.
I used a Boston MBTA map as the source, and tried to re-create the whole document to be Section 508 compliant. Any help would be much appreciated!
You can download the map on my web site:
http://jonathanmetz.com/creating-an-accessible-map/
Thanks in advance!
Jonathan
Creating an Accessible Map
2011-12-15 12:04:50
Answered
My Product Information:
Acrobat Pro 9.4.3, Macintosh
Acrobat Pro 9.4.3, Macintosh
2011-12-18 07:55:03
#2
Daka,
Thanks for the feedback. First, thank you for clarifying the notion of THead and TFoot. I was under the impression that those had to be placed in order to create a more accessible table. When looking at the PDF for 'Creating an Accessible PDF with CS4,' they mark up a list with only L and LI elements, but at some point I saw a post of yours mentioning that there was a correct way to create a list and included a worksheet PDF on doing so. I guess I over indulged in tagging with the table out of fear that the normal way to do tables. I'll make those changes to the table, and upload it again.
In your opinion, is my List also overly complex? Will screen readers be able to see the extra information I put in there, and most importantly, do you think they would be useful?
I have recently read the ISO 32000 offered by Adobe, and found it to be useful. I'm looking forward to checking out Part 2 when it becomes available.
As an aside, I didn't realize that this was a support forum, and was intending for this to be a request for collaboration of sorts. I'll look at the Forum and see if there is a better place to put this sort of thing. In the meantime, I will mark your answer as 'Accepted,' but welcome any further feedback on this project.
Again, thanks for your help.
Thanks for the feedback. First, thank you for clarifying the notion of THead and TFoot. I was under the impression that those had to be placed in order to create a more accessible table. When looking at the PDF for 'Creating an Accessible PDF with CS4,' they mark up a list with only L and LI elements, but at some point I saw a post of yours mentioning that there was a correct way to create a list and included a worksheet PDF on doing so. I guess I over indulged in tagging with the table out of fear that the normal way to do tables. I'll make those changes to the table, and upload it again.
In your opinion, is my List also overly complex? Will screen readers be able to see the extra information I put in there, and most importantly, do you think they would be useful?
I have recently read the ISO 32000 offered by Adobe, and found it to be useful. I'm looking forward to checking out Part 2 when it becomes available.
As an aside, I didn't realize that this was a support forum, and was intending for this to be a request for collaboration of sorts. I'll look at the Forum and see if there is a better place to put this sort of thing. In the meantime, I will mark your answer as 'Accepted,' but welcome any further feedback on this project.
Again, thanks for your help.
2011-12-18 11:27:59
#3
Actually, neither the AUC nor the Adobe U2U Acrobat Forums are "support" forums in the formal, you pay for it, Adobe support sense. Fundamentally, both are "collaborative" venues for end-users. In context of that, there are periodic posts to a thread by Adobe staff (although here at AUC there are frequent replies by the staff that perform moderator duties).
Some AUC members sport an AUC Expert and/or an AUC Team "badge". This population consistes of both non-Adobe and Adobe personnel.
Basically, other users interested in helping resolve issues through collaboration.
.
So, your posts (in the Accessibility forum of AUC)make sense.
Particularly so, as (currently) there is no other adequate venue comparable to the AUC's Accessiblity Forum for fairly "interactive" Q&A and discussion of Tagged (Accessible) PDF.
As well, there is the AUC's Learning Center.
.
With that said there is a phletora of "how-to" on the web vis-a-vis accessible PDF.
Alot at the dot GOV and dot EDU.
While some is spot on, much is stale, "off", or otherwise less than "usable".
(e.g., the VA "checklist" - it'd take something of an epistle to catagorize what is so very amiss with it.)
For Tagged output PDF you just gotta use ISO 32000 as the "foundation".
.
Having an interest in Accessible PDF you might visit http://pdf.editme.com/
.
Post ISO 14289-1 release by ISO there will be information available at:
http://www.aiim.org/resources/standards/committees/PDFUA/App-Notes
Some AUC members sport an AUC Expert and/or an AUC Team "badge". This population consistes of both non-Adobe and Adobe personnel.
Basically, other users interested in helping resolve issues through collaboration.
.
So, your posts (in the Accessibility forum of AUC)make sense.
Particularly so, as (currently) there is no other adequate venue comparable to the AUC's Accessiblity Forum for fairly "interactive" Q&A and discussion of Tagged (Accessible) PDF.
As well, there is the AUC's Learning Center.
.
With that said there is a phletora of "how-to" on the web vis-a-vis accessible PDF.
Alot at the dot GOV and dot EDU.
While some is spot on, much is stale, "off", or otherwise less than "usable".
(e.g., the VA "checklist" - it'd take something of an epistle to catagorize what is so very amiss with it.)
For Tagged output PDF you just gotta use ISO 32000 as the "foundation".
.
Having an interest in Accessible PDF you might visit http://pdf.editme.com/
.
Post ISO 14289-1 release by ISO there will be information available at:
http://www.aiim.org/resources/standards/committees/PDFUA/App-Notes
2011-12-18 12:19:17
#4
I'm glad someone else recognizes the issues with the VA checklist!
I recently joined the W3C community group on creating accessible inforgraphics, and I'm eager to see what sort of collaboration that turns into. Ad for the editme link, I've never looked outside of the /UA section before. There is actually a lot of cool stuff on there I'll check out.
Again, thanks for your help.
Jonathan
I recently joined the W3C community group on creating accessible inforgraphics, and I'm eager to see what sort of collaboration that turns into. Ad for the editme link, I've never looked outside of the /UA section before. There is actually a lot of cool stuff on there I'll check out.
Again, thanks for your help.
Jonathan
.
Just my observation; but, you've really over complicated the Table element's child structure.
While a well-formed Tagged output PDF provides a wealth of "stuff" the unfortunate truth is that most AT, most times harvests the wind-fall and low hanging fruit of the tree.
Consequently, simple is better.
Also, use of a complex table structure generally results in a need to use of Header IDs.
.
As the "fare table" does not split across multiple pages you could avoid use of <THead>, <TBody>, and <TFoot>.
A <Table> with child <TR> elements would be adequate.
The first row would be the header row (for Paying With, Subway Trip, Local Bus and Subway).
Five additional rows would hold the <TD> cells.
Tag "VALID PASSES: .... " with the <P> element.
.
Table 337, Standard structure types for table elements of ISO 32000-1 identifies that, when used in a Table, there is only one <THead> and only one <TFoot>.
(The Table in the PDF has multiple THead elements.)
.
When THead is used, there can be one or more TBody elements. TFoot is optional.
These three provide an explicit grouping of header rows, body rows, and footer rows respectively.
.
When a table splits across multiple pages the use of THead, TBody, and TFoot support:
Explicit grouping of header rows which supports redraw at the top of each table fragment.
Explicit grouping of footer rows which supports redraw at the bottom of each table fragment.
Explicit grouping of body rows which supports the body area being broken apart on a row boundary.
Multiple TBody elements support drawing of a border or background for a set of rows.
.
.
A sidebar of me nattering...
Worth a note — When making Tagged output PDF or post-processing Tagged PDF only one Standard is applicable.
Specifically, that is ISO 32000. Part I (32000-1) is the current ISO Standard. Part II (32000-2) looks to be well on its way to release in 2012.
Tagged PDF provides several functionalities. One of which is Accessible PDF. A well-formed Tagged PDF (per the ISO Standard) establishes an Accessible PDF.
The core discussion of Tagged PDF is in Section 14 of the ISO Standard.
Adobe has a free, ISO approved, copy of ISO 32000-1 available.
.
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_2008.pdf
.
ISO 14289-1, for PDF Universal Accessibility is anticipated to be released in 2012. This ISO standard will provide focus on Accessible PDF.
So, ISO 32000 establishes "Tagged" PDF and ISO 14289 will establish, in context of ISO 32000, what "Accessible" PDF is.
With that understood it becomes clear that achieving the well-formed Tagged PDF (and thus the Accessible PDF) is not accomplished by apply protocols associated with other markup languages.
That'd be like trying to fit Cinderella's slippers on the feet of the step-sister, eh.
Be well...