TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:suggestions for documenting unlabeled fields From:Michael Simoni <msimoni -at- OMWARE -dot- COM> Date:Thu, 26 Aug 1999 16:01:13 -0700
Our development team, in particular the chief programmer/company president,
occasionally place unlabeled controls on forms. Not very often, but enough
to annoy me. Granted, each window has a status bar that provides a limited
description of the data required for entry in each field.
When I ask them label a control, I get a standard reply such as "the clients
can read the status bar" or "after the clients do this once or twice,
they'll know what is required". I've tried a number of ways to convince them
to label the controls. But, alas, this is an argument I cannot win.
How do I refer to these unlabeled controls in procedures and reference
materials? Any ideas?
