Why Meta Quest?

Distribute and grow

Design

Design

Intro to immersive design

Key considerations

User considerations

Physical health and safety

General information

Shared Spatial Anchors

Accessibility checklist

Prototype setup

Input modalities

Quickstart prototype

Core interactions

Input hierarchy

Locomotion types

User preferences

Virtual environments

Comfort and usability

Spatial context

Scene understanding

Spatial anchors

Output modalities

Lighting and effects

Graphics pipeline

Virtual keyboard

Immersive audio

Listening devices

Immersive sound

Art preproduction

Sourcing assets

Art and performance

Hand representation

Icons and Images

Inputs and hit targets

Foundations

Accessibility checklist

Updated: Apr 13, 2026

Use this checklist during development to verify your app’s accessibility before submitting to the Meta Horizon Store. Each item links to guidance on the accessibility design page and to the accessibility VRCs.

All accessibility VRCs are recommended, not required for Store submission. Your app will not be rejected for missing these items, but meeting them improves the experience for users of your app.

VRC recommendations

These items map to accessibility VRCs evaluated during Store review. All are recommended, not required.

Vision and display

Text and in-app controls are clearly legible, with options for increased contrast or larger UI elements (VRC.Quest.Accessibility.2)

Users can adjust in-app display settings such as brightness and contrast to accommodate visual needs (VRC.Quest.Accessibility.5)

Color blindness is supported through color combined with patterns, icons, or text labels for visual distinction (VRC.Quest.Accessibility.6)

See color contrast, text sizing, and styles: color.

Hearing

App is playable without audio, or provides subtitles for all dialogue and sound effects (VRC.Quest.Accessibility.1)

Interactions provide feedback through multiple cues — visual, audio, and haptic — instead of relying on a single channel (VRC.Quest.Accessibility.3)

See hearing controls and captions and subtitles.

Input and interaction

App can be played with one hand or one controller, with configurable controller options when possible (VRC.Quest.Accessibility.4)

See mobility controls.

Movement and locomotion

Users can rotate their view without physically moving their head or neck (VRC.Quest.Accessibility.7)

Multiple locomotion styles are supported, such as teleportation, free locomotion, and snap turning (VRC.Quest.Accessibility.8)

All interactions are accessible from a fixed seated or standing position — immersive apps only (VRC.Quest.Accessibility.9)

See mobility controls.

Design best practices

These items do not map to specific VRCs but follow WCAG 2.1⁠ and Android accessibility guidelines⁠. They help you meet the VRC recommendations above and help you improve your experience overall.

Text and contrast

All text uses scalable units (sp) for font sizes, not fixed pixel values (dp)

Normal text meets a 4.5:1 contrast ratio; large text (18pt+, or 14pt bold) and UI components meet 3:1

Information is not conveyed by color alone — patterns, icons, or text labels accompany color indicators

See color contrast and fonts and icons: color in type.

Screen reader support

All images have alternative text or are marked as decorative (not important for accessibility)

All interactive elements have contentDescription attributes with meaningful, concise descriptions

App uses standard audio APIs so the system live captions feature works correctly

See screen reader and text-to-speech support and hearing controls.

Focus and navigation

All interactive elements have a visible focus state distinct from hover and selected states

Focus order matches visual layout and focus is never trapped in a single element or region

The entire app is navigable using only a controller

See focus indicators and mobility controls.

Interaction

Interactive elements have a minimum hit target of 48dp × 48dp; visual targets are at least 32dp × 32dp

No interactions require precise timing without alternatives or extensions

Gesture-based interactions have alternative input methods for users who cannot perform the required gestures

Error messages are clear, descriptive, and readable by screen readers

See hit targets and mobility controls.

Testing before submission

After completing the checklist, run through the testing scenarios on the accessibility design page to verify your app on an actual device.

Test with:

Screen reader enabled (Settings > Experimental)

Text size at minimum and maximum values

Color correction enabled

Live captions enabled

Controller-only navigation

Voice controls enabled

Remapped controller buttons

Next steps

Accessibility design guidelines: Full guidance on building accessible immersive experiences.

Accessibility VRCs: Store review recommendations for accessibility.

Android accessibility guidelines⁠: Platform-level accessibility APIs and patterns.

Build with Meta

Social Technologies

About us

Virtual reality / Meta Horizon

Meta Horizon Creator Program

Discover

Why Meta Quest?

What is mixed reality?

Platforms and tools

2D apps for Meta Horizon OS

Success stories

Support and legal

Developer policies

Build with Meta

Social Technologies

About us

Virtual reality / Meta Horizon

Meta Horizon Creator Program

Discover

Why Meta Quest?

What is mixed reality?

Platforms and tools

2D apps for Meta Horizon OS

Success stories

Support and legal

Developer policies

Build with Meta

Social Technologies

About us

Virtual reality / Meta Horizon

Meta Horizon Creator Program

Discover

Why Meta Quest?

What is mixed reality?

Platforms and tools

2D apps for Meta Horizon OS

Success stories

Support and legal

Developer policies

English (US)

© 2026 Meta