Skip to main content

Interface: InputA11yProps

Defined in: types.ts:264

The accessibility contract every element component must forward onto its focusable control (docs/06 §13). Spread it: <input {...field.inputProps} />.

Properties​

aria-describedby?​

optional aria-describedby?: string;

Defined in: types.ts:275

aria-invalid?​

optional aria-invalid?: boolean;

Defined in: types.ts:276

aria-labelledby?​

optional aria-labelledby?: string;

Defined in: types.ts:274

The field's own label. FieldWrapper renders a real <label for>, which is enough for an <input> — but a custom element that renders its control inside a <div role="combobox"> or a canvas has no label association at all without this, and docs/06 §4 names it as part of the contract for exactly that reason: the contract is what a REPLACEMENT component must honour.

aria-readonly?​

optional aria-readonly?: boolean;

Defined in: types.ts:278

aria-required?​

optional aria-required?: boolean;

Defined in: types.ts:277

autoComplete?​

optional autoComplete?: string;

Defined in: types.ts:293

Autofill hint. Only ever set from an explicit bind.autoComplete: guessing it would be worse than omitting it, because an enumerator's browser autofilling THEIR name into a respondent's field is a data-protection incident, not a convenience (docs/16).

dir?​

optional dir?: "ltr" | "rtl" | "auto";

Defined in: types.ts:279

id​

id: string;

Defined in: types.ts:265

inputMode?​

optional inputMode?: "text" | "numeric" | "decimal" | "tel" | "email" | "url";

Defined in: types.ts:286

Which on-screen keyboard to raise. Derived from the element type and props.format, so a phone number field opens a phone keypad — which on a device held one-handed in the sun is the difference between a tap and a hunt.

name​

name: string;

Defined in: types.ts:266

Methods​

onBlur()​

onBlur(): void;

Defined in: types.ts:294

Returns​

void