According to Trusted Tester 5F, how should errors be communicated to users?

• A. Errors are indicated only by color changes.
• B. Items that have errored are identified in text and sufficiently described to the user in text.
• C. Errors are announced via audio alerts.
• D. There is no requirement to describe errors.

Answer: (B)

Communicating errors effectively means that when something goes wrong, the system not only flags the issue but provides a clear, readable description in text that explains what happened and how to fix it. This is what Trusted Tester 5F expects: errors are identified in text and described to the user in text.

This approach matters because not all users perceive cues the same way. Relying on color changes alone can exclude people with color vision differences, and visual cues without descriptive text leaves users uncertain about the problem and how to resolve it. Audio alerts can be missed in many contexts and don’t provide a persistent record of the issue. Textual error messages placed near the affected element give everyone a precise explanation and, ideally, concrete steps to correct the issue.

For example, if a form field requires a minimum length, a helpful message would read: "Password must be at least 8 characters long." It clearly states what is wrong and how to fix it. This aligns with providing both identification of the error and a sufficient description in text.