[
    {
        "role": "user",
        "content": "Is%20the%20Discord%20platform%20accessible%20with%20JAWS%3F"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 Discord *is* accessible with JAWS, though the experience depends on which platform you\u2019re using (desktop, browser, or mobile) and on keeping certain settings up to date. Here\u2019s a detailed look at how well it works, what you can expect, and tips to improve the experience.\n\n---\n\n### \u2705 What the Evidence Shows\n\n- **Official Accessibility Commitment**  \n  Discord aims to meet WCAG 2.1 standards (Level AA). They state they include screen reader support in their accessibility tools and provide a dedicated Accessibility team to address issues. ([discord.com](https://discord.com/accessibility?utm_source=openai))\n\n- **Accessibility Features Built In**  \n  The platform supports features like:\n  - Text-to-speech (TTS) with adjustable speed  \n  - High contrast mode and contrast sliders/options  \n  - Reduced motion, control of animated emojis and GIFs  \n  - Keyboard navigation (tab order, roles/colors options, etc.) ([support.discord.com](https://support.discord.com/hc/en-us/articles/1500010454681-Accessibility-Settings-Tab?utm_source=openai))\n\n- **JAWS-Specific Support**  \n  A custom script system is maintained for Discord to enhance its interaction with JAWS. Notably, recent versions of JAWS (from 2019 onward) are compatible with these scripts. Some features provided by the scripts include:\n  - Reading chat messages properly  \n  - Announcing unread direct messages on servers  \n  - Reporting voice or stage activity in servers  \n  - Allowing keyboard-only actions to manage voice channels (connect/disconnect) using specific sequences ([dlee.org](https://www.dlee.org/discord/?utm_source=openai))\n\n- **Community Feedback & Review**  \n  The American Foundation for the Blind tested Discord using other screen readers like NVDA and found the desktop and browser clients are very well-labeled, include well-defined controls, and have few unlabeled UI elements. While the mobile version has more issues, there is general agreement that Discord is usable with patience and by learning the available shortcuts. ([afb.org](https://afb.org/aw/23/12/18148?utm_source=openai))\n\n---\n\n### \u26a0\ufe0f What Can Be Challenging\n\n- **App vs. Browser Differences**  \n  Some announcements or live region updates may not be accessible when using the Discord *desktop app*, depending on both your version of JAWS and certain settings. The browser version tends to perform more reliably in some of these respects. ([support.discord.com](https://support.discord.com/hc/en-us/articles/4408877527703-Accessible-Drag-and-Drop-FAQ?utm_source=openai))\n\n- **Set-up Matters**  \n  - You need JAWS version 2019 or newer for full support of the custom scripts. ([dlee.org](https://www.dlee.org/discord/?utm_source=openai))  \n  - Ensure the setting \u201cAnnounce Live Region Updates\u201d is enabled for Discord in JAWS. Without it, you might miss important UI updates (like server list info, read/unread status, etc.). ([support.discord.com](https://support.discord.com/hc/en-us/articles/4408877527703-Accessible-Drag-and-Drop-FAQ?utm_source=openai))\n\n- **Mobile Experience**  \n  The iOS and Android apps have more reported issues: items sometimes aren\u2019t labeled correctly, navigation can be less intuitive, and some gestures aren\u2019t well supported. ([afb.org](https://afb.org/aw/23/12/18148?utm_source=openai))\n\n---\n\n### \ud83d\udee0\ufe0f Tips for Using Discord with JAWS More Effectively\n\n1. **Use the browser version of Discord** (Chrome, Edge, Firefox) when possible. It often works better with screen reader announcements, especially live updates.  \n   ([support.discord.com](https://support.discord.com/hc/en-us/articles/4408877527703-Accessible-Drag-and-Drop-FAQ?utm_source=openai))\n\n2. **Get the JAWS \u201cDiscord\u201d-specific scripts** \u2014 they add or fix behaviors like announcing unread messages, enabling keyboard shortcuts for voice channel actions, etc.  \n   ([dlee.org](https://www.dlee.org/discord/?utm_source=openai))\n\n3. **Check your JAWS settings**:  \n   - \u201cAnnounce Live Region Updates\u201d is enabled for Discord.  \n   - You\u2019re using a current version that supports the community scripts.  \n   ([support.discord.com](https://support.discord.com/hc/en-us/articles/4408877527703-Accessible-Drag-and-Drop-FAQ?utm_source=openai))\n\n4. **Explore Discord\u2019s Accessibility settings**  \n   In Discord go to *User Settings > App Settings > Accessibility*. Here you can adjust TTS rate, enable/exclude animations, toggle high contrast mode, control color usage for roles and more.  \n   ([support.discord.com](https://support.discord.com/hc/en-us/articles/1500010454681-Accessibility-Settings-Tab?utm_source=openai))\n\n5. **Familiarize yourself with keyboard navigation and shortcuts**  \n   There are many hotkeys for jumping between servers, messages, channels, etc. Learning them makes the app much easier to use with a screen reader.  \n   ([discord.com](https://discord.com/accessibility?utm_source=openai))\n\n---\n\n### \u2696\ufe0f Bottom Line\n\nDiscord *is* accessible with JAWS, especially on desktop and in the browser. The combination of Discord\u2019s increasing accessibility efforts and JAWS support (via native features + external scripts) means the core functionality\u2014chatting, joining voice channels, navigating servers\u2014*can* be fully usable. But expect some setup work (scripts and settings) and accept that the mobile experience may require workarounds or patience.\n\nIf you'd like, I can help walk you through configuring Discord & JAWS specifically, or find a guide or setup checklist tailored to your exact version of JAWS. Do you want that?"
    }
]