Rich-text fields need a plain-text value

PDF/UA check TEXT_FIELD_RV_REQUIRES_V · Forms · severity High · PDF/UA 8.10.3.3 Text fields · advanced check

↩ Back to the rules index · WCAG cross-reference

Advanced check. This is a file-internals rule. It is hidden from the standard report view and generally indicates a problem with the tool that produced the PDF rather than something an author did.

Why it matters#

Rich-text-only fields are inaccessible to text-only assistive technology. A plain-text /V parallel makes the content available to all AT.

What you will see#

A text field stores a rich-text value with no plain-text equivalent alongside it.

How to fix#

Add a /V entry to the text field dictionary containing the plain-text equivalent of the /RV rich-text value, and keep the two textually identical. Alternatively, remove /RV if rich text formatting is not needed.

Step-by-step guide#

1. Identify the flagged text fields: they carry an /RV (rich text value) entry without a matching /V entry. In Acrobat, rich-text fields show Allow Rich Text Formatting checked under All tools > Prepare a form > field Properties > Options.
2. The compliant state adds a /V entry containing the plain-text equivalent of the /RV value (strip the XHTML markup, keep the text). ISO 14289-2 section 8.10.3.3 requires that when RV is present, V shall also be present and the two shall be textually equivalent.
3. Acrobat fix: open the form, re-enter the field's content while filling it in, and save - Acrobat writes both V and RV when a rich text field is filled.
4. If rich formatting is not actually needed, take the other allowed path: untick Allow Rich Text Formatting in field Properties > Options and re-enter the value so only a plain /V remains.
5. If any workflow later regenerates the rich text value, make it update /V in the same operation so the two entries never diverge.

Verify: Re-run the EQChecker scan in advanced mode: TEXT_FIELD_RV_REQUIRES_V should report zero errors. Inspect the field dictionary (Preflight > Browse internal structure) to confirm /V exists and its text matches /RV.

Note: The rule only fires on fields that have /RV; plain text fields with just /V are unaffected. EQChecker checks presence of /V, not equivalence, but the standard requires textually equivalent values - the same characters once formatting is removed; a summary or truncation of the rich value does not conform.

WCAG success criteria#

4.1.2 Name, Role, Value — Level A#

Every UI component must expose a correct name, role, and (where relevant) state/value to assistive technology.

Understanding 4.1.2

Standards#

This check contributes to the following standards:

PDF/UA WCAG A EN 301 549