No developer documentation on making applications compatible with OS accessibility features

As of May 2026, besides the documentation on "Lying Down Mode", there is no documentation for developers building Meta Quest applications on how to make sure that their applications are accessible and compatible with Meta's OS level accessibility features. According to Unity, 70%+ of top-selling Quest games are made with Unity. Despite Unity being the most popular platform for building Meta Quest applications, when you search for accessibility on the Unity developer documentation on Meta's documentation site for Quest, this is the only result:  

Also if you search for accessibility on the developer documentation for all other platforms, you get the same results and some platforms don't even provide the Lying Down Mode documentation.

While there is accessibility feature documentation for end users of the Meta Quest platform as well as design documentation for Meta Quest software developers, there is no corresponding developer documentation or example projects for how to actually implement these accessibility design guidelines to adhere to accessibility standards. 

While we have figured out our own ways to build our applications to adhere to most accessibility standards and be compatible most Meta OS accessibility features, so far we have not successfully found any way to make our application compatible with the Meta OS screen reader. We have followed the design guidelines, but the screen reader does not work with our application. Also in general the screen reader does not seem to work very well at all, and it is nearly impossible to turn off. There is another community thread where some guidance is provided, but in practice following this guidance does not help and most often a hard reboot is required which goes to show how unusable the screen reader feature is.