Research Guides
Keep Recurring Research Controls Recognizable Across Pages
A reader learns what a recurring control does and carries that expectation to the next page. A research library becomes harder to use when the same action appears under a new identity on each template. Review the repeated component as a family, not merely as a collection of individually working buttons.
This worksheet addresses recognition across a set of research pages. It is not a full accessibility certification, a claim about Colquhoun.AI features or a promise that changing a label improves search rankings.
1. Group controls by their actual function
W3C's Consistent Identification guidance explains that components with the same functionality within a set of pages should be identified consistently. Recognition may depend on labels, accessible names, icons or text alternatives. Consistency does not require identical wording when context justifies a meaningful difference.
Start with one recurring component, such as the library-search control in a shared header. Include an article page, a category page and a results page. Establish what happens when each instance is used. Do not group unrelated controls solely because they share a magnifying-glass icon.
2. Follow a fictional template split
Imagine a fictional publisher whose article header labels its library-search button “Search library.” Its category template labels the same component “Discover,” and its results template shows the original wording but announces “Explore” through a separate accessible name.
A reviewer confirms that all three controls submit the same kind of query to the same library. The inconsistency is therefore not explained by a different search scope. The useful finding identifies the three templates, their displayed identities and their exposed names, rather than asking for a general redesign.
In this example, the repair is to use a recognizable shared identity for that recurring search component and remove the conflicting name override. It should not rename a separate “Search within this report” control, which searches a different body of material. Accurate distinctions matter as much as consistency.
3. Keep a component-family record
- Family: the repeated component and the page collection it belongs to.
- Instance: the exact page and template under review.
- Function: the action, scope and result actually observed.
- Visible identity: label and relevant icon.
- Exposed identity: accessible name or text alternative, as appropriate.
- Difference: intentional context, unexplained variation or a genuinely different action.
Record observations before proposing a replacement. A naming spreadsheet without a behavior check can accidentally standardize two actions that ought to remain distinct. Equally, a screenshot alone cannot show whether an invisible name override disagrees with the displayed control.
4. Test the responsive variant, not just the desktop template
Where a small-screen layout replaces words with an icon, include that version in the same review. Note the actual viewport and how the control is identified. A screenshot of the desktop header does not establish that its compact variant retains a useful accessible name.
Also check whether a shared component was copied into a second template rather than reused. Fixing one source file may leave an older copy unchanged. Keep the tested page list with the change so the reviewer can revisit every observed variant after release.
5. Close with recognition and regression evidence
After the change, repeat the original actions and confirm their scope has not changed. Verify the live labels and exposed names on each sampled page. Check any compact version that was part of the finding; if it was not exercised, mark it untested.
A precise completion statement is: “The three sampled library-search instances now use the agreed identity, and each still searches the library. The report-only search remains separately identified.” It does not imply that all interface wording or every accessibility criterion has been reviewed.
Keep the component-family record for the next template update. Its value is the link between identity and verified function, not a blanket rule that every icon or button across a website must carry the same words.