Colquhoun.AI
← All guides

Research Guides

Identify Whose Information a Research Form Requests

· Colquhoun.shop editorial

A form asks for an email address. Is it the researcher's own contact address, a competitor's public contact or the identity used to sign in? Those fields can look similar while serving different purposes. An input review should record what the field means before copying markup from another form.

This worksheet concerns purpose identification in website forms. It is not a claim that Colquhoun.AI provides an automated accessibility audit or that a single attribute makes a form fully accessible.

1. Distinguish data type from purpose

The W3C explanation of Identify Input Purpose scopes this criterion to fields collecting information about the user, where the purpose is listed and the technology supports identifying it. An email input type describes a broad data category, not whose address is requested. HTML autocomplete tokens can express more specific meanings. Browser autofill appearing to work is not, by itself, proof that the purpose is programmatically identified.

Start the review with a plain-language question: whose information belongs here, and why is the form requesting it? If the product owner cannot answer, changing an attribute is premature.

2. Build a field-purpose inventory

Record the page, visible field label, field identifier and intended meaning. Include whether the information concerns the person completing the form or someone else. Keep the review focused on field definitions rather than collecting real submissions.

For each applicable field, compare the rendered markup with the agreed meaning and the relevant documented token. Do not invent a token from the wording of a label. Treat a missing purpose and an incorrect purpose as separate findings: they may need different repairs.

3. Examine a fictional copied component

Imagine a fictional research portal with two fields labeled Email. One belongs to the researcher's contact details. The other stores a competitor contact discovered during authorized research. A shared component has copied the same personal-information settings into both places.

The reviewer first asks the designer to make the two labels unambiguous. Next, they inspect each field independently instead of assuming that identical visual styling means identical meaning. Their issue record names the component, the affected page and the intended use of each field.

The fix should be reviewed against that record. A global replacement across every email-shaped field would be risky because other instances might serve account access or another workflow.

4. Test without exposing real information

Use a clean test profile and clearly fictional data where interaction testing is necessary. Avoid screenshots containing a real person's saved contact suggestions. A markup-only inspection may establish a narrow finding, but it cannot establish the complete experience across browsers and assistive technologies.

Record exactly what was observed. For example: the purpose token was inspected in the rendered control, or a particular browser suggested a saved test value. Do not compress those different observations into an unsupported claim that all autofill behavior works.

5. Copy this purpose-review card

Keep broader problems in separate issues. Confusing instructions, missing labels and unpredictable submission behavior should not disappear because a purpose token has been corrected.

6. Report the boundary of the result

A completed review connects each inspected field to a defensible meaning and records how that meaning is exposed. It does not certify the whole form, authorize collection of additional personal information or prove that every browser will fill it automatically. Narrow, reproducible conclusions are more useful than a green check mark with no stated scope.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.