Accessibility
LUDIA = AI + UDL · Universal Access to Universal Design for Learning
We built LUDIA to work for as many educators and learning leaders as possible. This statement tells you what works today, what does not, and what we are working on. It is written in plain language. The references at the end point to the formal standards we follow.
Standards we follow
- Web Content Accessibility Guidelines (WCAG) 2.2, level AA. This is the international accessibility standard from the World Wide Web Consortium (W3C). LUDIA is built to meet level AA.
- European Accessibility Act (EAA). This is Directive (EU) 2019/882. It became enforceable on 28 June 2025 for many digital services in the EU. LUDIA is built to meet the EAA accessibility requirements for chat-based services.
Accessibility features
- Keyboard access. You can move through LUDIA using the Tab key. Press Enter to send a message.
- Screen reader support. LUDIA uses standard HTML controls and ARIA labels so screen readers can announce the chat. We test with NVDA on Windows, Orca on Linux, VoiceOver on macOS and iOS, and TalkBack on Android.
- Readable type. The body font is Lexend Deca. It was chosen because the letter shapes are open and easy to tell apart, which helps readers with dyslexia and low vision.
- Strong color contrast. Body text and chat bubbles meet or exceed the WCAG 2.2 AA ratio of 4.5 to 1.
- Resizable text. You can zoom your browser up to 200 percent and the chat still works, along with settings for changing the default text size.
- Plain replies. LUDIA is tuned to reply in clear sentences. You can also ask it to simplify any answer in plain language.
- Multilingual. You can ask LUDIA to reply in many languages.
- Web-based. LUDIA runs in any current web browser. Nothing to install.
Speech to text and text to speech
- No speech-to-text (STT) inside LUDIA. You cannot speak to LUDIA and have your words appear in the chat using a button inside LUDIA.
- No text-to-speech (TTS) inside LUDIA. LUDIA does not read its replies aloud using a button inside LUDIA.
Why voice is not built in
Most voice features in chatbots send your audio, or the chat text, to a separate voice service run by another company. That company can keep the audio, log it, and sometimes use it to train other systems. Some of those servers sit outside Europe.
LUDIA does not save your chats and does not build a profile of you. Adding a voice service that quietly sends your audio to a third party would break that promise. So we have chosen, for now, not to build voice in.
What you can use instead
Your computer and your browser already include strong voice tools. They run on your device, so your audio does not leave your computer. You can use any of these with LUDIA today:
- Speech-to-text on your computer. Windows has Voice Access. Mac has Voice Control and Dictation. Chromebook has Dictation. iPad and iPhone have Dictation. Android has Voice Typing. Turn it on and dictate straight into the LUDIA chat box.
- Text-to-speech on your computer. Most systems can read selected text aloud. You can select LUDIA's reply and have your computer speak it. Screen readers (NVDA, JAWS, Orca, VoiceOver, TalkBack, Narrator) also work.
- Browser extensions. Many extensions add voice to any website. Some send text to third parties. Please read the extension's own privacy policy before using it.
Compatibility
LUDIA works in the current versions of these web browsers: Chrome, Edge, Firefox, and Safari.
LUDIA has been tested with the screen readers NVDA (Windows), Orca (Linux), VoiceOver (macOS and iOS), and TalkBack (Android). We continue to expand testing.
Known limits
- No speech-to-text or text-to-speech inside the chat (see above).
- Reading-level adjustment is done by asking LUDIA in chat, not by a separate setting.
- Some assistive technology combinations may behave differently. Please report anything that does not work.
Conformance status
LUDIA is built to conform to WCAG 2.2 at level AA. We are not aware of any current WCAG 2.2 AA failures.
Built-in speech-to-text and text-to-speech are not WCAG requirements. The decision not to include them is a privacy-driven design choice explained in the section above, not a conformance gap. Users who need voice input or output can use the on-device alternatives listed there.
How we test accessibility
We use a mix of methods, not just automated scans:
- Automated tools to catch common issues.
- Manual keyboard-only testing of every interactive element.
- Manual screen reader testing with NVDA on Windows, Orca on Linux, VoiceOver on macOS and iOS, and TalkBack on Android.
- Color and contrast checks against WCAG 2.2 AA ratios.
- Direct feedback from educators who use assistive technology.
LUDIA does not yet have third-party accessibility certification. That is on our roadmap.
Contact us if something does not work
Please tell us right away. Accessibility reports are a priority. We treat them as urgent and we will respond to you personally.
How to reach us
Email: accessibility@askludia.comWhat helps us help you
Share whatever you can:
- What you were trying to do.
- What happened, or what did not happen.
- The page or chat where it occurred.
- The browser and assistive technology you were using.
- How you would like us to reply (email, plain text, or another format).
What we promise
- Acknowledge your message within 2 business days.
- Reply with concrete next steps within 5 business days.
- Fix accessibility barriers as quickly as we can. When a fix will take longer, we will give you an honest timeline.
- Offer an alternative way to access the content while we work on the fix.
- Reply in your preferred format wherever possible.
References
Council of the European Union & European Parliament. (2019). Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the accessibility requirements for products and services. Official Journal of the European Union, L 151, 70–115. https://eur-lex.europa.eu/eli/dir/2019/882/oj
European Telecommunications Standards Institute. (2021). Accessibility requirements for ICT products and services (EN 301 549 V3.2.1). ETSI. https://www.etsi.org/deliver/etsi_en/301500_301599/301549/
World Wide Web Consortium. (2023, June 6). Accessible rich internet applications (WAI-ARIA) 1.2 (W3C Recommendation). https://www.w3.org/TR/wai-aria-1.2/
World Wide Web Consortium. (2023, October 5). Web content accessibility guidelines (WCAG) 2.2 (W3C Recommendation). https://www.w3.org/TR/WCAG22/
Last reviewed: 29 June 2026. Next scheduled review: 29 June 2027.