import { FC } from 'react';
interface Props {
    isSpeaking: boolean;
    /** No installed voice for the app language — stays visible, but inert. */
    disabled?: boolean;
    /** Why it is disabled; surfaced as the tooltip so it is never a dead control. */
    disabledReason?: string | null;
    /**
     * Id of the element carrying that reason as VISIBLE text.
     *
     * `title` alone is not an explanation: on a disabled button it cannot be
     * reached by touch and cannot take keyboard focus, so assistive tech and
     * phone users — the ones this feature is for — never see it.
     */
    describedById?: string | undefined;
    onClick: () => void;
}
/**
 * "Read aloud" control on an assistant message (BOFF-6290).
 *
 * A real `<button>`, sitting in the same action row as Copy and Retry, whose
 * accessible name is the ACTION it will perform next — "Read aloud" when idle,
 * "Stop reading" while speaking — with `aria-pressed` carrying the state. It
 * never moves focus and never renders a live region: a screen-reader user is
 * already having the message read to them by their own software, and a second
 * announcement would talk over it.
 *
 * The parent hides this entirely when the platform has no speech output, so an
 * unsupported browser gets no dead affordance (same rule as the composer mic).
 */
export declare const AssistantSpeakButton: FC<Props>;
export {};
//# sourceMappingURL=AssistantSpeakButton.d.ts.map