BETA release
G2_02 Text content correctly tagged (one container per word)
PDF102
Use case(s): Fundamental 2: Text
Last updated on January 3, 2025
Description
The objective of this technique is to show how to tag text content, so that it is machine-readable. In this example, each word is created in a separate container. All of the containers that semantically belong together are contained in one P tag.
Download(s)
These minimal examples are designed to express a single Technique. Effective use requires software that supports Tagged PDF.
Test(s)
Expected Results
Checks #1 through #4 are all true.
Procedure
- For content intended to be consumed as text, check that text is extractable.
- Check that Unicode can be derived for any text content.
- Check that the extractable characters match their visual appearance.
- Check that the Natural Language is set for any text content.
Application to WCAG 2.x
This Technique addresses the following WCAG 2.x Success Critieria:
Matterhorn Protocol
The Matterhorn Protocol 1.1 provides an algorithm for conformance with PDF/UA-1. Matterhorn checkpoint(s) (human or machine) relevant to this use-case:
- 08-001
- 10-001
- 11-001
- 11-002
- 11-003
- 11-006
Accessibility Technique Support Finder
Accessibility Technique Support Finders allows you to quickly locate software and services that claim to support a given Technique. Simply search the internet with a given technique’s finder together with the name of your product.
The technique finder for this Technique is: UA1_Tpdf-G2_02
NOTE: the “technique support finder” concept was introduced in January 2025; please allow time for adoption.
Related Techniques
All use cases
Visit the PDF Accessibility LWG’s public GihHub repo
List of All Techniques