@codecademy/styleguide 78.5.5-alpha.ebe1b3.0 → 78.5.5

package/.storybook/components/Elements/KeyboardKey.tsx

@@ -0,0 +1,17 @@
+import styled from '@emotion/styled';
+import { css } from '@codecademy/gamut-styles';
+
+export const KeyboardKey = styled.kbd(
+  css({
+    mx: 2 as any,
+    fontFamily: 'monospace',
+    fontSize: '0.75rem' as any,
+    bg: 'background-selected',
+    border: 1,
+    borderColor: 'border-tertiary',
+    borderRadius: 'sm',
+    px: 4,
+    py: 2 as any,
+    boxShadow: 'inset 0 -1px 0 rgba(0, 0, 0, 0.2)',
+  })
+);

package/.storybook/components/index.tsx

@@ -2,6 +2,7 @@ export * from './ImageWrapper';
 export * from './TokenTable';
 export * from './Headers';
 export * from './Elements/Callout';
+export * from './Elements/KeyboardKey';
 export * from './Elements/Markdown';
 export * from './Elements/ImageGallery';
 export * from './Scales/ColorScale';

package/CHANGELOG.md

@@ -3,7 +3,7 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
-### [78.5.5-alpha.ebe1b3.0](https://github.com/Codecademy/gamut/compare/@codecademy/styleguide@78.5.4...@codecademy/styleguide@78.5.5-alpha.ebe1b3.0) (2026-01-06)
+### [78.5.5](https://github.com/Codecademy/gamut/compare/@codecademy/styleguide@78.5.4...@codecademy/styleguide@78.5.5) (2026-01-07)
 
 **Note:** Version bump only for package @codecademy/styleguide
 

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@codecademy/styleguide",
   "description": "Styleguide & Component library for codecademy.com",
-  "version": "78.5.5-alpha.ebe1b3.0",
+  "version": "78.5.5",
   "author": "Codecademy Engineering",
   "license": "MIT",
   "publishConfig": {
     "access": "public"
   },
   "repository": "git@github.com:Codecademy/gamut.git",
-  "gitHead": "873587dd5513aace45c681f478a5ceb4de320604"
+  "gitHead": "2434f4c9b000f1952a8a234749e999ac19295882"
 }

package/src/lib/Atoms/FormElements/FormGroup/FormGroup.mdx

@@ -69,12 +69,6 @@ A field can include <LinkTo id="Molecules/Tips/InfoTip"> our existing `InfoTip`<
 
 <Canvas of={FormGroupStories.HighEmphasisInfoTip} />
 
-#### Accessibility
-
-InfoTip buttons are automatically labelled by string field labels for accessibility.
-
-<Canvas of={FormGroupStories.InfoTipAutoLabelling} />
-
 ## Playground
 
 <Canvas sourceState="shown" of={FormGroupStories.Default} />

package/src/lib/Atoms/FormElements/FormGroup/FormGroup.stories.tsx

@@ -97,14 +97,3 @@ export const HighEmphasisInfoTip: Story = {
     children: <Input />,
   },
 };
-
-export const InfoTipAutoLabelling: Story = {
-  args: {
-    label: 'Email address',
-    htmlFor: 'auto-label-input',
-    infotip: {
-      info: 'We will never share your email with third parties.',
-    },
-    children: <Input htmlFor="auto-label-input" type="email" />,
-  },
-};

package/src/lib/Atoms/SkipToContent/SkipToContent.mdx

@@ -1,6 +1,6 @@
 import { Canvas, Controls, Meta } from '@storybook/blocks';
 
-import { ComponentHeader } from '~styleguide/blocks';
+import { ComponentHeader, KeyboardKey } from '~styleguide/blocks';
 
 import * as SkipToContentStories from './SkipToContent.stories';
 
