pattern-library 1 linked patterns checked
U.S. Web Design System: Input prefix/suffix
Documents input prefixes and suffixes for commonly understood symbols, units, abbreviations, and icons; requires descriptive labels because affixes are hidden from screen readers; warns against open-ended fields and unclear abbreviations; and documents error and success group states.
Read with a purpose
What this source can teach
Use this source to compare a documented solution with the task and states in your own product.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Input prefix/suffix | Choose input prefix/suffix when a common fixed symbol, unit, abbreviation, domain, or icon clarifies what the text input accepts. | The affix is visible near the input but not editable as part of the field value. | USWDS supports affixes for common symbols, units, abbreviations, and icons, with descriptive labels because affixes are hidden from screen readers. |
Comparisons supported by this source
- Input prefix/suffix vs input mask vs text input vs inline validation
USWDS defines when affixes clarify common units or symbols, when open-ended fields need another approach, and why labels must describe hidden affix meaning.
Evidence Role
This source is treated as pattern-library evidence. Its value comes from the specific claims and setting described above.
Publisher: U.S. Web Design System. Last checked: .