PDF/UA and accessible document checks

PDF/UA defines requirements for accessible PDF, while useful accessibility also depends on the quality of the content and structure. A conformance claim should refer to the final file and a suitable review process.

The distinction that matters

PDF/UA belongs to the ISO 14289 family identified by the PDF Association. It should not be confused with PDF/A or with an ordinary tagged export. The purpose is accessible use, which means the document's machine-readable relationships matter alongside its visual appearance. A check that only looks for a title or a tag tree is incomplete.

For an operator, the practical starting point is the reader's task. Can they find headings, follow the intended sequence, understand a chart, identify form fields, and interpret a table? Automated tools can help detect missing or inconsistent structure, but the usefulness of a description or the sense of a reading order often needs human judgment.

Treat the document as a maintained artifact. A later merge, extraction, or rasterization can invalidate the assumptions behind an earlier review. If your workflow adds appendices after validation, the combined file needs its own checks. Pagestays does not advertise accessibility certification and does not promise to preserve tags through page assembly.

A worked example

Consider a hypothetical application form with a name field, a required selection, and an explanatory chart. A visual reviewer confirms that the form looks neat. An accessibility reviewer also checks field labels, required-state information, keyboard sequence, and a useful alternative to the chart. These are distinct acceptance criteria. Filling the fields correctly does not prove the blank form was accessible, and flattening it changes the interaction again.

Keep accessibility in the acceptance criteria

A readable-looking PDF can still be difficult to use with assistive technology. Meaningful headings, reading order, language, table structure, and text alternatives help a reader understand relationships that visual layout alone cannot express. Tags are useful structural information, but merely detecting a tag tree is not a complete accessibility review.

Start in the source document when possible. Proper headings, sensible table construction, descriptive links, and useful alternative text are easier to maintain before export than to reconstruct from a finished visual page. Export with the application's appropriate structure settings, then inspect the resulting PDF. A print-to-PDF path can produce a different artifact from a structured export.

After editing, check the features the workflow depends on. Merging or extracting pages can affect structure and navigation. Rasterizing a page removes the underlying text and relationships unless a separate process reconstructs them. OCR may recover characters, but it does not automatically recover a correct heading hierarchy, a complex table, or a meaningful image description.

Use both automated checks and human review for a consequential accessibility requirement. A tool can detect some missing properties while failing to judge whether an alternative description is useful or a reading sequence makes sense. Pagestays is a utility collection, not an accessibility remediation or certification service. If accessibility is required, preserve the original structured source and validate the final deliverable with the appropriate process.

Verify field values and their appearance

Interactive forms separate a stored value from the way that value is drawn. A field can contain the right text but show an outdated or clipped appearance in a particular viewer. After filling a form, save it and reopen the copy. Check long names, addresses, accented characters, multiline entries, and selected options instead of testing only a short familiar word.

A form-looking page is not necessarily interactive. A scan can contain empty printed boxes without any field objects. Adding a visible text annotation on top is a different task from updating a field value. Some receiving systems need the structured values, while others accept a readable completed page. Follow the publisher’s instructions before substituting one approach for the other.

Specialized forms may depend on calculations, scripts, dynamic layout, or a particular viewer. Pagestays supports common AcroForm fields, not XFA or every scripted behavior. If a total fails to update or part of the form is missing, do not assume that saving will fix it. Use the publisher-recommended software or ask for a compatible form.

Flattening is a deliberate final step when interactivity is no longer needed. It can make the visible values less dependent on form rendering, but it also removes the ability to edit those fields as fields. Keep the fillable original and a completed editable copy if future corrections are likely. A fixed appearance is not a certificate, a security policy, or proof that the form was completed by a particular person.

Preserve context, not only a file extension

An archive needs more than a document that opens today. The file should retain the information necessary to interpret it, and the organization should know where it came from, which version it represents, and what transformations were applied. A readable PDF is useful, but its extension alone does not establish a preservation policy or standards conformance.

Keep the source and record the purpose of any derivative. A small reading copy can be appropriate for sharing while a higher-quality master remains the preservation reference. Do not discard an original scan simply because a compressed output looks similar at normal zoom. Fine annotations, marginal notes, and tonal differences can carry information that becomes important later.

If a standard is required, identify the exact family and conformance target. PDF/A concerns long-term preservation, PDF/UA concerns accessibility, and PDF/X concerns print exchange. They are not interchangeable badges. A conversion should be followed by a validator appropriate to the target, and a later edit can require validation again.

Plan for retrieval as well as storage. Use meaningful filenames, stable descriptions, and controlled locations so someone can find the right document later. Metadata can help, but it should agree with the visible content and organizational records. Pagestays can change ordinary document information and create useful derivatives; it does not certify an archival collection or replace a records-management process.

Check more than the visible page

A PDF can carry a visual page and a separate structure for interaction and interpretation. Links, bookmarks, form widgets, tags, and document metadata do not all live in the same place as the text and images you see. An operation that copies or redraws page content can produce a convincing picture while leaving some of those other features behind.

Decide which features are part of the acceptance test. If readers need to follow a contents page, try its links. If a form must remain editable, change a value in a copy and save it. If assistive technology is part of the workflow, inspect reading order and structure rather than relying on visual appearance. A successful visual comparison does not establish accessibility conformance.

Page assembly deserves particular care because document-level information can depend on the original sequence. A bookmark can target an old page location, a printed cross-reference can become misleading, and a tagged reading order may no longer describe the merged packet. Keep a source document available and test the elements that readers actually use.

When a conversion intentionally removes interactivity, describe that choice to the recipient. An image export is useful for a slide or a visual reference, but it is a poor replacement for a form that needs further editing. The right output is defined by its purpose. Do not preserve a feature merely for its own sake, but do not discard one without recognizing what the next person needs to do.

Put the distinction to work

Open the related local tool when its supported operation matches your task. Read the limits beside the controls, make a separate output, and check it against the requirements described above. For a sequence of PDF operations, the workspace lets you carry a PDF result into the next edit.