@@ -21,11 +21,10 @@ export const parameters = {
 
 ## Usage
 
-Use `<SkipToContent />` to add a hidden-by-default link that becomes visible when the user <kbd>Tab</kbd>s over it (gives it focus).
+Use `<SkipToContent />` to add a hidden-by-default link that becomes visible when the user <KeyboardKey>Tab</KeyboardKey>s over it (gives it focus).
 It takes in the ID of the element it will scroll to and focus ([dev.to article explaining why](https://dev.to/robdodson/managing-focus-64l)) on click (via mouse or keyboard).
 
-This type of control is necessary for pages that have a bunch of stuff keyboard users would have to Tab through to get
-to the page's main content (like navigations).
+This type of control is necessary for pages that have a bunch of stuff keyboard users would have to <KeyboardKey>Tab</KeyboardKey> through to get to the page's main content (like navigations).
 
 For this element to work properly, there must be a `<SkipToContentTarget />` component with the id passed into this component for the `contentId` prop. The `<SkipToContentTarget />` component by default has a `tabIndex` of -1.
 Example:
@@ -43,7 +42,7 @@ Example:
 </div>
 ```
 
-To see it, keep tabbing around on this page or visit [the catalog](https://www.codecademy.com/catalog/language/javascript) and navigate via tab to see it in action.
+To see it, keep pressing <KeyboardKey>Tab</KeyboardKey> around on this page or visit [the catalog](https://www.codecademy.com/catalog/language/javascript) and navigate via <KeyboardKey>Tab</KeyboardKey> to see it in action.
 
 ## Playground
 

package/src/lib/Molecules/Flyout/Flyout.mdx

@@ -1,6 +1,6 @@
 import { Canvas, Controls, Meta } from '@storybook/blocks';
 
-import { ComponentHeader, LinkTo } from '~styleguide/blocks';
+import { ComponentHeader, KeyboardKey, LinkTo } from '~styleguide/blocks';
 
 import * as FlyoutStories from './Flyout.stories';
 
@@ -25,7 +25,7 @@ export const parameters = {
 
 ## Usage
 
-On button click, a container animates in from the left or right side of the window. Flyout can be configured to close by pressing the “X” close icon, pressing they “esc” key, and/or clicking outside of the container.
+On button click, a container animates in from the left or right side of the window. Flyout can be configured to close by pressing the "X" close icon, pressing the <KeyboardKey>Esc</KeyboardKey> key, and/or clicking outside of the container.
 
 Internally, Flyout is a combination of <LinkTo id="Molecules/Modals/Overlay">Overlay</LinkTo> and <LinkTo id="Atoms/Drawer">Drawer</LinkTo>.
 

package/src/lib/Molecules/Modals/Modal/Modal.mdx

@@ -1,6 +1,6 @@
 import { Canvas, Controls, Meta } from '@storybook/blocks';
 
-import { ComponentHeader } from '~styleguide/blocks';
+import { ComponentHeader, KeyboardKey } from '~styleguide/blocks';
 
 import * as ModalStories from './Modal.stories';
 
@@ -77,7 +77,7 @@ If the close button is hidden, you will need to create a custom way to close the
 Other than creating buttons that can close the Modal, there are other ways a Modal can be closed by the user.
 
 1. Clicking the content outside of the Modal
-2. Clicking the escape key on their keyboard
+2. Pressing the <KeyboardKey>Esc</KeyboardKey> key on their keyboard
 
 All of these methods default to `true` for accessibility reasons, and rely on setting the required `onRequestClose` prop and making sure it toggles the `isOpen` prop on the Modal.
 

package/src/lib/Molecules/Tabs/Tabs.mdx

@@ -1,6 +1,6 @@
 import { Canvas, Controls, Meta } from '@storybook/blocks';
 
-import { ComponentHeader, LinkTo } from '~styleguide/blocks';
+import { ComponentHeader, KeyboardKey, LinkTo } from '~styleguide/blocks';
 
 import * as TabStories from './Tabs.stories';
 
@@ -67,7 +67,7 @@ It is recommended to add a unique `aria-label` to the `TabNav` component, to dif
 
 ### Tabs with interactive content
 
-Normally, when you navigate to the contents of a `TabPanel` using the <kbd>tab</kbd> key or arrow keys, the entire section of the `TabPanel` will be in focus.
+Normally, when you navigate to the contents of a `TabPanel` using the <KeyboardKey>Tab</KeyboardKey> key or arrow keys, the entire section of the `TabPanel` will be in focus.
 
 However, if you have tabs with interactive content within them (such as a button or link), and tab into the `TabPanel`, the focus will be on the interactive content and not the entirety of the `TabPanel`.
 

package/src/lib/Molecules/Tips/InfoTip/InfoTip.mdx

@@ -1,6 +1,6 @@
 import { Canvas, Controls, Meta } from '@storybook/blocks';
 
-import { ComponentHeader } from '~styleguide/blocks';
+import { ComponentHeader, KeyboardKey } from '~styleguide/blocks';
 
 import * as InfoTipStories from './InfoTip.stories';
 
@@ -25,10 +25,11 @@ export const parameters = {
 
 ## Usage
 
-A tip is triggered by clicking on an information icon button and can be closed by clicking outside, pressing <kbd>Esc</kbd>, or clicking the info button again.
+A tip is triggered by clicking on an information icon button and can be closed by clicking outside, pressing <KeyboardKey>Esc</KeyboardKey>, or clicking the info button again.
 
 Use an infotip to provide additional info about a nearby element or content.
-The info button has low and high emphasis variants and the `Tip` has 4 alignment variants.
+
+Infotip consists of an icon button and the .tip-bg subcomponent. The info button has low and high emphasis variants and the `.tip` has 4 alignment variants.
 
 ## Variants
 
@@ -56,19 +57,17 @@ This `floating` variant should only be used as needed.
 
 ### InfoTips with links or buttons
 
-Links or buttons within InfoTips should be used sparingly and only when the information is critical to the user's understanding of the content. When an InfoTip opens, focus automatically moves to the tip content, allowing keyboard users to immediately interact with any links or buttons inside.
+Links or buttons within InfoTips should be used sparingly and only when the information is critical to the user's understanding of the content. If an infotip _absolutely requires_ a link or button, it needs to provide a programmatic focus by way of the `onClick` prop. The `onClick` prop accepts a function that can accept an `{isTipHidden}` argument and using that you can set programmatic focus as needed.
 
 <Canvas of={InfoTipStories.WithLinksOrButtons} />
 
-### Automatic Focus Management
+### Floating placement
 
-InfoTips automatically manage focus for optimal keyboard accessibility:
+When using `placement="floating"`, InfoTips implements focus management for easier navigation:
 
-- **Opening**: Focus automatically moves to the tip content when opened
-- **Tab (Floating)**: Navigate forward through focusable elements (links, buttons) inside the tip. When reaching the last element, wraps back to the InfoTip button
-- **Shift+Tab (Floating)**: Navigate backward naturally - from the button, exits to the previous page element
-- **Tab/Shift+Tab (Inline)**: Follows normal document flow
-- **Escape**: Closes the tip and returns focus to the InfoTip button
+- **<KeyboardKey>Tab</KeyboardKey>**: Navigate forward through focusable elements (links, buttons) inside the tip. When reaching the last element, wraps back to the InfoTip button for convenience
+- **<KeyboardKey>Shift</KeyboardKey>+<KeyboardKey>Tab</KeyboardKey>**: Navigate backward naturally through the page
+- **<KeyboardKey>Esc</KeyboardKey>**: Closes the tip and returns focus to the InfoTip button
 
 <Canvas of={InfoTipStories.KeyboardNavigation} />
 
@@ -76,28 +75,13 @@ InfoTips automatically manage focus for optimal keyboard accessibility:
 
 InfoTips have intelligent Escape key handling that works correctly both inside and outside Modals:
 
-- **InfoTips close on Escape** regardless of where keyboard focus is, and focus returns to the InfoTip button
-- **InfoTips inside Modals close first** - When an InfoTip is placed inside a Modal, pressing Escape closes the InfoTip while keeping the Modal open
-- **Layered navigation** - After closing an InfoTip inside a Modal, pressing Escape again closes the Modal
-- **Modals take priority over external InfoTips** - InfoTips detect when `dialog[open]`, `role="dialog"`, or `role="alertdialog"` elements are present and defer Escape handling to them when the InfoTip is outside the Modal
+- **InfoTips close on <KeyboardKey>Esc</KeyboardKey>** regardless of where keyboard focus is, and focus returns to the InfoTip button
+- **InfoTips inside Modals close first** - When an InfoTip is placed inside a Modal, pressing <KeyboardKey>Esc</KeyboardKey> closes the InfoTip while keeping the Modal open
+- **Layered navigation** - After closing an InfoTip inside a Modal, pressing <KeyboardKey>Esc</KeyboardKey> again closes the Modal
+- **Modals take priority over external InfoTips** - InfoTips detect when `dialog[open]`, `role="dialog"`, or `role="alertdialog"` elements are present and defer <KeyboardKey>Esc</KeyboardKey> handling to them when the InfoTip is outside the Modal
 
 <Canvas of={InfoTipStories.InfoTipInsideModal} />
 
-## Custom Accessible Labeling
-
-Provide either `ariaLabel` or `ariaLabelledby` to ensure screen reader users understand the purpose of the InfoTip button.
-
-The InfoTip button's accessible label can be customized using either prop:
-
-- **`ariaLabel`**: Directly sets the accessible label text. Useful when you want to provide a custom label without referencing another element.
-- **`ariaLabelledby`**: References the ID of another element to use as the label. Useful when you want the InfoTip button to be labeled by visible text elsewhere on the page. This is useful for when the `InfoTip` is beside text that contextualizes it.
-
-### Custom Role Description
-
-The `InfoTipButton` uses [`aria-roledescription`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-roledescription) to provide additional context to screen reader users about the button's specific purpose. This defaults to `"More information button"` but can be customized via the `ariaRoleDescription` prop for translation or other accessibility needs.
-
-<Canvas of={InfoTipStories.AriaLabel} />
-
 ## InfoTips and zIndex
 
 You can change the zIndex of your `InfoTip` with the zIndex property.

package/src/lib/Molecules/Tips/InfoTip/InfoTip.stories.tsx

@@ -4,20 +4,17 @@ import {
   FillButton,
   FlexBox,
   GridBox,
-  IconButton,
   InfoTip,
   Modal,
   Text,
 } from '@codecademy/gamut';
-import { SparkleIcon } from '@codecademy/gamut-icons';
 import type { Meta, StoryObj } from '@storybook/react';
-import { useState } from 'react';
+import { useRef, useState } from 'react';
 
 const meta: Meta<typeof InfoTip> = {
   component: InfoTip,
   args: {
     alignment: 'top-left',
-    ariaLabel: 'More information',
     info: `I am additional information about a nearby element or content.`,
   },
 };
@@ -31,10 +28,7 @@ export const Emphasis: Story = {
   },
   render: (args) => (
     <FlexBox center m={24} py={64}>
-      <Text id="emphasis-text" mr={4}>
-        Some text that needs info
-      </Text>
-      <InfoTip {...args} ariaLabelledby="emphasis-text" />
+      <Text mr={4}>Some text that needs info</Text> <InfoTip {...args} />
     </FlexBox>
   ),
 };
@@ -44,15 +38,10 @@ export const Alignments: Story = {
     <GridBox gap={24} gridTemplateColumns="1fr 1fr" ml={8} py={64}>
       {(['top-right', 'top-left', 'bottom-right', 'bottom-left'] as const).map(
         (alignment) => {
-          const labelId = `alignment-${alignment}`;
           return (
             <Box key={alignment}>
-              <Text id={labelId}>{alignment}</Text>
-              <InfoTip
-                {...args}
-                alignment={alignment}
-                ariaLabelledby={labelId}
-              />
+              <Text>{alignment}</Text>
+              <InfoTip {...args} alignment={alignment} />
             </Box>
           );
         }
@@ -67,51 +56,10 @@ export const Placement: Story = {
   },
   render: (args) => (
     <FlexBox center>
-      <Text id="placement-text" mr={4}>
+      <Text mr={4}>
         This text is in a small space and needs floating placement
       </Text>{' '}
-      <InfoTip {...args} ariaLabelledby="placement-text" />
-    </FlexBox>
-  ),
-};
-
-export const AriaLabel: Story = {
-  render: (args) => (
-    <FlexBox center column gap={24} my={48} width={1}>
-      <FlexBox alignItems="center" gap={8}>
-        <Text fontSize={16} fontWeight="bold">
-          Using ariaLabel (no visible label text):
-        </Text>
-      </FlexBox>
-      <FlexBox alignItems="center" gap={8}>
-        <IconButton
-          icon={SparkleIcon}
-          tip="This tool needs to be explained in the InfoTip"
-          tipProps={{ placement: 'floating' }}
-          onClick={() => null}
-        />
-        <InfoTip
-          {...args}
-          ariaLabel="Learn more about this tool"
-          info="This is some helpful info about the tool represented by the IconButton"
-        />
-      </FlexBox>
-
-      <FlexBox alignItems="center" gap={8}>
-        <Text fontSize={16} fontWeight="bold">
-          Using ariaLabelledby (references visible text):
-        </Text>
-      </FlexBox>
-      <FlexBox alignItems="center" gap={8}>
-        <Text id="custom-info-id">
-          I am some helpful yet concise text that needs more explanation
-        </Text>
-        <InfoTip
-          alignment="bottom-left"
-          ariaLabelledby="custom-info-id"
-          info="I am clarifying information related to the concise text."
-        />
-      </FlexBox>
+      <InfoTip {...args} />
     </FlexBox>
   ),
 };
@@ -121,16 +69,19 @@ export const WithLinksOrButtons: Story = {
     placement: 'floating',
   },
   render: function WithLinksOrButtons(args) {
+    const ref = useRef<HTMLDivElement>(null);
+
+    const onClick = ({ isTipHidden }: { isTipHidden: boolean }) => {
+      if (!isTipHidden) ref.current?.focus();
+    };
+
     return (
       <FlexBox center py={64}>
-        <Text id="links-text" mr={4}>
-          This text is in a small space and needs info
-        </Text>{' '}
+        <Text mr={4}>This text is in a small space and needs info </Text>{' '}
         <InfoTip
           {...args}
-          ariaLabelledby="links-text"
           info={
-            <Text tabIndex={-1}>
+            <Text ref={ref} tabIndex={-1}>
               Hey! Here is a{' '}
               <Anchor href="https://giphy.com/search/nichijou">
                 cool link
@@ -142,6 +93,7 @@ export const WithLinksOrButtons: Story = {
               that is also super important.
             </Text>
           }
+          onClick={onClick}
         />
       </FlexBox>
     );
@@ -150,35 +102,42 @@ export const WithLinksOrButtons: Story = {
 
 export const KeyboardNavigation: Story = {
   render: function KeyboardNavigation() {
+    const floatingRef = useRef<HTMLDivElement>(null);
+    const inlineRef = useRef<HTMLDivElement>(null);
+
     const examples = [
       {
         title: 'Floating Placement',
         placement: 'floating' as const,
+        ref: floatingRef,
         links: ['Link 1', 'Link 2', 'Link 3'],
       },
       {
         title: 'Inline Placement',
         placement: 'inline' as const,
         alignment: 'bottom-right' as const,
+        ref: inlineRef,
         links: ['Link A', 'Link B'],
       },
     ];
 
     return (
-      <FlexBox center flexDirection="column" gap={24} py={64}>
+      <FlexBox center column gap={24} py={64}>
         <GridBox gap={16} gridTemplateColumns="1fr 1fr">
-          {examples.map(({ title, placement, alignment, links }) => {
-            const labelId = `keyboard-nav-${placement}`;
+          {examples.map(({ title, placement, alignment, ref, links }) => {
+            const onClick = ({ isTipHidden }: { isTipHidden: boolean }) => {
+              if (!isTipHidden) ref.current?.focus();
+            };
+
             return (
               <FlexBox gap={8} key={placement}>
-                <Text fontSize={16} fontWeight="bold" id={labelId}>
+                <Text fontSize={16} fontWeight="bold">
                   {title}
                 </Text>
                 <InfoTip
                   alignment={alignment}
-                  ariaLabelledby={labelId}
                   info={
-                    <Text>
+                    <Text ref={ref} tabIndex={-1}>
                       {links.map((label, idx) => (
                         <>
                           {idx > 0 && ', '}
@@ -191,6 +150,7 @@ export const KeyboardNavigation: Story = {
                     </Text>
                   }
                   placement={placement}
+                  onClick={onClick}
                 />
               </FlexBox>
             );
@@ -202,10 +162,6 @@ export const KeyboardNavigation: Story = {
             Keyboard Navigation:
           </Text>
           <Box as="ul" fontSize={14} pl={16}>
-            <li>
-              <strong>Opening:</strong> Focus automatically moves to the tip
-              content when opened
-            </li>
             <li>
               <strong>Floating - Tab:</strong> Navigates forward through links,
               then wraps to button (contained)
@@ -268,10 +224,8 @@ export const InfoTipInsideModal: Story = {
             <Text>This modal contains an InfoTip below:</Text>
 
             <FlexBox alignItems="center" gap={8}>
-              <Text id="modal-infotip-text">
-                Some text that needs explanation
-              </Text>
-              <InfoTip {...args} ariaLabelledby="modal-infotip-text" />
+              <Text>Some text that needs explanation</Text>
+              <InfoTip {...args} />
             </FlexBox>
 
             <Text color="text-disabled" fontSize={14}>
@@ -299,14 +253,11 @@ export const ZIndex: Story = {
       <Box bg="paleBlue" zIndex={3}>
         I will not be behind the infotip, sad + unreadable
       </Box>
-      <InfoTip
-        ariaLabel="z-index example without override"
-        info="I am inline, cool"
-      />
+      <InfoTip info="I am inline, cool" />
       <Box bg="paleBlue" zIndex={3}>
         I will be behind the infotip, nice + great
       </Box>
-      <InfoTip {...args} ariaLabel="z-index example with override" />
+      <InfoTip {...args} />
     </FlexBox>
   ),
 };
@@ -314,10 +265,7 @@ export const ZIndex: Story = {
 export const Default: Story = {
   render: (args) => (
     <FlexBox center m={24} py={64}>
-      <Text id="default-text" mr={4}>
-        Some text that needs info
-      </Text>
-      <InfoTip {...args} ariaLabelledby="default-text" />
+      <Text mr={4}>Some text that needs info</Text> <InfoTip {...args} />
     </FlexBox>
   ),
 };

package/src/lib/Organisms/ConnectedForm/ConnectedFormGroup/ConnectedFormGroup.mdx

@@ -61,26 +61,6 @@ A `ConnectedFormGroup` can be in one of three states: `default`, `error`, or `di
 
 <Canvas of={ConnectedFormGroupStories.States} />
 
-## InfoTip
-
-A `ConnectedFormGroup` can include an `infotip` prop to provide additional context.
-
-### Automatic labelling
-
-InfoTip buttons are automatically labelled by string field labels for accessibility.
-
-<Canvas of={ConnectedFormGroupStories.InfoTipAutoLabelling} />
-
-### ReactNode labels
-
-For ReactNode labels (e.g., styled text or icons), you have three options:
-
-- `labelledByFieldLabel: true` - opt into automatic labelling by the field label
-- `ariaLabel` - provide a custom accessible name
-- `ariaLabelledby` - reference another element on the page, such as a section heading
-
-<Canvas of={ConnectedFormGroupStories.InfoTipWithReactNodeLabel} />
-
 ## Playground
 
 To see how a `ConnectedFormGroup` can be used in a `ConnectedForm`, check out the <LinkTo id="Organisms/ConnectedForm/ConnectedForm">ConnectedForm</LinkTo> page.

package/src/lib/Organisms/ConnectedForm/ConnectedFormGroup/ConnectedFormGroup.stories.tsx

@@ -2,9 +2,7 @@ import {
   ConnectedForm,
   ConnectedFormGroup,
   ConnectedFormGroupProps,
-  ConnectedInput,
   ConnectedRadioGroupInput,
-  Text,
   useConnectedForm,
 } from '@codecademy/gamut';
 import { action } from '@storybook/addon-actions';
@@ -121,85 +119,3 @@ export const States = () => {
     </ConnectedForm>
   );
 };
-
-/**
- * InfoTip buttons are automatically labelled by string field labels for accessibility.
- * Screen readers will announce "Field Label, button" when focusing the InfoTip.
- */
-export const InfoTipAutoLabelling: Story = {
-  render: () => (
-    <ConnectedForm
-      defaultValues={{ email: '' }}
-      onSubmit={(values) => action('Form Submitted')(values)}
-    >
-      <ConnectedFormGroup
-        field={{ component: ConnectedInput, type: 'email' }}
-        infotip={{
-          info: 'We will never share your email with third parties.',
-          placement: 'floating',
-        }}
-        label="Email address"
-        name="email"
-      />
-    </ConnectedForm>
-  ),
-};
-
-/**
- * For ReactNode labels, you have three options for accessible InfoTip labelling:
- * - `labelledByFieldLabel: true` - uses the field label
- * - `ariaLabel` - provides a custom accessible name
- * - `ariaLabelledby` - references another element on the page
- */
-export const InfoTipWithReactNodeLabel: Story = {
-  render: () => (
-    <ConnectedForm
-      defaultValues={{ username: '', password: '', apiKey: '' }}
-      onSubmit={(values) => action('Form Submitted')(values)}
-    >
-      <Text as="h3" id="api-section-heading" mb={8}>
-        API Configuration
-      </Text>
-      <ConnectedFormGroup
-        field={{ component: ConnectedInput }}
-        infotip={{
-          alignment: 'top-left',
-          info: 'Choose a unique username between 3-20 characters.',
-          labelledByFieldLabel: true,
-        }}
-        label={
-          <Text as="span" fontWeight="bold">
-            Username (labelledByFieldLabel)
-          </Text>
-        }
-        name="username"
-      />
-      <ConnectedFormGroup
-        field={{ component: ConnectedInput, type: 'password' }}
-        infotip={{
-          info: 'Password must be at least 8 characters with one uppercase letter and one number.',
-          ariaLabel: 'Password requirements',
-        }}
-        label={
-          <Text as="span" fontWeight="bold">
-            Password (ariaLabel)
-          </Text>
-        }
-        name="password"
-      />
-      <ConnectedFormGroup
-        field={{ component: ConnectedInput }}
-        infotip={{
-          info: 'You can find your API key in the developer settings dashboard.',
-          ariaLabelledby: 'api-section-heading',
-        }}
-        label={
-          <Text as="span" fontWeight="bold">
-            API Key (ariaLabelledby)
-          </Text>
-        }
-        name="apiKey"
-      />
-    </ConnectedForm>
-  ),
-};

package/src/lib/Organisms/GridForm/Fields.mdx

@@ -95,23 +95,3 @@ Hidden inputs can be used to include data that users can't see or modify with th
 We call it a "sweet container" so that bots do not immediately detect it as a honeypot input.
 
 <Canvas of={FieldsStories.SweetContainer} />
-
-## InfoTip
-
-Any field can include an `infotip` prop to provide additional context to users.
-
-### Automatic labelling
-
-InfoTip buttons are automatically labelled by string field labels for accessibility.
-
-<Canvas of={FieldsStories.InfoTipAutoLabelling} />
-
-### ReactNode labels
-
-For ReactNode labels, you have three options:
-
-- `labelledByFieldLabel: true` - opt into automatic labelling by the field label
-- `ariaLabel` - provide a custom accessible name
-- `ariaLabelledby` - reference another element on the page, such as a section heading
-
-<Canvas of={FieldsStories.InfoTipWithReactNodeLabel} />

package/src/lib/Organisms/GridForm/Fields.stories.tsx

@@ -1,4 +1,4 @@
-import { FormGroup, GridForm, Input, Text } from '@codecademy/gamut';
+import { FormGroup, GridForm, Input } from '@codecademy/gamut';
 import { action } from '@storybook/addon-actions';
 import type { Meta, StoryObj } from '@storybook/react';
 
@@ -328,75 +328,3 @@ export const SweetContainer: Story = {
     ],
   },
 };
