[
    {
        "role": "user",
        "content": "%20Is%20there%20a%20way%20of%20making%20the%20claude%20client%20more%20compatible%20with%20jaws"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 there *are* ways to improve compatibility between Claude (especially Claude Code or the Claude client) and the JAWS screen reader, though with some caveats. I\u2019ll walk you through what works already, what gaps remain, and the steps you can take (including workarounds and giving feedback) to get a better experience.\n\n---\n\n## \u2705 What Claude already supports\n\n1. **\u201cScreen reader mode\u201d in Claude Code (CLI)**  \n   If you're using **Claude Code** from the terminal (command line), there's a built-in screen reader mode that simplifies output, removes decorative visuals, adds labels (\u201cyou:\u201d, \u201cclaude:\u201d, etc.), and presents menus and prompts in a sequential, plain-text format. This version is usable with JAWS. ([support.claude.com](https://support.claude.com/en/articles/15924927-use-claude-code-cli-with-a-screen-reader?utm_source=openai))\n\n2. **General accessibility guidelines**  \n   Claude has a *Screen Reader Compatibility Guide*, which outlines how interfaces (especially Claude Code and generated code) should work with popular screen readers including JAWS. It discusses best practices like structuring output (e.g. marking operation statuses, using ARIA live regions in browser components) to make content more accessible. ([script-kit.github.io](https://script-kit.github.io/claude-research/docs/development/accessibility/screen-reader-guide?utm_source=openai))\n\n---\n\n## \u26a0\ufe0f Known limitations and gaps\n\n- The regular Claude web interface (browser) and desktop apps often **do not** read text aloud automatically; there is no built-in text-to-speech (TTS) mode on desktop or web for Claude responses. That means users must rely entirely on the screen reader to navigate and read responses themselves. ([reddit.com](https://www.reddit.com/r/Anthropic/comments/1sskvzl/why_is_tts_mobileonly_your_disabled_desktop_users/?utm_source=openai))  \n- Many users have reported accessibility gaps with Claude in its GUI (chat input fields, notifications, formatting, UI scaling, etc.), especially for blind or low-vision users. ([reddit.com](https://www.reddit.com/r/Anthropic/comments/1lhwc9o?utm_source=openai))\n\n---\n\n## \ud83d\udd27 What you can do right now to improve compatibility\n\nDepending on which version of Claude you\u2019re using (CLI, desktop, browser), try these:\n\n| Scenario | What to try |\n|---------|-------------|\n| **Using Claude Code in terminal** | Turn on the \u201cscreen reader mode\u201d by either:<br>\u2022 Running `claude --ax-screen-reader` for one session<br>\u2022 Setting the environment variable `CLAUDE_AX_SCREEN_READER=1`<br>\u2022 Adding `\"axScreenReader\": true` to your settings file `~/.claude/settings.json` ([support.claude.com](https://support.claude.com/en/articles/15924927-use-claude-code-cli-with-a-screen-reader?utm_source=openai)) |\n| **Using desktop app or browser** | Try using JAWS\u2019 navigation commands to read through content. Disable any visual clutter (themes, extra UI elements) and see if High Contrast or magnifier settings help. Use built-in browser shortcuts (like heading navigation, list navigation) where possible. |\n| **Requesting features / filing bug reports** | Send feedback to Anthropic via their \u201cGet Help\u201d / \u201cSupport\u201d options in Claude. If you\u2019re on a paid plan (Pro, Max, Team, Enterprise), reach out directly \u2014 feature requests or accessibility bugs often get more visibility. |\n\n---\n\n## \ud83d\udd2e Possible future improvements\n\nThese are things many users are requesting or that Anthropic has hinted at / is working on:\n\n- **Desktop/web text-to-speech (TTS)** \u2014 having Claude read its own replies aloud (especially helpful on desktop). Many users see this as an essential accessibility feature. ([reddit.com](https://www.reddit.com/r/Anthropic/comments/1sskvzl/why_is_tts_mobileonly_your_disabled_desktop_users/?utm_source=openai))  \n- **UI improvements** \u2014 better labeling of interactive elements, better support for keyboard navigation, consistent screen reader announcements.  \n- **Consistent theme scaling and contrast options** \u2014 to help with vision impairments or sensitivity to light.\n\n---\n\nIf you tell me *which specific environment* you\u2019re using (CLI, desktop app, browser, version of Claude, and version of JAWS), I can give more targeted steps (or even settings you can try) to tailor the experience further. Would you like me to walk through that with your setup?"
    },
    {
        "role": "user",
        "content": "yes%2C%20jaws%20works%20fairly%20well%2C%20but%20its%20very%20difficult%20to%20locate%20recent%20replies%20and%20general%20conversation%20navigation"
    },
    {
        "role": "assistant",
        "content": "Great, knowing that makes it easier to tailor suggestions. Here are specific strategies to help you locate recent replies and navigate conversations more effectively when using JAWS with Claude (web or desktop), along with some ideas for improvements you or Anthropic might apply.\n\n---\n\n## \ud83d\udd0d How JAWS modes affect navigation\n\nFirst, pick the right mode in JAWS:\n\n- **Browse mode** (Virtual Cursor on): Best for reading content that's not directly focusable, like large blocks of text (Claude responses). But arrow keys might not always move you to the next recent message reliably.\n- **Forms/Focus mode**: Switches when you\u2019re typing. In this mode, many focusable elements (input boxes, buttons) are navigable via Tab/Shift-Tab, so you can jump from the message input field back up to previous messages.  \n  (These are standard JAWS behaviors.) ([webaim.org](https://webaim.org/articles/jaws/?utm_source=openai))\n\nIf things feel lost in web or desktop apps, try alternating between browse mode and focus mode to navigate up/down messages vs. jumping to controls.\n\n---\n\n## \ud83d\udd11 Useful JAWS navigation shortcuts\n\nHere are some built-in JAWS & browser shortcuts to help skim through conversation threads and find new or recent content faster:\n\n| Shortcut | What it helps you do |\n|----------|-----------------------|\n| `JAWS + \u2193` (\u201cSay All\u201d) | Reads everything from the current place forward. Good when you\u2019ve been away and want to hear everything you missed. ([webaim.org](https://webaim.org/articles/jaws/?utm_source=openai)) |\n| `Tab` / `Shift + Tab` | Moves between focusable elements like buttons, links, input boxes ( reply box, conversation thread). Helps you leave the input box and move up into the conversation messages. ([webaim.org](https://webaim.org/resources/shortcuts/jaws?utm_source=openai)) |\n| Headings navigation (H / Shift + H) | If Claude\u2019s web interface uses headings (like \u201cConversation\u201d, \u201cResponse\u201d, etc.), you can jump from heading to heading. Not all parts may be marked properly but it's worth trying. |\n| Links list (`JAWS + F3`) | Brings up all links on the page. If there is a sidebar with conversation list or \u201cRecent\u201d, you may find it here. ([webaim.org](https://webaim.org/resources/shortcuts/jaws?utm_source=openai)) |\n| Text search (`Ctrl + F`) | Search for words like \u201cyou:\u201d or \u201cclaude:\u201d or \u201creply\u201d \u2014 or a keyword you remember \u2014 to jump directly where that appears. |\n\n---\n\n## \u2699\ufe0f Claude-side tools / shortcuts\n\nThese can help you move between chats, locate recent replies, and reduce the scrolling or guessing:\n\n- Web/Desktop Claude has keyboard shortcuts such as:\n  - `Ctrl (or Cmd) + Shift + O`: Start a new chat (so you can return to a clean state). ([shortcut-tools.com](https://shortcut-tools.com/en/shortcuts/claude/?utm_source=openai))  \n  - `Ctrl (or Cmd) + Shift + S`: Toggle the sidebar (chat history), letting you quickly focus on the list of conversations. ([shortcut-tools.com](https://shortcut-tools.com/en/shortcuts/claude/?utm_source=openai))  \n  - `Ctrl (or Cmd) + Shift + ;`: Focus the message input field, useful for jumping straight to where you can start typing. ([claudecodeguides.com](https://claudecodeguides.com/claude-shortcuts-complete-guide/?utm_source=openai))  \n\n- In **Claude Code (CLI)** using screen reader mode:\n  - It labels messages with `you:` and `claude:` so you can search in terminal for \u201cclaude:\u201d to find Claude\u2019s last response easily. ([support.claude.com](https://support.claude.com/en/articles/15924927-use-claude-code-cli-with-a-screen-reader?utm_source=openai))  \n  - Menus convert to numbered lists, so you hear each option clearly and can speak or type the number. View counts, prompts, etc., all come in plain, sequential text with minimal distractions. ([support.claude.com](https://support.claude.com/en/articles/15924927-use-claude-code-cli-with-a-screen-reader?utm_source=openai))  \n\n- You can also customize keyboard shortcuts in Claude Code (v2.1.18+), including scroll, transcript view etc., which may help you bind keys that better work with JAWS navigation. ([code.claude.com](https://code.claude.com/docs/en/keybindings?utm_source=openai))  \n\n---\n\n## \ud83d\udd27 Workarounds and enhancements you can try\n\nIf the default behavior still makes locating messages and navigating tedious, these tweaks might help:\n\n1. **Bookmark or \u201canchor\u201d system**  \n   - Use your browser\u2019s built-in bookmarks or notes to mark \u201clast reply heard\u201d. Then use the location (URL fragment, or scrolling) to return to that message.\n\n2. **Short chats / breakpoints**  \n   - Occasionally start a new chat if a topic has diverged; shorter threads are easier to navigate. Keep older conversations saved by topic.\n\n3. **Use external tools or scripts**  \n   - AutoHotkey or similar tools could map keys like PageUp / PageDown or Home / End to move you faster through the conversation pane if the app doesn\u2019t support it well. There are existing threads complaining that arrow keys / PgUp / PgDn don\u2019t always work in Claude Desktop. ([reddit.com](https://www.reddit.com/r/ClaudeAI/comments/1sopfgw/claude_desktop_no_keyboard_scrolling_is_it_just_me/?utm_source=openai))\n\n4. **Feedback / feature requests**  \n   - Ask Anthropic to add:  \n     \u2022 A \u201cjump to latest unread reply\u201d shortcut  \n     \u2022 Bookmarks or message markers inside the conversation  \n     \u2022 A \u201cmessage list\u201d sidebar that your screen reader can access  \n\n   There are already feature requests from users asking for better navigation tools like quote-jumping, message bookmarks, sidebar lists, etc. ([reddit.com](https://www.reddit.com/r/ClaudeAI/comments/1sl72a3/4_feature_requests_to_improve_navigation_in_long/?utm_source=openai))  \n\n---\n\nIf you tell me exactly *which* version of Claude (web vs desktop vs CLI) and what browser or environment (Windows + JAWS version + browser) you\u2019re using, I can suggest a set of custom shortcuts or even a personalized \u201cnavigation cheat sheet\u201d that fits your setup. Do you want me to build that out for your setup?"
    },
    {
        "role": "user",
        "content": "%20are%20there%20not%20any%20jaws%20scripts%20for%20claude%20desktop"
    },
    {
        "role": "assistant",
        "content": "I couldn\u2019t find any evidence of publicly available **JAWS scripts** specifically written for *Claude Desktop*. Here\u2019s what I did find \u2014 and what that suggests about possible paths forward.\n\n---\n\n## \ud83d\udd0d What I found\n\n- There's no listing in official Claude documentation or accessible forums about specific JAWS Script Library (JSL) files created for Claude Desktop.\n- Several users on Reddit have asked for or shared small hacks or browser userscripts (e.g., for the web version) that improve navigation, but these aren\u2019t the same as supported JAWS script files for the desktop app. ([reddit.com](https://www.reddit.com/r/ClaudeAI/comments/1sfxgvn/anthropic_your_accessibility_is_an_embarrassment/?utm_source=openai))\n- The *Claude Screen Reader Compatibility Guide* covers how Claude Code and AI-generated code should behave with screen readers (including JAWS), but it doesn\u2019t mention custom JAWS scripts for desktop or chat. ([script-kit.github.io](https://script-kit.github.io/claude-research/docs/development/accessibility/screen-reader-guide?utm_source=openai))\n- There\u2019s no indication in the \u201cClaude Desktop\u201d release notes, support articles, or accessibility docs that a script file for JAWS was shipped or supported. ([support.claude.com](https://support.claude.com/en/articles/10065433-install-claude-desktop?__from__=talkingdev&utm_source=openai))\n\n---\n\n## \ud83e\uddd0 What this means\n\n- **Absence of evidence** suggests such scripts may not exist (or aren't publicly shared).\n- Some users have tried DIY fixes (userscripts or interface tweaks), especially in the browser version, but those don\u2019t translate directly to desktop apps for JAWS.\n- Without semantic markup or explicit support from Claude, navigation with JAWS often depends on how well the app implements accessibility standards (semantic HTML, ARIA roles, keyboard focus, etc.).\n\n---\n\n## \u2699\ufe0f Workaround ideas & next steps\n\nTo improve navigation without specific scripts, or to try encouraging creation of scripts, here are some suggestions:\n\n1. **Reach out for support & accessibility requests**  \n   Ask Anthropic\u2019s accessibility team directly if they can release a JAWS script file (a `.jsl` file) or offer improved keyboard navigation. Sometimes feature requests can lead to internal script development.\n\n2. **Build your own JAWS script**  \n   - If you\u2019re comfortable with code or have access to assistive tech developers, you might try writing a simple JAWS Script Library file yourself.  \n   - You\u2019ll need to use JAWS\u2019 scripting tools (Script Manager, etc.), inspect Claude Desktop\u2019s interface to see control names, classnames or window titles you can target.  \n   - Simple features like \u201cjump to newest message\u201d, \u201cfind last sender label\u201d, etc., can often be scripted.\n\n3. **Use userscripts for browser/web version**  \n   If using Claude in browser, users have had some success with *Violentmonkey* / *Tampermonkey* scripts that restructure the page (e.g. add landmarks, labels). Not a perfect solution for desktop, but can help you compare behaviors and see what works. ([reddit.com](https://www.reddit.com/r/ClaudeAI/comments/1sfxgvn/anthropic_your_accessibility_is_an_embarrassment/?utm_source=openai))\n\n4. **Alternate screen reader or configuration**  \n   Some users report *NVDA* works better for navigating Claude chat threads, possibly because it handles HTML content differently. Trying another reader might help, or at least give you a basis for comparison. ([reddit.com](https://www.reddit.com/r/Blind/comments/1v80cpq/screen_readers_and_ai_apps/?utm_source=openai))\n\n---\n\nIf you want, I can try to find or even attempt to design a draft JAWS script for Claude Desktop based on its current interface (version you\u2019re running). Would you like me to start pulling together something customized to your version of Claude?"
    }
]