Phone format instructions do not match the required field

Capture the contradiction in one checkout state

Keep the field label, required marker, format instruction and error together with the checkout URL and observation date. Record the selected checkout country and whether the phone field has its own country selector. Do not assume a shipping-country selection is also the phone-number country. Establish which selection, if any, the actual validator uses.

Describe the submitted shape without keeping the number: country-prefix presence, digit count, separators and extension presence. Use the real report rather than inventing a sample number. Remove the buyer’s contact details from screenshots. If the error embeds the number, redact that value while retaining the surrounding message.

Read the rule that rejected the input

Have the field owner identify the configured rule or code and the stage where it rejected the value. Compare any browser-side rule with the server or extension rule receiving the field. Record whether the implementation changes the input before validation. The public label cannot establish accepted punctuation, country handling or length.

If the rule accepts the instructed format but the failure record shows rejection, preserve that contradiction for the maintainer to trace. If the rule expressly expects a different shape, the mismatch is identifiable. The business still needs to decide which supported format it intends to collect before changing the rule or instruction. Making the field optional simply to suppress a required-field error does not resolve that decision.

Keep autocomplete purpose separate from acceptance

MDN describes autocomplete values as hints about the purpose and expected value of a field. The tel token includes the country-code concept, and separate tokens describe telephone components. Compare that purpose with whether your checkout collects a whole number or several parts. Inspect the actual token rather than assuming every telephone field has the same meaning.

The browser chooses its autofill source and behavior can vary. An autofilled value does not prove that the store’s rule accepts it, while rejection does not prove that autofill supplied the wrong person’s number. Record whether the existing report involved typing or autofill, but keep the cause unconfirmed until the input shape and validation path explain it.

Align the instruction with a useful error

W3C’s Labels or Instructions guidance calls for labels or instructions when content requires input. Its Error Identification guidance says an automatically detected error must identify the affected item and describe the error in text. Compare what the buyer is told before entry with what the error explains afterwards. A required marker alone leaves a format restriction unexplained; a generic rejection leaves the buyer without the specific mismatch you have identified.

Ask the responsible maintainer to align the rule, visible instruction and textual error for the supported country context. Define completion evidence as the published wording and affected field behavior agreeing on that same path. This focused comparison does not certify the whole checkout’s accessibility.

For a Prism checkout-review consultation, summarize the field, country context and conflicting wording, with the public website and research-only products. Confirm scope, responsibilities, fees and terms before work. Leave customer records and credentials out of the public form; the inquiry is not an implementation order or processing application.

Phone-validation issue record

Use one copy for each distinct country and field path in a real report. Fill the final column with redacted observations and rule references. A documented instruction-rule conflict identifies a correction; an unseen rule remains an investigation item.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.