-
-/**
- * InfoTip buttons are automatically labelled by string field labels for accessibility.
- * Screen readers will announce "Field Label, button" when focusing the InfoTip.
- */
-export const InfoTipAutoLabelling: Story = {
-  args: {
-    fields: [
-      {
-        label: 'Email address',
-        name: 'email',
-        size: 9,
-        type: 'email',
-        infotip: {
-          info: 'We will never share your email with third parties.',
-          placement: 'floating',
-        },
-      },
-    ],
-  },
-};
-
-/**
- * For ReactNode labels, you have three options for accessible InfoTip labelling:
- * - `labelledByFieldLabel: true` - uses the field label
- * - `ariaLabel` - provides a custom accessible name
- * - `ariaLabelledby` - references another element on the page
- */
-export const InfoTipWithReactNodeLabel: Story = {
-  render: (args) => (
-    <>
-      <Text as="h3" id="api-section-heading" mb={8}>
-        API Configuration
-      </Text>
-      <GridForm {...args} />
-    </>
-  ),
-  args: {
-    fields: [
-      {
-        label: <strong>Username (labelledByFieldLabel)</strong>,
-        name: 'username',
-        size: 9,
-        type: 'text',
-        infotip: {
-          info: 'Choose a unique username between 3-20 characters.',
-          labelledByFieldLabel: true,
-        },
-      },
-      {
-        label: <strong>Password (ariaLabel)</strong>,
-        name: 'password',
-        size: 9,
-        type: 'password',
-        infotip: {
-          info: 'Password must be at least 8 characters with one uppercase letter and one number.',
-          ariaLabel: 'Password requirements',
-        },
-      },
-      {
-        label: <strong>API Key (ariaLabelledby)</strong>,
-        name: 'apiKey',
-        size: 9,
-        type: 'text',
-        infotip: {
-          info: 'You can find your API key in the developer settings dashboard.',
-          ariaLabelledby: 'api-section-heading',
-        },
-      },
-    ],
-  },
-};

package/src/lib/Organisms/GridForm/Layout.mdx

@@ -34,7 +34,7 @@ Solo field form should always have their solo input be required. They should aut
 
 ## InfoTips
 
-A field can include our existing `InfoTip`. See the <LinkTo id="Molecules/Tips/InfoTip">Fields</LinkTo> story for specific accessibility tooling and <LinkTo id="Molecules/Tips/InfoTip">InfoTip</LinkTo> story for more information on what props are available.
+A field can include our existing `InfoTip`. See the <LinkTo id="Molecules/Tips/InfoTip">InfoTip</LinkTo> story for more information on what props are available.
 
 See the <LinkTo id="Atoms/FormInputs/Radio">Radio</LinkTo> story for an example of how to add a infotip to a radio option.