Expo-Provided AccessibilityInfo Wrapper and React Native AccessibilityInfo Interoperability

Answer

Use import { AccessibilityInfo } from 'react-native'. There is no official Expo wrapper for AccessibilityInfo, and expo-constants does not export it. Standardizing on the direct React Native import guarantees you receive the API surface shipped with the React Native version pinned by your Expo SDK. Using a non-existent expo wrapper would create version skew and break builds.

Confirmed facts

• AccessibilityInfo is a React Native core module. The canonical import is import { AccessibilityInfo } from 'react-native'.
• expo-constants provides app manifest constants, build info and device constants. It does not export AccessibilityInfo.
• There is no official Expo package named expo-accessibility that re-exports AccessibilityInfo. Expo does not provide a wrapper for this API; accessibility features are accessed directly via React Native.
• In Expo managed workflow, React Native core APIs are available as-is. The API you get is the one shipped with the React Native version pinned by the Expo SDK.

Likely explanation for the premise

The premise that expo-constants and expo-accessibility re-export AccessibilityInfo and return the same object reference is not supported by current Expo module design. The confusion likely comes from mixing app metadata modules like expo-constants with accessibility APIs, or from deprecated community re-exports that once attempted to wrap React Native modules.

Version skew and functional difference

Skew can only arise if a third-party or custom wrapper re-exports an older copy of the RN module. A true pass-through would resolve to the same React Native implementation as a direct import. An outdated wrapper would miss new APIs and behavioral changes, which would affect screen-reader announcements and focus management only if new React Native accessibility methods are not available to your code.

Steps for this case

1. Grep your codebase for AccessibilityInfo imports and ensure they resolve to 'react-native'.
2. Check package.json for expo SDK version and the resolved react-native version to know the available API surface.
3. Remove any imports from expo-constants or a package named expo-accessibility for AccessibilityInfo.
4. Log Object.keys(AccessibilityInfo) in a dev build to verify the methods match the React Native version you are on.

One diagnostic detail that changes the recommendation is your Expo SDK version and workflow type. Confirm the SDK version so the React Native version it pins can be matched to the AccessibilityInfo API you need.