import * as React from "react";
/**
 * The accessible-name / description / validation contract that {@link FormField} injects onto its
 * single control child (via `cloneElement`). EVERY form-capable `@godxjp/ui` component accepts
 * these props and forwards them to its **semantic focus target** — the real `<input>` / combobox /
 * trigger the user tabs to, never a presentational wrapper `<div>`.
 */
export interface FieldA11yProps {
    "aria-label"?: string;
    "aria-labelledby"?: string;
    "aria-describedby"?: string;
    "aria-errormessage"?: string;
    "aria-invalid"?: React.AriaAttributes["aria-invalid"];
    "aria-required"?: React.AriaAttributes["aria-required"];
    "data-field"?: string;
}
/**
 * Merge one or more space-separated id-reference lists (`aria-describedby`, `aria-labelledby`,
 * `aria-errormessage`) into a single deduplicated token list. Returns `undefined` when empty so the
 * attribute is omitted rather than rendered as `""`.
 */
export declare function mergeAriaIds(...values: Array<string | undefined>): string | undefined;
/**
 * Extract ONLY the defined field-a11y attributes from a props bag, ready to spread onto a
 * component's semantic focus target. Undefined entries are dropped so a forwarded contract never
 * clobbers a control's own intrinsic `aria-label` / `aria-invalid`.
 */
export declare function pickFieldA11y(props: FieldA11yProps): FieldA11yProps;
/**
 * The inverse of {@link pickFieldA11y}: everything EXCEPT the field-a11y attributes. Use it when a
 * component must route the contract somewhere other than the element the remaining props land on —
 * e.g.
 */
export declare function omitFieldA11y<T extends FieldA11yProps>(props: T): Omit<T, keyof FieldA11yProps>;
/**
 * As {@link pickFieldA11y}, but resolves the accessible **name** for a control that also has an
 * intrinsic `aria-label` (e.g. SearchInput's built-in "Search"): when the FormField supplies an
 * `aria-labelledby`, it wins and the intrinsic `aria-label` is dropped (a control must not carry
 * both — `aria-labelledby` takes precedence and the redundant `aria-label` only adds noise).
 */
export declare function resolveFieldA11y(props: FieldA11yProps, intrinsicAriaLabel?: string): FieldA11yProps;
/**
 * `cloneElement` can only wire the field-a11y contract onto FormField's single direct child. When
 * that child is a layout wrapper (a `Flex` holding a range from/to pair, a 年/月 input+select
 * combo), the naming attributes stop on the wrapper `div` and every control inside is left with no
 * accessible name at all (axe: `label` on the inputs, `button-name` on select/combobox triggers).
 */
export interface FieldNameContextValue {
    /** DOM id of FormField's visible label element (the `aria-labelledby` target). */
    labelId: string;
    /** The label's plain-text content, when it is a string (belt-and-suspenders `aria-label`). */
    label?: string;
}
/**
 * Write attributes onto the real `<input>` react-aria hides inside a Checkbox / Radio / Switch.
 *
 * react-aria renders the painted control as a `<label>` and the FOCUS TARGET as a visually hidden
 * `<input>` inside it — then strips every `data-*` off that input (`removeDataAttributes`) and
 * forwards only the aria attributes its own props model knows about. So the two contracts this
 * library puts on the semantic focus target — `data-field` (gh#337, the machine key automation
 * addresses) and the aria state a control has no react-aria prop for — have to be written by hand.
 *
 * Deliberately NOT left on the root as well: one field must resolve to exactly one node.
 */
export declare function useMirroredInputAttributes(inputRef: React.RefObject<HTMLInputElement | null>, attributes: Record<string, string | undefined>): void;
export declare const FieldNameContext: React.Context<FieldNameContextValue | null>;
/**
 * Resolve the last-resort accessible name for a control's semantic focus target (see
 * {@link FieldNameContext}). Returns `{}` — never clobbering anything — unless the control is
 * inside a FormField AND still nameless after its own props and the cloned contract are applied.
 */
export declare function useFieldNameFallback(name: Pick<FieldA11yProps, "aria-label" | "aria-labelledby">): Pick<FieldA11yProps, "aria-label" | "aria-labelledby">;
/**
 * `cloneElement` reaches FormField's single DIRECT child only. In the real screens this library
 * serves, 322 of 1,410 controls (23%) sit one level deeper — the direct child is a `Flex` holding
 * a from/to pair, a 年/月 combo, or a value + 「不明」 checkbox — so the machine key stopped on the
 * wrapper `div` and the controls inside stayed anonymous.
 */
export interface FieldIdentityContextValue {
    /** Whether the app opted into a native `name` (@see AppProviderProp.emitFieldNames). */
    emitName: boolean;
}
export declare const FieldIdentityContext: React.Context<FieldIdentityContextValue | null>;
/**
 * Resolve `data-field` / `name` for a control nested under a `FormField` (see {@link
 * FieldIdentityContext}). Returns `{}` — adding nothing — in every case but the one it exists for,
 * which is what keeps it safe to call from every control: - **outside a FormField** → `{}`.
 */
export declare function useFieldIdentity(own: {
    id?: string;
    name?: string;
    "data-field"?: string;
}): {
    "data-field"?: string;
    name?: string;
};
/**
 * The field-a11y attributes valid on a **group container** (`role="group"`), used by composite
 * controls that have no single labelable focus target — CheckboxGroup, and the two-input range
 * pickers / Transfer shuttle. Per WAI-ARIA 1.2 only `aria-labelledby` and `aria-describedby` are
 * globally allowed on `role="group"`; `aria-invalid` / `aria-errormessage` / `aria-required` are
 * widget-only and would be an invalid-ARIA violation on a group.
 */
export declare function pickGroupFieldA11y(props: FieldA11yProps): {
    "aria-labelledby"?: string;
    "aria-describedby"?: string;
    "data-field"?: string;
};