Do I need to implement eye tracking accessibility?

Implementing eye tracking accessibility is not strictly necessary, but it can significantly enhance the user experience, especially for users of visionOS and Apple Vision Pro. Here are some key points to consider:

Natural Input with VisionOS:
- VisionOS uses natural input, allowing users to target interaction regions with their eyes and interact by tapping their fingers together. This is highlighted in the session Optimize for the spatial web.
Privacy Considerations:
- VisionOS ensures user privacy by keeping the gaze data private. The highlights indicating where the user is looking are drawn by a process outside of Safari, ensuring that even the browser does not know where the user is looking (Optimize for the spatial web).
WebXR and Gaze Interaction:
- In WebXR, gaze and pinch interactions are used, but knowing what the user is looking at is considered sensitive information. Spatial inputs only reveal where the user was looking at the moment of a pinch (Build immersive web experiences with WebXR).
Hand Tracking:
- Hand tracking is a primary means of input on visionOS, and it can be used to detect gestures and anchor virtual content to hands. This is discussed in the session Create enhanced spatial computing experiences with ARKit.
Accessibility in SwiftUI:
- SwiftUI provides robust accessibility features, ensuring that all interactive elements are accessible through technologies like VoiceOver. This is covered in the session Catch up on accessibility in SwiftUI.

Relevant Sessions

In summary, while not mandatory, implementing eye tracking accessibility can greatly improve the user experience on visionOS and Apple Vision Pro, and it aligns with Apple's commitment to privacy and accessibility.