Fillable PDFs: Test the Route Through the Form

A client opens your beautifully arranged PDF questionnaire, clicks the first box and begins typing. When they press Tab, the cursor jumps to the footer. Another press takes them to a question halfway down the page.

The layout looks organised. The route through it is not. For creators selling workbooks, planning sheets or client forms, that route is part of the product.

Before approving a fillable PDF, complete it using the keyboard in the file a buyer will receive. Treat the order of movement as an editorial decision: it should help the person answer the questions in a meaningful sequence.

The order you see and the order you follow

The W3C’s PDF3 technique explains that tab order governs navigation through interactive elements, including fields and links. It should reflect the document’s logical order. The guidance distinguishes this from the reading structure in a tagged PDF and notes that complex layouts may need correction after conversion.

That gives a creator two related questions. Is the document’s content organised meaningfully? And can a person move through its interactive parts in a sequence that makes sense? A neat arrangement of rectangles does not answer either question by itself.

The related PDF23 technique focuses on keyboard operation of form controls. Its test asks whether users can reach each control and activate it or change its value using the keyboard. It also warns that form fields may not survive conversion fully. These techniques offer examples of accessibility practice; this short check alone does not establish complete accessibility.

Write the route before inspecting the settings

Consider a hypothetical freelance designer creating a project-intake form. The form asks for a project name, intended audience, main objective, required deliverables and a contact address.

Before opening the form editor, write that sequence in plain language. Check whether the questions actually belong in that order. A person may need to state the objective before choosing deliverables. If so, the interaction should support that relationship.

Now compare the expected route with the exported PDF. Begin at the start and move through the fields. Record the actual sequence, including links and buttons. Look for skipped questions, sudden jumps and repeated stops that do not help the task.

A useful defect report names the transition: ‘After the audience field, Tab moves to the website link instead of the objective field.’ That is more actionable than ‘navigation feels awkward’.

Test answering, not just reaching

Landing in a field is only the beginning. In the hypothetical form, try entering a realistic project title, selecting the intended options and changing an answer. Check whether you can complete each action without reaching for the mouse.

Use fictional information throughout the test. Include answers that resemble the lengths and choices a buyer might need, rather than typing one letter into every box and calling the form finished.

Try correcting an earlier answer too. Ask whether the current location is apparent and whether returning to the previous question is manageable in the tested viewer. Record confusing behaviour so the person repairing the file can reproduce it.

If a control behaves differently from what you expected, investigate the control and the viewing application before deciding which part needs changing. Keep the test environment with the defect report.

Give multi-column pages a deliberate sequence

Suppose the designer rearranges the questions into two columns to make the page feel lighter. Should the user finish the left column before moving to the right, or complete each row across the page?

Choose according to meaning. If a short explanation belongs with the response beside it, preserve that pairing. If each column forms a separate section, make that structure clear. Do not assume a visual convention will settle the decision for every form.

Ask the implementer to show how the chosen route is represented in the exported file. Then repeat the keyboard test. A setting that appears correct in the editor is useful evidence, but the buyer’s experience remains the acceptance check.

For a particularly confusing layout, consider simplifying the page instead of building an elaborate navigation arrangement around it. The design should make the sequence easier to understand.

Keep the final export in the review

Review the delivered PDF after any export or conversion step. If AI helped generate the source document or place fields, apply the same test. A claim that the form is interactive should be demonstrated in the final file.

Keep a clean master and a separate completed test copy. Confirm that the download you intend to sell is the clean version, with the expected field behaviour. Do not leave fictional test answers in the buyer’s file.

Also test the completion journey promised in your instructions. If users are meant to save a filled copy, close and reopen a test copy to check the result. MaryChuks.com’s guide to digital workbook reading and saving addresses that separate handover concern.

Record the viewers and devices used for your checks. Describe supported use accurately in the product instructions rather than assuming that one successful test proves every possible environment works.

Repair the source and verify the repair

Where possible, make structural changes in the editable source so the next export does not silently undo them. If the final PDF needs a separate repair, document that step as part of producing each release.

After a correction, repeat the affected route and continue through the rest of the form. Moving one field in the sequence should not leave a later section untested. Keep a short release checklist with the approved question order.

Ask a person who did not build the form to try a fictional submission. Give them the same instructions a buyer receives, then observe where explanation is needed. Their experience can reveal an unclear question as well as a navigation problem.

The goal is a form that makes its next step understandable. Good visual design invites a person to begin; a coherent keyboard route helps them continue. Approve both before treating the file as ready for delivery.

Sources

W3C WAI PDF3: Ensuring correct tab and reading order; W3C WAI PDF23: Providing interactive form controls. Live guidance checked 7 November 2026. The designer scenario and review routine are illustrative editorial applications.