DHS-3418-SPA conformance report

What the validator failed, and what was done

Rule	veraPDF description	Before	Action
`7.1-3`	Content shall be marked as Artifact or tagged as real content	582	Untagged content was inspected operator by operator: every item was a path-painting operator (table rules, borders, fills), none was text. Each was wrapped as an Artifact so assistive technology skips it. No text was artifacted.
`7.2-9`	TD element should be contained in TR element	8	Cells that were nested directly inside other cells (a Designer export habit) were retyped as generic block containers, so their content belongs to the outer cell and the row structure is legal.
`7.4.2-1`	For documents that are not strongly structured, as described in ISO 32000-1:2008, 14.8.4.3.5, heading tags shall be used as follows: () If any heading tags are used, H1 shall be the first. () A document may use more than one instance of any specific tag level. For example, a tag level may be repeated if document content requires it. () If document semantics require a descending sequence of headers, such a sequence shall proceed in strict numerical order and shall not skip an intervening heading level. () A document may increment its heading sequence without restarting at H1 if document semantics require it	1	A heading that jumped a level (H1 to H3) was set to the level the outline implies (H2). Heading text was not changed.
`7.10-1`	Each optional content configuration dictionary that forms the value of the D key, or that is an element in the array that forms the value of the Configs key in the OCProperties dictionary, shall contain the Name key	1	The optional-content configuration received a Name.
`7.10-2`	The AS key shall not appear in any optional content configuration dictionary	1	The optional-content configuration's AS (usage application) array was removed, as PDF/UA requires.
`7.18.1-2`	An annotation (except Widget annotations or hidden annotations, or those having rectangle outside the crop-box) shall have either Contents key or an Alt entry in the enclosing structure element	2	Every Link annotation received a Contents entry: the visible link text under the link rectangle, or the destination URL where no text sits under it.
`7.18.5-2`	Links shall contain an alternate description via their Contents key as described in ISO 32000-1:2008, 14.9.3	2	Same fix as 7.18.1-2: a Contents entry on every Link annotation.

Language: the failure the validator cannot see

A validator checks that a language is declared. It cannot tell whether the declared language matches the text. This document declared: es-ES on the document and en-US on 9 elements. It now declares es on the document, and the language was set on every element from its own text: 555 elements marked Spanish, 9 marked English, 9 stale declarations removed so the element inherits correctly.

Page	Element	Before	After	Text (start)
1	`H1`	inherited	es	Renovación de los programas de atención médica de Minnesota para personas que recibenasistencia médica y tiene
1	`H2`	inherited	es	¿Por qué he recibido este formulario de renovación?
1	`P`	inherited	es	Debe llenar este formulario para renovar su elegibilidad al Programa de Medical Assistance (MA) o al Programa
1	`H2`	inherited	es	¿Qué necesito hacer con este formulario?
1	`P`	inherited	es	1. Lea cada pregunta y responda a todas las que le correspondan. Si necesita más espacio, escriba el número de
1	`P`	inherited	es	2. Posiblemente deba enviarnos comprobantes de cierta información. Envíe copias de los comprobantes. No envíe
1	`P`	inherited	es	3. Firme y feche el formulario de renovación de la página 12.
1	`P`	inherited	es	4. Lea el Aviso de Prácticas de Privacidad y el Aviso de Derechos y Responsabilidades del Anexo A. Arranque es

Title: DHS-3418-SPA (Renovación de los programas de atención médica de Minnesota para personas que reciben asistencia médica y tienen 65 años o más y personas ciegas o discapacitadas (MA-ABD)) → Renovación de los programas de atención médica de Minnesota, MA-ABD (DHS-3418-SPA), and the viewer is set to display it.

Findings

The published file already claimed PDF/UA-1 conformance.

Its XMP carried pdfuaid:part=1 while veraPDF reported 7 failed rules and 597 failed checks. A conformance claim that a validator refutes is worse than no claim: it tells a buyer's checker the vendor never ran the validator.

Element-level language contradicted the document.

The document declared es-ES, but nine elements carried en-US, and element-level language wins. Those nine were the English-language agency names and addresses, which are correctly English; 555 Spanish elements now carry es explicitly, so nothing depends on inheritance.

Cells nested inside cells.

Eight table cells sat directly inside other cells rather than in a row, a LiveCycle Designer export habit. They were retyped as block containers inside the outer cell, which is what they are.

Untagged table graphics.

582 path-painting operators (form rules, boxes, borders) were outside the tag tree and are now artifacts. No text was untagged.

Not covered by this pass

Reading order was not re-sequenced. The existing tag order was kept.
Alternate text was not written or rewritten. Existing alternate text was kept as published.
Table header scope was assigned by position (first row = column headers, leading cell = row header). A human check against the visual table is recommended for complex tables.
No content was translated, corrected or rewritten. Where the published file contains untranslated or outlined text, this report says so; fixing it needs the issuer's source.
Form-field tooltips (Designer forms) were kept as published; their language and wording were not reviewed.

A PASS from veraPDF means the file has no machine-detectable defect against ISO 14289-1. It does not by itself mean the document is usable; the findings above are the part a validator cannot judge, and they are why a human pass exists.

Renovación de los programas de atención médica de Minnesota (MA-ABD)