← Back to Catalog

Don't split phone, SSN, or card

dont-split-phone-ssn-card

Do not split phone, SSN, or credit-card numbers into separate fields. One input; segmented fields force meaningless labels for AT. Distinct from GOV.UK three-field dates.

Description

USWDS keeps phone, SSN, and credit-card numbers in one input each so assistive technology gets a meaningful label and users paste or autofill without hopping boxes. Segmented fields force meaningless part labels and break common entry habits. This is distinct from GOV.UK three-field memorable dates. Splitting those numbers across multiple boxes fails; use a single field per number type.

When to use

Collecting phone, Social Security, or payment-card numbers in a form.

Not when

GOV.UK-style three-field memorable dates, which are a different pattern.

Agent hint

Keep phone, SSN, and card numbers in one field each; do not segment them.

Pass

Phone, SSN, and card number are each one field.

Fail

Those numbers are split across multiple fields.

Citations

Open UX · cited UX rules agents audit against

Privacy · Sources ·