Object Tags

Tables are labeled with a <Table> tag and contain <TH> and <TD> tags.

To determine if tables are tagged correctly:

> anywhere inside the table

R>

> Table Editor Properties

To determine if Table Header Cells are labeled correctly:

R> inside each Header Cell

> Table Cell Properties

Check to see if the Header Cell radio button is selected. If not:

> Header Cell radio button

> OK

When working with complex tables, always start by tagging Header Cells. A good rule of thumb is to start in the top left most cell and work across to assign column headers and then down to assign row headers.

To determine if Table Cells are labeled correctly:

R> inside each cell

> Table Cell Properties

> Data Cell radio button

NOTE: if Header Cells are assigned appropriately, all corresponding <TD> tags should be correct. If there appears to be missing <TD> cells throughout the table, assign Header Cells first and then recheck <TD> tags.

Row/Column span is used when cells are merged to indicate how many cells are associated with the merge.

To set Row/Column span:

R> inside the merged cells

> Table Cell Properties

If cells are merged in a row, modify the number in the dialogue box next to Row Span. If cells are merged in a column, modify the number in the dialogue box next to Column Span. Single column and row cells should have the number 1 listed for Row and or Column Span.

Scope refers to row or column and is typically used with Header Cells. If a Header Cell is a row header select the radio button for Row. If a Header Cell is a column header, select the radio button for Column. If a Header Cell spans both rows and columns, select the radio button for Both.

To assign Scope:

R> inside a Header Cell

> Table Cell Properties

> Header Cell radio button

> Row, Column, or Both (from the Scope drop down menu)

> OK

Complex tables with multiple layers of headers should include Assigned Header Cell IDs to help provide additional guidance on table navigation to assistive technology. To begin, start in the upper left corner of the table and work through, left to right, top to bottom to assign header cells.

Once Header Cells are assigned:

R> any data cell

> Table Cell Properties

> green + button associated with the Assign Header Cell IDs dialogue box

> Yes in the auto-generate IDs for header cells dialogue box

> green + button associated with the Assign Header Cell IDs dialogue box

> the IDs in reading order, relevant for the specific data cell

> OK

NOTE: Assistive technology reads from bottom to top. The first Header Cell ID to be read should be at the bottom of the list, followed by the next Header Cell ID in reading order until all Header Cell IDs are present.

While table summaries are optional, best practice is to fix a failed table summary that sometimes is identified by running an Accessibility Full Check. To fix:

> + (next to the Table Summary Fail indicator)

> Element 1

> Reading Order in the Tools Pane

R> grey box above table

> Edit Table Summary.

Provide a summary as you would any other alternative text

> OK

If content is in a bulleted or numbered list it should be tagged as a list (<L>) within the Tag Tree. Most frequently, if the Accessibility Checker indicates a fail it is because a List Item tag <LI> is not a child of a List tag <L>.

To fix:

Accessibility Checker

R> Element 1

> Show in Tags Panel (this highlights the incorrectly tagged <LI>)

From here there are two options. First, if a <L> tag already exists, drag and drop the <LI> tag to its appropriate location under the <L> tag. Second, if a <L> tag does not exist, one must be created.

To create:

R> <LI> tag

> New Tag

> List from the dropdown menu

< OK

A <L> tag will now appear in the tag tree; drag and drop the <LI> tag to its appropriate location under the <L> tag.

Lists must be labeled with a root <L> tag.

List Items must be labeled with a <LI> tag.

Complex lists can also contain optional List Body <Lbody> tags or List Label <Lbl> tags. If the <L> and <LI> tags are appropriately nested, check to ensure that the List Body <Lbody> of List Label <Lbl> tags are correctly listed as a child of a List Item tag <LI>.

To fix:

> + (to the left of the Lbl and Lbody – Failed)

R> the Lbl/Lbody 1

> Show in Tags Panel

Drag and drop the <Lbl> or >Lbody> tag to its appropriate location under the <LI> tag

Links should be embedded within the text using descriptive text. The following is an example of an embedded link:

Many helpful resources can be found on KPC’s website.

The Tag Tree includes URL within a content box and a <Link> –OBJR tag. The order of the URL and the <Link> - OBJR does not matter so long as they are both listed as a child of the parent <Link> tag.

If hyperlinks are created correctly in the Source Document, they will transfer correctly when the Source Document is saved as a PDF. When working with hyperlinks, you will need to turn on Tag Annotations within the Tag Tree.

To turn on Tag Annotation:

R> the root tag

> Tag Annotation

If you find that the Tag Tree is incorrectly tagged, the easiest solution is to fix the hyperlink in the Source Document and reconvert to a PDF. If the Source Document is not available, you can manually add links through the Edit PDF Tool.

To manually add tags

> Edit PDF Tool (located in the top toolbar)

> Link

> Add/Edit Web or Doc Link

Use crosshairs to select the underlines "link" in the text

Release the mouse to display the dialogue box

> Open a web page

> Next

Type in the short URL

> OK

Close Edit PDF Tool

Expand the Tag Tree

R> Add Tags to Doc

Links must also include alternative text. The alternative text should describe the link destination.

To add alternative text:

> <Link>

> Tag menu

> Properties

An Object Properties dialog box will open. Fill in the alternate text box with a description of the link

> OK