import { ReactNode } from 'react';
export interface TooltipProps {
    /** Tooltip content - can be string or ReactNode */
    content: ReactNode;
    /** Children to wrap with tooltip (trigger element) */
    children: ReactNode;
    /** Additional class name for the wrapper */
    className?: string;
    /** Additional class name for the tooltip content */
    contentClassName?: string;
    /** Custom ID for the tooltip (for aria-describedby association) */
    tooltipId?: string;
    /** Tab index for the wrapper. Use -1 when wrapping already-focusable elements like buttons. Defaults to 0. */
    tabIndex?: number;
    /**
     * Announce the trigger as a button carrying `aria-expanded`, and let Enter
     * and Space toggle the content.
     *
     * Off by default: a trigger whose content only supplements what is already
     * on screen is not a control and should not claim to be one. Turn it on
     * where the content is something a reader summons deliberately. A glossary
     * term is the case this exists for, and two products had independently built
     * the same trigger contract around one.
     *
     * Do not combine with `tabIndex={-1}`, which is for wrapping an element that
     * is already focusable and already owns its role.
     */
    toggleable?: boolean;
}
export declare function Tooltip({ content, children, className, contentClassName, tooltipId, tabIndex, toggleable, }: TooltipProps): import("react").JSX.Element;