WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tagging nomenclature

for

From: chagnon@pubcom.com
Date: Apr 18, 2020 8:02PM

Building on Jonathan's comments, the grouping tags are used like this
example:

Tags
<Document> Should encase all of the tags in the entire document
<Art> Which is an article, not artwork.
Should group an entire story, from its heading to
the end.
<Hx>
<P>
Followed by more regular element tags, <L>, <Table>
and others.
<Sect> A small section of content related to the
article/story.
Common example is a sidebar to a story.

The <Part> tag is for a major section of a large document. Examples: a
chapter of a book, a department in a magazine.

<Div> is not well defined in PDF/UA and is not recognized by AT, so we don't
recommend its use in most PDFs.

- - -
Bevi Chagnon, founder/CEO | <EMAIL REMOVED>
- - -
PubCom: Technologists for Accessible Design + Publishing
consulting . training . development . design . sec. 508 services
Upcoming classes at www.PubCom.com/classes
- - -
Latest blog-newsletter - Accessibility Tips at www.PubCom.com/blog

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
Jonathan Avila
Sent: Saturday, April 18, 2020 6:55 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Tagging nomenclature

Hi Laurie, the Tagged PDF Best Practice Guide: Syntax
Document<https://www.pdfa.org/wp-content/uploads/2019/06/TaggedPDFBestPracti
ceGuideSyntax.pdf> from the PDF Association give some information about
structure and grouping. In terms of titles for tags - I suggest picking
something that works best for you to help you understand what is covered
without having to expand the elements. Titles might also be helpful to
someone else who you are working with to remediate or someone who might come
after you to remove the tags tree to quickly locate portions of the
document. I find that when element highlight is on in large documents and
tags have to be expanded Acrobat can be slow - so naming can help you
quickly jump around without having to use the highlight feature or expand
the tag. The title's won't be visible to users of assistive technology when
reading a document though - but they would be visible to anyone who looked
in the tags structure - so be mindful of comments.

Jonathan

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
Laurie Kamrowski
Sent: Saturday, April 18, 2020 5:56 PM
To: <EMAIL REMOVED>
Subject: [WebAIM] Tagging nomenclature



CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.





Hi everyone!



I am remediating PDFs and I was wondering if there is a recommended
structure for organizing tags? I know that you can actually name them, and I
have when tagging a table by hand, but is there an actual industry standard?
I've checked W3 but the only thing I've found is this article about PDF
techniques for WCAG 2.0 <https://www.w3.org/TR/WCAG20-TECHS/pdf#PDF2>.



I have been using a method when I name every tag by page number and in what
order it appears in the document.



Example:



(This is what my tags panel inside the Accessibility tool looks like in one

document)



[Tags]

[<Part> Chapter 5]

indent [<Sect> Page 12]

indent indent [<H1> 12.1]

indent indent [<H2> 12.2]

indent indent [<P> 12.3]

indent indent [<P> 12.4]

indent [<Sect> Page 13]

indent indent [<P>13.1]

indent indent [<P> 13.2]



End example



I think this system should work for most articles and things that I work on,
but I probably will encounter something that completely negates this.



Laurie Kamrowski

She/Her/Hers

Accessibility Specialist

Mid Michigan College


http://webaim.org/discussion/archives

<EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
http://webaim.org/discussion/archives