> For the complete documentation index, see [llms.txt](https://augmented-reality-ux-accessibili.gitbook.io/augmented-reality-storybook-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://augmented-reality-ux-accessibili.gitbook.io/augmented-reality-storybook-guide/contextual-considerations/short-intro-to-context/accessibility-context.md). # Accessibility context ## What do I mean by accessibility context? When it comes to AR, **this is a tough topic to write about.** If I'm being honest, accessibility was not the first thing I thought of when I tried to push the startup back in 2018. In fact, it never crossed my mind at that time. Why is it important? Is it even possible? This is where context comes in. We need to step our of our own shoes and think of those who may not be able to easily use an AR experience. Instead of answering the above question for you, I'll ask you this: **If we are creating new and engaging ways to do storytelling, why shouldn't any child regardless of disability be able to use it?** In my comparative analysis, I examined several AR storybooks that I found on Amazon.com. I found common pain points throughout these books, such as: * No colorblind option for AR books * No braille option for AR books * No text-to-speech options for AR apps * Over emphasis on motion controls * Limited input/output methods for interactivity * Limited tactile features within AR books * Limited or no sound to correlate the visual experience And these are just a few. The list isn't exhaustive and more research definitely needs to be conducted around accessibility for AR. ## How could AR possibly be made accessible? **You may be thinking "I can't make an AR Storybook that is accessible to literally everyone."** I encourage you to start small. Take time to research your target audience. Do more research on common pain points that children with certain disabilities may run into. You'd be surprised how much of a difference you could make by doing something as simple as adding in colorblind options or text-to-speech to your app. User context is key. Accessibility is becoming best practice across industries. One of the core reasons to design accessibly first is that it is much easier to incorporate it early rather than come back to a finished product and try to add it in. **Designing broader experiences that are accessible to more users will not only make your book useable by a larger audience, but it will also make it more appealing.** {% hint style="info" %} **Tip:** AR apps that are on the market right now may not be accessible, but does that mean they never will be? The equitability and inclusiveness of AR is already [being studied](https://itif.org/publications/2021/06/01/current-and-potential-uses-arvr-equity-and-inclusion/), and it's use as an assistive technology has already been proven valuable. But even so, it's hard to say that AR can one day be accessible to all. **It's up to us as designers and developers to come up with creative solutions to address the needs of** **all of our users.** Does AR have to remain within the confines of a visual experience, or can we find other creative ways to augment the user's world around them? {% endhint %} {% hint style="warning" %} **Accessibility Scenario:** Consider a scenario where a young child is legally blind, but wants to experience augmented reality. **What are some creative options that we can build into AR storybooks that could still provide an augmented experience for someone who has low or no vision?** * Tactile options for feeling textures in the book * Options for the app to read the text aloud * Audible image and 3D object descriptions These are just a few ways that we can augment a low vision user's world. {% endhint %} [**Send feedback**](https://forms.gle/ZMVzx4KoZE3d6Nvg7) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://augmented-reality-ux-accessibili.gitbook.io/augmented-reality-storybook-guide/contextual-considerations/short-intro-to-context/accessibility-context.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.