Make form labels clear and usable

A placeholder disappears as someone types. It should not be the only explanation of what belongs in a field.

1. Provide a visible label

Use a clear label above or beside each control and connect it correctly. Explain required information before the user encounters an error.

2. Explain errors specifically

Tell the person which field needs attention and what to change. Avoid relying on colour alone to identify the problem.

3. Test with a keyboard

Move through the fields, buttons and error messages without a mouse. The focus indicator should remain visible and the order should make sense.

4. Check submission and delivery

With permission, send a labelled test and confirm the saved entry and email route. Accessible controls and reliable delivery are separate requirements.

When to ask for help

Stop if the change affects a critical workflow, requires access you do not have or produces a result you cannot explain. Keep the original evidence and a restorable backup. A short, well-defined repair request is easier to review than a series of speculative changes.

Related repair: request a scope review. Choose your platform on the request form; availability and price are confirmed before payment.