@oxyhq/bloom 0.88.0 → 0.89.0

package/src/select/index.web.tsx

@@ -324,7 +324,10 @@ export function SelectItem({ ref, value, label, children, style }: SelectItemPro
       // dropped it, leaving every option a `role="radio"` with no accessible
       // name for a screen reader to announce.
       accessibilityLabel={label}
-      accessibilityState={{ checked: isSelected }}
+      // `aria-checked` is the state ARIA defines for `role="radio"`, and the
+      // only one react-native-web emits — it never reads `accessibilityState`,
+      // so this fork's options announced no selection at all.
+      aria-checked={isSelected}
       onPress={() => {
         ctx.onValueChange?.(value);
         ctx.close();

package/src/settings-list/SettingsList.tsx

@@ -128,7 +128,10 @@ export const SettingsListItem = memo<SettingsListItemProps>(function SettingsLis
       accessibilityRole={role}
       accessibilityLabel={label}
       accessibilityHint={accessibilityHint}
-      accessibilityState={disabled ? { disabled: true } : undefined}
+      // See the pressable branch above, which gets `aria-disabled` for free
+      // from its `disabled` prop. A `View` has no such prop, and
+      // react-native-web never reads `accessibilityState`.
+      aria-disabled={disabled || undefined}
     >
       {content}
     </View>

package/src/slider/Slider.tsx

@@ -198,8 +198,16 @@ const SliderComponent = function Slider({
       testID={testID}
       accessibilityRole="adjustable"
       accessibilityLabel={accessibilityLabel}
-      accessibilityValue={{ min, max, now: value }}
-      accessibilityState={{ disabled }}
+      // react-native-web reads the FLAT `aria-value*` props; it has no handling
+      // for the `accessibilityValue` object at all, so this rendered a
+      // `role="slider"` carrying no value whatsoever — a screen reader could
+      // say the control existed but never what it was set to. React Native
+      // folds these three back into `accessibilityValue`, and `aria-disabled`
+      // into `accessibilityState`, so native keeps what it had.
+      aria-valuemin={min}
+      aria-valuemax={max}
+      aria-valuenow={value}
+      aria-disabled={disabled || undefined}
       style={[
         styles.root,
         { height: Math.max(thumbSize, trackHeight) + 8 },

package/src/switch/Switch.tsx

@@ -82,7 +82,13 @@ const SwitchComponent = React.forwardRef<React.ElementRef<typeof Pressable>, Swi
         ref={ref}
         role="switch"
         aria-checked={value}
-        accessibilityState={{ checked: value, disabled }}
+        // The disabled state has to travel on this prop, not on `aria-disabled`:
+        // react-native-web's `Pressable` appends its own `aria-disabled` from
+        // `disabled` AFTER spreading the caller's props, so a caller-supplied
+        // one is overwritten. `handlePress` already no-ops when disabled, so
+        // this only adds what was missing — the announced state, and skipping
+        // the control in the tab order.
+        disabled={disabled}
         onPress={handlePress}
         onPressIn={onPressIn}
         onPressOut={onPressOut}

package/src/tab-bar/TabBarBase.tsx

@@ -569,7 +569,10 @@ function TabBarButtonBody({
       // Accessibility defaults come BEFORE the spread so an explicit prop — or
       // one injected by a router trigger — still wins.
       accessibilityRole="tab"
-      accessibilityState={{ selected: focused }}
+      // `aria-selected` is the state ARIA defines for `role="tab"`, and the one
+      // spelling both platforms read: react-native-web ignores
+      // `accessibilityState`, React Native folds `aria-selected` into it.
+      aria-selected={focused}
       accessibilityLabel={item.label}
       {...pressableProps}
       onPress={(event) => {