CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 date: Sat, 11 Oct 2025 04:34:33 GMT content-type: text/html; charset=utf-8 content-encoding: gzip content-location: PDF13.html vary: negotiate,Accept-Encoding,Origin tcn: choice last-modified: Thu, 05 Sep 2013 16:02:32 GMT cache-control: max-age=31536000 expires: Sun, 11 Oct 2026 04:34:33 GMT access-control-allow-origin: * x-backend: www-mirrors x-request-id: 98cba54b1b4fc46e strict-transport-security: max-age=15552000; includeSubdomains; preload content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests cf-cache-status: BYPASS set-cookie: __cf_bm=LtiEU8_zj.ABUR9Ik.3.iFaqDPZZ9zmsnzR01FBQ1nc-1760157273-1.0.1.1-ShkHNyelhZLc23HrlksYMHjcoRKcOGUiEIIVVb6a6LrFIi_IZrjBkfqHANJ7PmsU5TTd57ZAnrkJ_esWvd_mB09OKOBEKuqc5ORlezhjslI; path=/; expires=Sat, 11-Oct-25 05:04:33 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare cf-ray: 98cba54b1b4fc46e-BLR alt-svc: h3=":443"; ma=86400 PDF13: Providing replacement text using the /Alt entry for links in PDF documents | Techniques for WCAG 2.0

Skip to Content (Press Enter)

On this page:

PDF13: Providing replacement text using the /Alt entry for links in PDF documents

Applicability

Tagged PDF documents that contain links.

This technique relates to:

User Agent and Assistive Technology Support Notes

See PDF Technology Notes for information on user agent and assistive technology support.

Description

The objective of this technique is to provide replacement link text via the /Alt entry in the property list for a tag. This is usually not necessary, but in some situations, additional information beyond the visible link text is needed, particularly for screen reader users. Screen readers can read visible link text, but replacing the screen text with meaningful alternate text for links in a PDF document can make links more accessible.

Links in PDF documents are represented by a Link tag and objects in its sub-tree, consisting of a link object reference (or Link annotation) and one or more text objects. The text object or objects inside the Link tag are used by assistive technologies to provide a name for the link.

Authors can replace the default link text by providing an /Alt entry for the Link tag. When the Link tag has an /Alt entry, screen readers ignore the value of any visible text objects in the Link tag and use the /Alt entry value for the link text.

The simplest way to provide context-independent link text that complies with the WCAG 2.0 success criteria is to create them when authoring the document, before conversion to PDF. In some cases, it may not be possible to create the links using the original authoring tool. When editing PDF documents with Adobe Acrobat Pro, the best way to create accessible links is to use the Create Link command.

Authors should make sure that the alternate text makes sense in context of the screen text before and after the link.

Examples

Example 1: Adding alternate link text using Adobe Acrobat 9 Pro

This example is shown with Adobe Acrobat Pro. There are other software tools that perform similar functions. See the list of other software tools in PDF Authoring Tools that Provide Accessibility Support.

The image below shows a document converted to PDF from Oracle Open Office. Note that the visible link text is the URL for the link target. A screen reader will read the entire URI as the link text.

A document with the link URI as the link text.

To create more accessible link text for assistive technology:

In the View menu, open the Tag panel by selecting Navigation Panels > Tags.
Locate the Link tag in the tag tree, access the context menu for the link, and select Properties.
In the TouchUp Properties dialog, in the Tags tab, enter replacement text in the Alternate Text field. Screen readers will read this text instead of the entire URI.

The next image shows the Link tag structure in the Tag panel.

The Link tag structure in the tag panel.

The last image shows the Alternate Text specified in the Link tag's TouchUp Properties dialog. A screen reader will read the Alternate Text as the link text.

The new Alternate Text: 'Boston Globe technology page'

This example is shown in operation in the working example of adding alternate link text (OpenOffice file) and working example of adding alternate link text (PDF file).

Example 2: Adding alternate link text in a PDF document using the /Alt entry

The following code fragment illustrates code that is typical for alternative text for a link. This is typically accomplished by an authoring tool.

32 0 obj
<<
  /S/URI                                       %Action type (required), must be URI for a URI action
  /URI(https://www.boston.com/business/technology/)  %Uniform resource identifier(required), the URI to be resolved
>>
endobj

The following illustrates how to specify alternate text for the URL in the above link:

11 0 obj
<<
  /Alt(Boston Globe technology page)    %Alternate text entry
  /K [ 1                                                      
       <<
         /Obj 27 0 R
         /Type /OBJR            %Object reference to the link
       >>
       ]                       
  /P 12 0 R
  /Pg 18 0 R
  /S
  /Link
>>
endobj

Resources

Resources are for information purposes only, no endorsement implied.

Section 14.9.4 (Replacement Text) in PDF 1.7 (ISO 32000-1)
PDF and Accessibility

Tests

Procedure

For the hyperlink, verify that the alternate link text is properly coded by one of the following:
- Read the PDF document with a screen reader, listening to hear that the alternate link text is read correctly.
- Use a tool that is capable of showing the /Alt entry to open the PDF document and view the hyperlink and alternate link text.
- Use a tool that exposes the document through the accessibility API and verify that the alternate link text is the text for the link.

Expected Results

#1 is true.

If this is a sufficient technique for a success criterion, failing this test procedure does not necessarily mean that the success criterion has not been satisfied in some other way, only that this technique has not been successfully implemented and can not be used to claim conformance.

Techniques are Informative

Techniques are informative—that means they are not required. The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard—not the techniques. For important information about techniques, please see the Understanding Techniques for WCAG Success Criteria section of Understanding WCAG 2.0.

This Web page is part of Techniques and Failures for Web Content Accessibility Guidelines 2.0. The entire document is also available as a single HTML file. See the The WCAG 2.0 Documents for an explanation of how this document fits in with other Web Content Accessibility Guidelines (WCAG) 2.0 documents. To send public comments, please follow the Instructions for Commenting on WCAG 2.0 Documents.

Original Source | Taken Source