# Accessibility

> How Patine UI support VoiceOver, TalkBack and the keyboard — adjustable wheels, labelled calendar days, arrow keys on the web, selection and disabled states, and what you should add.

Accessibility is built in. Here's what each component exposes to VoiceOver (iOS), TalkBack (Android), screen readers on the web and the keyboard.

## Wheels

`WheelPicker` (and each column of `MultiWheelPicker`, `TimePicker` and `DateWheelPicker`) is a single element with:

| Property | Value |
| --- | --- |
| `accessibilityRole` | `adjustable` |
| `accessibilityValue` | the current label, e.g. `"45"` |
| `accessibilityActions` | `increment`, `decrement`: swipe up / down moves one row |
| `accessibilityLabel` | the `accessibilityLabel` prop |

Name your wheels, especially multi-column ones:

```tsx
<WheelPicker accessibilityLabel="Shirt size" items={sizes} value={size} onValueChange={setSize} />

<MultiWheelPicker
  columns={[
    { key: 'h', accessibilityLabel: 'Hours', items: hours, value: h, onValueChange: setH },
    { key: 'm', accessibilityLabel: 'Minutes', items: minutes, value: m, onValueChange: setM },
  ]}
/>
```

## Calendar

- Each day is a `button` labelled with the **full date** in the calendar's locale ("Wednesday, 14 October 2026"), with `selected` and `disabled` states.
- The arrows are buttons labelled **Previous** and **Next**, with a `disabled` state at min / max.
- The month title is a button (quick jump) or a `header`.
- Quick-jump grid cells expose `selected` / `disabled`.

## Select

- The field is a `button` labelled with `label` (or the placeholder). Its hint lists the selected options, and it has an `expanded` state.
- Options are `button`s in single mode and `checkbox`es in multiple mode, with `selected`, `checked` and `disabled`.
- Chips are buttons labelled `Remove {label}`, and × is labelled **Clear**.
- The search input is labelled with `searchPlaceholder`.
- While `loading`, the loader is a `progressbar`.

Every field, `Select`, `PhoneField` and `InputOTP` reads "required" after its label when `required` is set, and reads the `error` message as its hint.

## Slider and rating

- Each slider thumb is `adjustable`: swipe up or down to step it. It's named by `accessibilityLabel`, or `thumbLabels` on a range (default **Minimum** and **Maximum**), and its value is the formatted number.
- An interactive `Rating` is `adjustable` too, named **Rating** by default, with a value such as "3 of 5" (`formatValue`). A `readOnly` rating is read as text.

## Codes and phone numbers

- `InputOTP` is one text input named **Verification code** by default; the boxes are hidden from screen readers. It asks for SMS autofill (`oneTimeCode` on iOS, `sms-otp` on Android).
- In `PhoneField`, the country button reads "Country code: " with the country and its dialing code, with an `expanded` state. The number input asks for phone autofill (`tel`).

## DropdownMenu and action sheet

The `DropdownMenu` trigger is a button with an `expanded` state. Each action is a button labelled with its label and description, with `selected` and `disabled` states. A title has the `header` role.

## Horizontal list

The list is a `radiogroup` named by `accessibilityLabel`; each item is a `radio` labelled with its `label`, with `checked` and `disabled` states.

## Emoji

Every emoji cell is a button labelled with its name ("thumbs up"). Category tabs are `tab`s with a `selected` state, and the skin-tone button is labelled **Skin tone**. A long press on an emoji opens its tones, each labelled with the name and tone ("thumbs up, skin tone 3"); the button sets a tone for every emoji without one.

## Sheets

The sheet is marked `accessibilityViewIsModal`, so focus stays inside it. The backdrop is a button labelled **Close**, string titles have the `header` role, and Android back closes the sheet.

## Keyboard

On the web, every picker works without a mouse:

| Key | What it does |
| --- | --- |
| <kbd>Tab</kbd> | Moves between fields, buttons, wheels and sliders |
| <kbd>Enter</kbd> / <kbd>Space</kbd> | Opens a field, picks the focused day, option or emoji |
| <kbd>↑</kbd> <kbd>↓</kbd> | On a wheel, steps one row. In a calendar, list or grid, moves to the cell above or below. From a search field, goes into the results, and back |
| <kbd>←</kbd> <kbd>→</kbd> | Moves to the next cell, wrapping to the next row, or to the next wheel of a date or time |
| <kbd>Home</kbd> / <kbd>End</kbd> | Jumps to the first or last cell, or to the ends of a wheel or slider |
| <kbd>Page Up</kbd> / <kbd>Page Down</kbd> | Moves a slider by a bigger step |
| <kbd>Esc</kbd> | Closes a sheet or dropdown |

Arrows follow what's drawn, so they go the right way in RTL and in any custom layout. Colour sliders and the colour square move with the arrows, and the clock dial steps its hand. When a sheet or dropdown closes, focus goes back to the field that opened it.

Buttons, checkboxes, switches and radios show a focus ring for keyboard focus only, not after a click or tap.

## Reduced motion

When the user turns on **Reduce Motion** (iOS), **Remove animations** (Android) or `prefers-reduced-motion` (browsers), every animation in the library jumps straight to its end: sheets, dropdowns, wheels snapping, switches, checkmarks, the segmented thumb and press ripples. Buttons stop shrinking while pressed; the dim or ripple alone answers the press. Looping animations, such as the skeleton's pulse and the OTP caret's blink, hold still. Nothing to configure.

## Your checklist

- Give every wheel an `accessibilityLabel`.
- Translate the English accessibility strings by passing translated `label` / `placeholder` / `searchPlaceholder` props.
- Keep custom `renderDay` / `renderOption` content as plain views and text. The library already provides the pressable and its accessibility props.
- Keep colour contrast when theming: `textSecondary` on `background` should meet WCAG AA (4.5:1) for body text.
