Working with Taglines

Element/Attribute	Usage
Tagline	The Tagline element is optional; however, it is present on all base documents. The default behavior is to exclude the tagline from screen readers when the Tagline element is used without the ReadElement attribute.
ReadElement	The attribute is optional. When the ReadElement attribute is used on the Tagline element, and defined with a value of Yes, the tagline is included for reading. If the ReadElement attribute is present on the Tagline element, and defined with a value of No, the tagline is excluded from screen reading.

The tagline element on a document is not read by screen readers. To include the tagline element as a readable tag you must set the ReadElement attribute on the tagline. The tagline element does not include the ReadElement unless specifically added during authoring.

On the Tagline element, the ReadElement attribute is used to define the tagline for availability to screen reader applications. The ReadElement attribute provides a Yes/No value pair with the default value as Yes. Including the tagline for reading is defined by the ReadElement attribute with a Yes value. To exclude the tagline as a read element, define the attribute as No.

Note: If the ReadElement attribute is not present on the Tagline element, the tagline will not be read by screen reading tools.

The ReadElement attribute is available within the Tagline element. Right-click the Tagline element and select Add Attribute > ReadElement.

In the ReadElement attribute you can select the attribute value as Yes or No. The default value is Yes (ReadElement = Yes). To modify the attribute value, select the attribute and double-click (in this case, the available values are Yes/No).

When producing a Tagged PDF (see Creating a Tagged PDF), tags are not created in the structure tree for tagline information if the ReadElement value is No (or not present in the REQ file). If the ReadElement value is Yes, tags generate for all of the pages tagline information and all are placed at the top of structure tree.

Embedded PDF Documents

EmbeddedPDF documents may have a tagline. Expere engine controls a list of field names that will not be tagged and read aloud. The list includes any fields starting with the following:

Form_UserDefined_Left
Form_UserDefined_Center
Form_UserDefined_Right
Form_CustomBrandTag
Form_WarrantyControl
Form_Barcode

Any of these fields may be present in multiple locations, but the field name must be unique (e.g. unique numeric indicator, such as Form_Barcode_1, Form_Barcode_2, etc.

Note: The fields specified above are named when the PDF used in the REQ file is created.