Resource test record.

Visit pack builder: print output

All seven page templates were selected, the pack was previewed, then printed to PDF with the browser in each paper and text size.

Keyboard use: the Preview button was reached with the Tab key alone and Enter built the pack.

Downloadable files

Checked 2026-10-24, after that day’s update (kit version 2.1, quick-start files version 1.1), with scripts (PyMuPDF and pypdf on Python 3.14, Windows 11) that open each published file and read it back, and by looking at every page rendered as an image, in color and in grayscale. Anyone can repeat the basic checks: open the PDF in a reader and look at the page count, the page size in the document properties, the bookmarks panel and the form fields.

Nail and Foot-Care Visit Kit, version 2.1

Checked 2026-10-24, after that day’s update (fields you can type into on screen, larger page footer; the pages and page numbers did not change), with the same scripts and a look at every page.

Form fields: every field was filled by a script and the pages were rendered again to check that typed text sits on the printed lines and inside the table cells. Each field has a name a screen reader can announce (for example “My question (line 1 of 2)”). The fields are not part of the PDF’s tag structure.

Page counts for every free file are also checked at each site build against the PDFs themselves, so a page that describes a file with the wrong number of pages cannot be published: the kit is 24 pages, the seven-day quick-start planner is 5, and the Appointment Question Card and the Care Instruction Capture Template are 2 each.

Question prompt bank: reading and keyboard use

Checked 2026-10-23 on the question prompt bank with Chromium 153.0.8010.12 (automated), on a local copy of the site.

• Without JavaScript: all 42 prompts show, in five groups of 9, 10, 7, 9 and 7. They are plain list items in the page itself.
• With JavaScript: the list starts with 10 common prompts. The “Show all 42 prompts” button was reached with the Tab key alone (15 presses from the top of the page); Enter showed all 42 and the button reported itself as expanded.
• Narrow screens: the home page, the kit page, the question card page and one article showed no sideways scrolling at 320, 375, 390 and 768 pixels wide, and the menu button opened the menu at each width.

Not tested yet

• Editing the DOCX files in LibreOffice or Google Docs. Microsoft Word opened all four without errors; how each program lays out the pages has not been compared.
• Typing into the PDF fields by hand in a PDF reader app or a browser. The fields were filled and read back by script only.
• Printing on physical printers, double-sided output and paper show-through.
• Screen-reader reading order of the PDFs (all the PDFs are tagged, but no screen reader has been run on them).
• Touch-screen phones and tablets: the narrow-screen checks above were run in a desktop browser set to phone widths.
• Use by people outside our team. When we run real usability sessions, we will say how many people took part and what changed.

Found a problem with a file or the builder? Tell us through the contact page. Please do not include health details.