> ## Documentation Index > Fetch the complete documentation index at: https://learn.playlab.ai/llms.txt > Use this file to discover all available pages before exploring further. # Accessibility > How Playlab supports accessible learning experiences for every user Playlab is **actively working toward WCAG 2.0 AA conformance** — we are not yet certified. This page describes the accessibility work in progress and the features available today. ## Our commitment Playlab is built so that every learner and every educator can use it — regardless of how they interact with the web. We are working toward conformance with the **Web Content Accessibility Guidelines (WCAG) 2.0 at the AA level**, the standard most widely referenced by schools, districts, and procurement teams. We have not yet completed a formal audit and do not claim conformance today. Accessibility is treated as an ongoing investment, not a one-time milestone. New features are reviewed against the same standards before they ship, and we will publish formal documentation once the work is complete. ## Keyboard navigation Every interactive element in Playlab can be reached and operated using only a keyboard. * **Visible focus indicators** appear on every interactive element — buttons, links, inputs, menus — so you can always see where you are on the page. * **Tab order** follows the visual reading order, so moving through a page with `Tab` and `Shift + Tab` matches what you'd expect. * **Standard keys** (`Enter` to activate, `Esc` to dismiss, arrow keys inside menus) behave consistently across the product. ## Screen reader support Playlab is designed to work with screen readers such as VoiceOver, NVDA, and JAWS. * **Accessible labels on icon buttons** — every icon-only button (send, attach, flag, share, and so on) has a descriptive label so screen readers can announce what it does, not just "button". * **Semantic structure** — pages use proper headings, landmarks, and lists so screen reader users can navigate by structure. * **State changes are announced** — when something is selected, loaded, or expanded, screen readers are notified. ## Visual design * **Color contrast** — we are working toward meeting WCAG 2.0 AA minimums for body text and interactive elements across the product. * **Color is never the only signal** — status, errors, and required fields are communicated with text or icons as well as color. * **Resizable text** — Playlab respects browser zoom and OS-level text-size preferences. ## Built-in accessibility features Several Playlab features are themselves accessibility tools you can turn on as needed: * [Voice Input](/features/Voice%20Input) — speak instead of typing, with real-time transcription * [Voice Output](/features/Voice%20Output) — listen to Playlab's responses with text-to-speech * [Using Dictation](/features/Using%20Dictation) — dictate longer responses with platform dictation * [Spanish Mode](/features/Spanish%20Mode) — operate Playlab in Spanish * [Math Inputs](/features/Math%20Inputs) — input math expressions without relying on keyboard symbols * [Camera Handwriting Input](/features/Camera%20Handwriting%20Input) — submit handwritten work via camera ## For procurement and compliance teams We are in the process of completing a formal accessibility audit and **VPAT** (Voluntary Product Accessibility Template). These documents are not yet available. If your district or procurement process requires a VPAT before purchase, please reach out so we can share our current status and timeline. > [View Data Privacy Agreements & compliance documents](/faq/Data%20Privacy%20Agreements) ## Reporting an accessibility issue If something in Playlab is blocking you or a student, we want to hear about it. Accessibility issues are prioritized. Contact us at [support@playlab.ai](mailto:support@playlab.ai) with: * A short description of what you were trying to do * The assistive technology you were using (if any) * The browser and operating system * A screenshot or screen recording if you can capture one *** *Last updated: 05-15-2026*