BETA release
G2_F03 Graphics representing text incorrectly tagged as figure
PDF-F4
FAIL
Use case(s): Fundamental 2: Text
Last updated on January 3, 2025
Description
This example demonstrates the failure condition that applies for non-text content that is intended to be consumed as text, but appropriate ActualText is missing. In this example, graphics were used to place the word "paragraph" on the page, instead of text objects. In this case the related non-text content is incorrectly tagged as a Figure with alt text.
Download(s)
These minimal examples are designed to express a single Technique. Effective use requires software that supports Tagged PDF.
Test(s)
Expected Results
Although checks #2 and #4 are true, checks #1 and 3 are false.
Procedure
- Check that the related characters are present as extractable characters for content intended to be consumed as text.
- 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:
01-006- 08-001
- 08-002
10-001- 11-001
- 11-006
- 13-007
- 13-008
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_F03
NOTE: the “technique support finder” concept was introduced in January 2025; please allow time for adoption.
Related Techniques
PDF103 All use cases
Visit the PDF Accessibility LWG’s public GihHub repo
List of All Techniques