diff --git a/docs/data/base/getting-started/accessibility/accessibility.md b/docs/data/base/getting-started/accessibility/accessibility.md
new file mode 100644
index 00000000000000..fa28b288385a25
--- /dev/null
+++ b/docs/data/base/getting-started/accessibility/accessibility.md
@@ -0,0 +1,57 @@
+# Accessibility
+
+<p class="description">
+Accessibility is our top priority for Base UI components.
+However, the library cannot make your application fully accessible.
+This page highlights the most common actions you, as an application developer, need to take to ensure your product is accessible.
+</p>
+
+Base UI components implement the .
+
+## Keyboard navigation
+
+As the Base UI components follow the [WAI-ARIA 1.2 standard](https://www.w3.org/TR/wai-aria-1.2/), they are accessible with a keyboard.
+This is important for users who have trouble using a pointing device, but also comes in handy for users who find navigating with a keyboard faster and expect web components to behave the same way as native operating system controls.
+
+Specifically, interactive components can be focused using the <kbd>Tab</kbd> key.
+List-like components (such as Select, Menu, etc.) can be browsed and activated using arrow keys, <kbd>Home</kbd>, <kbd>End</kbd>, <kbd>Enter</kbd>/<kbd>Return</kbd> and <kbd>Escape</kbd>.
+The Select and Menu also let users navigate to options that begin with a provided string by pressing alphanumeric keys.
+
+## Focus ring
+
+While Base UI components handle keyboard navigation, it's the developers' responsibility to indicate when a component is focused and can receive keyboard input.
+This is usually done by styling the [`:focus`](https://developer.mozilla.org/en-US/docs/Web/CSS/:focus) or [`:focus-visible`](https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible) pseudoclasses.
+The [WCAG guidelines](https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance-minimum) specify the required appearance of focused elements.
+
+## Color contrast
+
+As Base UI controls are unstyled, it's up to you to ensure appropriate contrast between text and background.
+You can use online tools such as https://cliambrown.com/contrast/ to measure contrast between colors (note that it uses the [APCA algorithm](https://ruitina.com/apca-accessible-colour-contrast/) that's being considered for the WCAG 3 guidelines).
+
+## Accessible labels
+
+It is also your responsibility to ensure that components have accessible names.
+
+For form controls (such as the [Input](/base-ui/react-input/), [Number Input](/base-ui/react-number-input/), [Select](/base-ui/react-select/), etc.), this requires adding an associated `<label>` element or placing an `aria-label` attribute on the component itself:
+
+```jsx
+<label>
+  First name <Input />
+</label>
+```
+
+or
+
+```jsx
+<label for="first-name">First name</label>
+<Input id="first-name" />
+```
+
+or
+
+```jsx
+<Input aria-label="First name" />
+```
+
+For buttons, their inner text becomes the accessible label.
+You only need to place an `aria-label` attribute if the button contains no text (like an icon button).
diff --git a/docs/data/base/pages.ts b/docs/data/base/pages.ts
index 885f564a1c701e..2f041567682d7e 100644
--- a/docs/data/base/pages.ts
+++ b/docs/data/base/pages.ts
@@ -10,6 +10,7 @@ const pages: readonly MuiPage[] = [
       { pathname: '/base-ui/getting-started/quickstart', title: 'Quickstart' },
       { pathname: '/base-ui/getting-started/usage', title: 'Usage' },
       { pathname: '/base-ui/getting-started/customization', title: 'Customization' },
+      { pathname: '/base-ui/getting-started/accessibility', title: 'Accessibility' },
     ],
   },
   {
diff --git a/docs/pages/base-ui/getting-started/accessibility.js b/docs/pages/base-ui/getting-started/accessibility.js
new file mode 100644
index 00000000000000..0a2db71b65440b
--- /dev/null
+++ b/docs/pages/base-ui/getting-started/accessibility.js
@@ -0,0 +1,12 @@
+import * as React from 'react';
+import MarkdownDocs from 'docs/src/modules/components/MarkdownDocsV2';
+import AppFrame from 'docs/src/modules/components/AppFrame';
+import * as pageProps from 'docs/data/base/getting-started/accessibility/accessibility.md?@mui/markdown';
+
+export default function Page() {
+  return <MarkdownDocs {...pageProps} />;
+}
+
+Page.getLayout = (page) => {
+  return <AppFrame>{page}</AppFrame>;
+};
diff --git a/docs/src/components/productBaseUI/BaseUISummary.tsx b/docs/src/components/productBaseUI/BaseUISummary.tsx
index 1388eab935f0f9..d5e8b610fcf43e 100644
--- a/docs/src/components/productBaseUI/BaseUISummary.tsx
+++ b/docs/src/components/productBaseUI/BaseUISummary.tsx
@@ -29,7 +29,7 @@ const content = [
     title: 'Accessibility',
     description:
       'We take accessibility seriously. The Base UI docs are loaded with guidelines and best practices.',
-    link: '/base-ui/getting-started/quickstart/#components-and-hooks',
+    link: '/base-ui/getting-started/accessibility/',
   },
 ];