diff --git a/.storybook/preview.tsx b/.storybook/preview.tsx
index 54ccf8c0..18242a7d 100644
--- a/.storybook/preview.tsx
+++ b/.storybook/preview.tsx
@@ -76,6 +76,7 @@ const preview: Preview = {
"Helpers",
"Theme",
"Theme/Logos",
+ "Accessibility",
"MUI",
"Components",
],
diff --git a/src/storybook/accessibility/00-overview.mdx b/src/storybook/accessibility/00-overview.mdx
new file mode 100644
index 00000000..b34f93bf
--- /dev/null
+++ b/src/storybook/accessibility/00-overview.mdx
@@ -0,0 +1,189 @@
+import { Meta } from "@storybook/addon-docs/blocks";
+
+
+
+
+
+# Accessibility (a11y)
+
+Our goal is to make interfaces that are understandable, predictable, and
+usable across a wide range of abilities, environments, and levels of fatigue.
+
+## Standards and approach
+
+We follow WCAG 2.2 as the compliance baseline, and use APCA (Advanced
+Perceptual Contrast Algorithm) to keep text readable and comfortable in
+real-world conditions. See [Colour contrast and
+vision](?path=/docs/accessibility-colour-contrast-and-vision--docs) for
+details.
+
+## Core principles
+
+
+ -
+ Clarity over cleverness: interfaces should explain
+ themselves.
+
+ -
+ Predictable behaviour: similar things behave in similar
+ ways.
+
+ -
+ Multiple ways to perceive information: never rely on one
+ signal alone.
+
+ -
+ Low cognitive effort by default: minimise mental overhead.
+
+
+
+## ✅ Do
+
+### Interactive elements
+
+
+ - Ensure every interactive control has an accessible name.
+ -
+ Provide this via a visible label,
aria-label, or{" "}
+ aria-labelledby.
+
+ - Make keyboard focus clearly visible at all times.
+ -
+ Use a consistent focus indicator (outline) rather than transient effects
+ such as ripples.
+
+ -
+ Ensure disabled states are clearly distinguishable from enabled and default.
+
+
+
+### Keyboard navigation
+
+
+ -
+ All interactive elements must be reachable and usable using a keyboard
+ alone.
+
+ - Follow a logical tab order that matches the visual and reading order.
+ -
+ Do not trap focus. Users must be able to move in and out of components using
+ standard keyboard interactions.
+
+ -
+ Ensure focus is always visible and moves predictably between elements.
+
+ -
+ Support standard keyboard interactions (e.g. Enter or Space to activate
+ controls).
+
+
+
+For overlays such as menus and dialogs, manage focus intentionally:
+
+
+ - Move focus into the component when it opens.
+ -
+ Keep focus within modal dialogs while they are open. Non-modal menus and
+ popovers should close on Escape or when focus leaves.
+
+ - Return focus to the triggering element when it closes.
+
+
+### Icons and icon-only actions
+
+
+ -
+ Icon-only controls must include an accessible name that describes the action
+ (e.g. “Delete sample”), using
aria-label or{" "}
+ aria-labelledby.
+
+ -
+ Tooltips support discoverability, but do not replace accessible names.
+
+ -
+ Decorative icons should be hidden from assistive technologies using{" "}
+
aria-hidden="true".
+
+ - Do not rely on an icon alone to communicate critical meaning.
+ -
+ If an icon represents a toggle or state, expose the state using appropriate
+ ARIA attributes (e.g.
aria-pressed).
+
+
+
+For interactive icons, ensure both an accessible name and a visible affordance
+such as a tooltip or label.
+
+In MUI, use
aria-label on
IconButton. Tooltips (e.g.
<Tooltip />) should be used in addition to, not instead of,
+accessible labelling.
+
+### Forms and inputs
+
+
+ - Always associate inputs with labels (even if visually hidden).
+ -
+ Do not show validation errors while a user is actively typing. Validate on
+ blur or submission.
+
+ - Make error messages clear, specific, and actionable.
+ - Associate errors programmatically with the relevant field.
+
+
+### Content and layout
+
+
+ - Do not rely on colour alone to convey meaning.
+ - Do not rely on icons alone to convey critical meaning.
+ - Use a logical, predictable reading order.
+
+
+## ❌ Don’t
+
+
+ - Don’t use placeholder text as a replacement for labels.
+ - Don’t hide important information in faint or decorative text.
+ - Don’t introduce unexpected interaction patterns.
+ - Don’t create dense, unbroken blocks of content.
+
+
+## Storybook guidance
+
+
+ -
+ Simple component stories may be visually minimal, but should still expose an
+ accessible name, or be documented as intentionally incomplete.
+
+
+
+## Quick sense check
+
+
+ - Can this be used with a keyboard only?
+ - Is its purpose clear without colour or icons?
+ - Would it still make sense when someone is tired or distracted?
+
+
+## Learn more:
+
+
+
+
diff --git a/src/storybook/accessibility/01-colour-contrast.mdx b/src/storybook/accessibility/01-colour-contrast.mdx
new file mode 100644
index 00000000..bf6d929f
--- /dev/null
+++ b/src/storybook/accessibility/01-colour-contrast.mdx
@@ -0,0 +1,108 @@
+import { Meta } from "@storybook/addon-docs/blocks";
+
+
+
+
+
+# Colour contrast and vision
+
+Poor contrast slows decisions and raises error rates, especially in dense,
+data-heavy interfaces. Colour choices also need to work for people with colour
+vision deficiency (CVD).
+
+## How we judge contrast
+
+
+ -
+ APCA is the primary tool for tuning colours. It accounts
+ for font size, weight, and light or dark polarity.
+
+ -
+ WCAG 2.2 is the compliance floor. If it fails, the colour
+ must change.
+
+ -
+ If WCAG 2.2 passes but APCA still shows poor readability, improve the
+ colour rather than treating compliance as enough.
+
+
+
+## Do
+
+
+ -
+ Use the theme tokens and roles (
--ds-*) rather than picking
+ colours by hand.
+
+ - Test text across sizes, weights, and both light and dark modes.
+ -
+ Pair colour with text, an icon, or a label. Icons should differ in shape,
+ not just colour.
+
+ -
+ Keep disabled states distinguishable without making them unreadable. WCAG
+ 2.2 exempts disabled controls from contrast minimums, but we still aim for
+ legible text.
+
+ - Use subtle text only for non-essential information.
+
+
+## Watch out for
+
+
+ -
+ Status colours (
--ds-success, --ds-warning,{" "}
+ --ds-danger). Saturated colours can pass WCAG and still vibrate
+ or feel muddy, and they fall in the red-green range that the most common
+ types of CVD compress together.
+
+ -
+ Status colours placed side by side, such as a legend or results table.
+ Check them in a CVD simulator, not just by eye.
+
+ - Reducing contrast for visual subtlety where meaning is still needed.
+ - Assuming light and dark mode need the same values.
+
+
+Learn more:
+
+
+
+
diff --git a/src/storybook/accessibility/02-cognitive-a11y.mdx b/src/storybook/accessibility/02-cognitive-a11y.mdx
new file mode 100644
index 00000000..f10cba6d
--- /dev/null
+++ b/src/storybook/accessibility/02-cognitive-a11y.mdx
@@ -0,0 +1,72 @@
+import { Meta } from "@storybook/addon-docs/blocks";
+
+
+
+
+
+# Cognitive accessibility and usability
+
+People differ in how they process information, maintain focus, and recover from
+errors. In scientific software, users may work for long periods or run live
+experiments where mistakes are costly. The goal is not to simplify the science,
+but to remove cognitive load the interface adds.
+
+## Design objectives
+
+
+ -
+ Be understandable: use familiar patterns and terminology,
+ and make state visible at a glance.
+
+ -
+ Reduce memory burden: keep important information visible
+ and favour recognition over recall.
+
+ -
+ Support focus: avoid competing emphasis and keep
+ navigation consistent.
+
+ -
+ Prevent and recover from errors: show consequences before
+ actions, and make recovery obvious and forgiving.
+
+ -
+ Design for long sessions: assume users are tired,
+ interrupted, or multitasking.
+
+
+
+## Quick sense check
+
+
+ - Is it understandable without prior knowledge?
+ - Does it rely on memory or hidden behaviour?
+ - Is important state clearly visible?
+ - Is error recovery clear and forgiving?
+ - Would it still be clear at the end of a long experiment session?
+
+
+Learn more:
+
+
+
+