Explore the test library

Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.

Filter the library

SearchTypeCategorySubcategoryFormatUse caseIndustryWorkflowValidityEditable workspaceDestination platformBrowser test targetSort

243 results

Page 6 of 11; 24 results per page.

Show the canonical directory

KYC Identity AcroForm (SAMPLE)

Fillable fictional KYC identity PDF for testing identity-form fields and consent checkboxes.

File: PDF · Acroform · 5 fields
Use case: Form testingPDF form filling+2

KYC Identity Verification Form (HTML)

Know-your-customer style identity form with DOB, document type, and file upload: fictional SAMPLE IDs only.

File: HTML · KYC · 7 fields
Use case: Form testingForm parsing+1

Labelling: aria-describedby help text (HTML)

Every control carries both a name and a description, wired with aria-describedby to the hint that explains its rule. Use it to check that a scanner reports the description as well as the name, and does not merge the two.

File: HTML · Accessibility Testing · 5 fields
Use case: Form testingForm parsing+2

Labelling: aria-labelledby (HTML)

No label element appears anywhere. Each control points at a span through aria-labelledby, including one control whose name is assembled from two references, which is the case that catches naive accessible-name implementations.

File: HTML · Accessibility Testing · 5 fields
Use case: Form testingForm parsing+2

Labelling: Explicit label for (HTML)

The reference labelling technique: each control carries an id and is named by a separate label element pointing at it. Use it as the known-good baseline when comparing accessible-name computation across the other labelling fixtures in this set.

File: HTML · Accessibility Testing · 6 fields
Use case: Form testingForm parsing+2

Labelling: Placeholder-only anti-pattern (HTML)

A deliberate anti-pattern. No control has a label element, an aria-label or an aria-labelledby, so every accessible name has to be guessed from the placeholder or the name attribute. Ship it as a failing case for an accessibility scanner, never as a template to copy.

File: HTML · Accessibility Testing · 5 fields
Use case: Form testingForm parsing+2

Labelling: Visually hidden labels (HTML)

Every control has a real label element that is clipped out of view, while the visible wording lives in a placeholder. A visual scraper and an accessibility tree walker see different text for the same control, which is the point of the file.

File: HTML · Accessibility Testing · 5 fields
Use case: Form testingForm parsing+2

Labelling: Wrapping labels (HTML)

Implicit labelling: each control is a child of the label that names it and no for attribute is present. Parsers that resolve names only through for and id will report six unnamed controls on this file.

File: HTML · Accessibility Testing · 6 fields
Use case: Form testingForm parsing+2

Large Form: Sixty Fields (HTML)

Sixty named controls across ten titled sections. Large enough to expose pagination, truncation and quadratic behaviour in form extractors, and regular enough that a failure is easy to localise.

File: HTML · Employment · 60 fields
Use case: Form testingForm parsing+3

Lease Addendum (HTML)

Lease addendum SAMPLE for pet/policy amendment form tests.

File: HTML · Housing · 3 fields
Use case: Form testingForm parsing+1

Lease Addendum AcroForm (SAMPLE)

Fillable lease addendum PDF.

File: PDF · Housing · 2 fields
Use case: Form testingPDF form filling+2

Length-Constraint Matrix (HTML)

Textual controls carrying explicit minlength and maxlength bounds - including the exact-length and maximum-only cases, and a textarea whose counter hint and attribute must agree - for testing length validation and truncation behaviour.

File: HTML · Software Quality · 8 fields
Use case: Form testingForm parsing+3

Likert Survey Matrix (HTML)

A five-by-five Likert matrix: five statements, each a radio group over the same five points. Twenty-five radio controls that resolve to five fields is the densest grouping case in the catalog.

File: HTML · Feedback · 7 fields
Use case: Form testingForm parsing+3

Loan / Credit Application (HTML)

Income, employment, and amount fields for credit-application form testing. Entirely fictional SAMPLE data.

File: HTML · Finance · 8 fields
Use case: Form testingForm parsing+1

Login Form (HTML)

A downloadable login form: email and password with a remember-me toggle and native HTML5 validation, for testing autofill and credential-manager behaviour.

File: HTML · Account Access · 3 fields
Use case: Form testingAutofill testing+2

Malformed Document (intentionally corrupt XFDF)

Intentionally corrupt. An XFDF document with an unclosed field element and no closing root tag, so a strict parser must reject it and a lenient one must say what it recovered. Small on purpose - the damage is structural, not volume.

File: XFDF · Acroform · 5 fields
Use case: Form testingPDF form filling+2

Medical Consent Acknowledgment (HTML)

Checkbox consent + signature style medical acknowledgment for healthcare form testing. Fictional clinic.

File: HTML · Medical · 8 fields
Use case: Form testingForm parsing+1

Medical Consent AcroForm (SAMPLE)

Fillable fictional patient consent PDF for healthcare form tooling tests.

File: PDF · Acroform · 4 fields
Use case: Form testingPDF form filling+2

Medical Intake (Fillable PDF)

A fillable PDF patient-intake AcroForm: demographics, sex radios, reason-for-visit, allergies, medications, and a consent checkbox. A sample layout only. Never enter real medical data.

File: PDF · Acroform · 10 fields
Use case: Form testingPDF form filling+2

Mismatched Field Manifest (intentionally corrupt JSON)

Intentionally corrupt. A field manifest that claims to describe acro-checkbox-matrix.pdf but names two fields the PDF does not have, omits one it does, contradicts one field's type and states a count that does not match its own array.

File: JSON · Form Data
Use case: Form parsingForm testing+1

Mismatched Option Values (intentionally corrupt HTML)

Intentionally corrupt. A select has two options with the same value under different labels, a radio group repeats a value, and one option's value contradicts its wording outright. A form that reads labels and a form that reads values disagree about what was chosen.

File: HTML · Software Quality · 5 fields
Use case: Form testingForm parsing+3

Move-in Checklist (HTML)

Residential move-in inspection checklist SAMPLE.

File: HTML · Housing · 3 fields
Use case: Form testingForm parsing+1

Multipart Submission Body (TXT)

A complete multipart request dump for the multipart upload form: two file parts with placeholder payloads, a filename containing a space and parentheses, a repeated field name and the empty honeypot.

File: TXT · Form Data · UTF-8
Use case: Form parsingForm testing+1· Conversion set

Native Validation Enforced (HTML)

A counterpart to the rest of the catalog's forms: it omits novalidate, so the browser's own constraint UI blocks submission and shows the bubble. Use it to tell native enforcement apart from script-driven validation in the same harness.

File: HTML · Software Quality · 5 fields
Use case: Form testingForm parsing+3