[
    {
        "role": "user",
        "content": "Is%20there%20a%20desktop%20app%20for%20jira"
    },
    {
        "role": "assistant",
        "content": "Yes \u2014 there *are* desktop app options for Jira, but it's a bit nuanced. Here\u2019s what you should know as of **August 3, 2026**:\n\n---\n\n### \ud83c\udfe2 Official Atlassian Options\n\n- **Mac (Jira Cloud)**  \n  Atlassian offers a *native Mac app* for Jira Cloud, which included better integration with macOS features like notifications, dark mode, etc. ([wac-cdn.atlassian.com](https://wac-cdn.atlassian.com/dam/jcr%3Aa8444f9f-fb21-4737-ba71-7d2c8c14d57a/Differentiator-ebook?utm_source=openai))\n\n- **Windows / Mac (Desktop Connector / \u201cDesktop App for Jira\u201d)**  \n  There are third-party Marketplace apps (created by partners, not by Atlassian itself) like **Desktop Connector for Jira** by Infosysta. These provide desktop-style Jira access, desktop notifications, issue tracking, dashboards, multiple instance switching, etc. They aim to let you work *outside* your browser. ([marketplace.atlassian.com](https://marketplace.atlassian.com/apps/1232960/desktop-connector-for-jira-windows-and-mac?utm_source=openai))\n\n---\n\n### \u26a0\ufe0f What\u2019s Not (Or Was Discontinued)\n\n- Atlassian previously had an official desktop application for Mac, but it has been **sunsetted/discontinued** ([community.atlassian.com](https://community.atlassian.com/t5/Jira-questions/Is-there-a-desktop-app-for-Jira-Work-Management-instance/qaq-p/2358574?utm_source=openai)).\n\n- There is *no official Atlassian desktop app for Windows* provided by Atlassian itself (currently) ([community.atlassian.com](https://community.atlassian.com/forums/Jira-questions/Is-there-a-software-on-windows/qaq-p/1199665?utm_source=openai)).\n\n---\n\n### \ud83d\udd0d Community / Open-Source Solutions\n\n- There are open-source desktop clients (built with frameworks like Electron) made by the community. These aren\u2019t official, so feature support, security, and maintenance might vary. For example, one user shared they built a cross-platform \u201cJira Desktop\u201d client. ([reddit.com](https://www.reddit.com/r/opensource/comments/1sdzrw5/i_built_a_dedicated_jira_desktop_client_for_mac/?utm_source=openai))\n\n---\n\nIf you tell me whether you use **Cloud vs Data Center / Server** or **Mac vs Windows**, I can recommend the best desktop app option for your setup."
    },
    {
        "role": "user",
        "content": "I%20am%20using%20windows%2C%20it%20is%20for%20work%2C%20I%20need%20it%20to%20be%20screen%20reader%20accessible."
    },
    {
        "role": "assistant",
        "content": "Using Windows for work and needing screen-reader accessibility definitely shapes what Jira setup is going to work best. Here\u2019s what I found, and some suggestions based on your needs:\n\n---\n\n## \ud83d\udd0e What Atlassian Offers (Officially)\n\n- As of now, **there is no official Atlassian desktop app for Jira on Windows**. Atlassian withdrawn its native Mac app, and there are no parallel desktop builds supported by Atlassian for Windows. Much of Jira\u2019s strength lies in its web-based experience.  \n- The web version *does* have tested support for screen readers and accessibility features. Atlassian publishes a **VPAT (Voluntary Product Accessibility Template)** for Jira Software Cloud, which documents some compliance with accessibility standards (WCAG, etc.), but also lists limitations \u2014 things like missing alternative text, controls not always being keyboard-accessible, tooltips inaccessible to screen readers, etc. ([atlassian.com](https://www.atlassian.com/dam/jcr%3Acd90cf70-99d8-4d1c-ad8c-07b6748a8102/Atlassian%20Jira%20Software%20Cloud%20VPAT.pdf?utm_source=openai))\n\n---\n\n## \u2699\ufe0f Important Constraints on Accessibility\n\nFrom the VPAT and other official sources:\n\n- Some parts of Jira\u2019s web interface are **not fully keyboard-navigable** (especially the Rich Text Editor and custom controls). ([atlassian.com](https://www.atlassian.com/dam/jcr%3Acd90cf70-99d8-4d1c-ad8c-07b6748a8102/Atlassian%20Jira%20Software%20Cloud%20VPAT.pdf?utm_source=openai))  \n- Many images/icons are used as CSS background images, which can\u2019t be read by high-contrast modes or screen readers properly. ([atlassian.com](https://www.atlassian.com/dam/jcr%3Acd90cf70-99d8-4d1c-ad8c-07b6748a8102/Atlassian%20Jira%20Software%20Cloud%20VPAT.pdf?utm_source=openai))  \n- Tooltips and some hover\u2010based UI cues aren\u2019t always exposed to screen readers. ([atlassian.com](https://www.atlassian.com/dam/jcr%3Acd90cf70-99d8-4d1c-ad8c-07b6748a8102/Atlassian%20Jira%20Software%20Cloud%20VPAT.pdf?utm_source=openai))  \n\nSo even in the browser, there can be gaps.\n\n---\n\n## \ud83e\uddf0 Possible Workarounds & Third-Party Tools\n\nGiven those limitations, here are some ways you might get a more accessible experience on Windows:\n\n1. **Using the Web App + Accessibility Enhancements**\n   - Use the web interface with modern browsers like Chrome, Edge, or Firefox. They have many built-in accessibility features.\n   - Pair with a good screen reader: **JAWS** and **NVDA** are among the most used on Windows. ([en.wikipedia.org](https://en.wikipedia.org/wiki/JAWS_%28screen_reader%29?utm_source=openai))\n   - Use high contrast mode, magnification, custom styling etc.\n\n2. **\u201cUnstoppable for Jira\u201d**\n   - This is a plugin / app available via Jira Marketplace that enhances accessibility in Jira instances (Server or Data Center). It improves **ARIA labels**, landmarks, keyboard navigation, high contrast mode, etc. It reports compatibility with **NVDA**, **JAWS**, and **VoiceOver**. ([marketplace.atlassian.com](https://marketplace.atlassian.com/apps/1214187/unstoppable-for-jira?hosting=datacenter&tab=overview&utm_source=openai))  \n   - If your organization uses Jira Server or Data Center, this could *substantially improve* screen reader usability.\n\n3. **Unofficial Desktop Wrappers**\n   - \u201cJira Desktop Unofficial (JDU)\u201d is a lightweight wrapper that turns your Jira Cloud site into something resembling a desktop app using Microsoft Edge\u2019s WebView2. However, **because it's just wrapping the web client**, all the same accessibility limitations from the web version will generally still apply. ([sourceforge.net](https://sourceforge.net/projects/jira-desktop-unofficial/?utm_source=openai))  \n   - Since this is community\u2010driven, support for screen readers is not guaranteed, and may lag behind web version updates.\n\n---\n\n## \u2705 What I\u2019d Recommend\n\nGiven you\u2019re using Windows, it\u2019s for work, and screen\u2010reader accessibility is essential:\n\n| Option | Pros | Cons |\n|---|---|---|\n| Stick with the **web version** + screen reader (NVDA or JAWS) + accessibility settings | It\u2019s official and fully supported; you get latest features & security; screen readers and browsers are well integrated | Some UI elements incomplete in accessibility; some menus, icons, tooltips may be harder to use |\n| Install **Unstoppable for Jira** (if your Jira is Server or Data Center) | Enhances keyboard navigation, improves labels, helps compliance, works with major screen readers ([marketplace.atlassian.com](https://marketplace.atlassian.com/apps/1214187/unstoppable-for-jira?hosting=datacenter&tab=overview&utm_source=openai)) | If your organization doesn\u2019t run Server or Data Center, you can\u2019t use it; might require IT/admin permissions |\n| Try an **unofficial desktop wrapper** like JDU | More focused window, fewer browser distractions | Not officially supported; same accessibility gaps as the web; possible incompatibilities or delays in updates |\n\n---\n\nIf you tell me which **screen reader** you\u2019ll be using (e.g. JAWS, NVDA, Narrator), and whether your Jira instance is **Cloud** or **Server/Data Center**, I can recommend a more tailored setup (and share specific tips for your screen reader to make Jira more usable)."
    },
    {
        "role": "user",
        "content": "I%20am%20using%20jaws%2C%20it%20is%20not%20always%20the%20accessibility%20that%20is%20a%20problem%2C%20it%20is%20so%20hard%20to%20use.%20I%20lose%20my%20orientation%2C%20can%27t%20easily%20find%20info%20I%20need%2C%20it%20takes%20an%20hour%20to%20do%20what%20people%20do%20in%20minutes."
    },
    {
        "role": "assistant",
        "content": "I\u2019m sorry to hear how frustrating using Jira with JAWS has been. Losing orientation or taking much longer than others is a common challenge. I looked up how Jira currently works, what the obstacles are, and some tips you (or your team) could try to make things more usable. Here\u2019s a breakdown with actionable steps to make your workflow smoother:\n\n---\n\n## \ud83d\udd0d What Jira\u2019s Accessibility Looks Like (with JAWS)\n\nFrom Atlassian\u2019s VPAT and others:\n\n- The **rich text editor (RTE)** in Jira has many controls \u2014 toolbars, emojis, drop-down pickers \u2014 that are not reliably keyboard accessible, whose buttons don\u2019t always get announced properly by screen readers. ([atlassian.com](https://www.atlassian.com/dam/jcr%3Acd90cf70-99d8-4d1c-ad8c-07b6748a8102/Atlassian%20Jira%20Software%20Cloud%20VPAT.pdf?utm_source=openai))  \n- Some UI elements (icons, placeholders, breadcrumbs) are poorly marked up or not marked at all, so JAWS can\u2019t always read out what they are or what state they\u2019re in. ([ucl.ac.uk](https://www.ucl.ac.uk/accessibility/digital-accessibility-statements/jira-accessibility-statement?utm_source=openai))  \n- Tooltips, popup content, and some dropdowns aren\u2019t announced or accessible. Some content is only triggered on hover, which is very problematic when using screen readers. ([atlassian.com](https://www.atlassian.com/dam/jcr%3Acd90cf70-99d8-4d1c-ad8c-07b6748a8102/Atlassian%20Jira%20Software%20Cloud%20VPAT.pdf?utm_source=openai))  \n- Zoom, contrast, and content reflow issues remain \u2014 when you scale the page up or use high contrast modes, some text or layout breaks, which can disorient you. ([ucl.ac.uk](https://www.ucl.ac.uk/accessibility/digital-accessibility-statements/jira-accessibility-statement?utm_source=openai))  \n\nThese all contribute to losing track of \u201cwhere you are\u201d in the app, spending extra time finding commands, etc.\n\n---\n\n## \u2705 Shortcuts & Keyboard Navigation: Key Tools You May Not Be Using (that Help a Lot)\n\nLearning and using keyboard shortcuts in Jira can dramatically reduce how much time you spend moving around and hunting for what you need. Atlassian has put together fairly comprehensive lists. Here are some that may help with orientation and faster navigation:\n\n| Shortcut / Command | What It Does | Why It Helps When Using JAWS |\n|--------------------|---------------|-------------------------------|\n| `?` (Shift + `/`) | Opens the full keyboard shortcut guide ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) | You can pull this up any time, learn new shortcuts, refresh what keys do what without needing a mouse. |\n| `c` | Create a work item / issue ([tutorialtactic.com](https://tutorialtactic.com/blog/atlassian-jira-agile-shortcuts/?utm_source=openai)) | If starting a task is common, you won\u2019t have to navigate menus. |\n| `/` | Quick Search or jump into search field ([tutorialtactic.com](https://tutorialtactic.com/blog/atlassian-jira-agile-shortcuts/?utm_source=openai)) | Find issues/projects/boards by name fast, rather than navigating step by step. |\n| `g` then `d` / `g` then `p` / `g` then `i` | \u201cGo to Dashboard\u201d, \u201cBrowse Projects\u201d, \u201cGo to Issues\u201d ([product-downloads.atlassian.com](https://product-downloads.atlassian.com/software/jira/downloads/documentation/JIRA%204.3%20Documentation%20%28PDF%29%2020110328.pdf?utm_source=openai)) | Helps you go directly to big areas instead of moving through many UI layers. |\n| `j` / `k` | Move up/down between issues in lists or boards ([tutorialtactic.com](https://tutorialtactic.com/blog/atlassian-jira-agile-shortcuts/?utm_source=openai)) | Keeps you oriented in a list without scrolling or hunting. |\n| `n` / `p` | Move next / previous columns in boards ([confluence.atlassian.com](https://confluence.atlassian.com/jirasoftware/blog/2015/12/4-essential-jira-software-keyboard-shortcuts?utm_source=openai)) | If you use boards, helps you shift context (from \u201cTo Do\u201d to \u201cIn Progress\u201d, etc.) via keyboard. |\n| `Ctrl + K` (Windows) | Opens the **command palette** \u2014 lets you type what you need (issues, projects, actions) rather than browsing menus ([community.atlassian.com](https://community.atlassian.com/learning/lesson/explore-jira-commands-and-shortcuts?utm_source=openai)) | Extremely useful for jumping to sections or actions quickly. |\n\n---\n\n## \ud83d\udee0 Tips & Techniques to Help Keep Your Place\n\nBeyond shortcuts, here are strategies that can make your experience smoother and help preserve orientation:\n\n1. **Use page landmarks / heading navigation:**  \n   - Make a habit of using JAWS commands to jump by **headings** or **landmarks** (\u201cnavigation regions\u201d). If you know you're looking for something in the sidebar or header, use those navigation commands. This helps you keep \u201cwhere you are\u201d in mind.  \n   - Encourage your team/admins to structure Jira instance pages with proper headings and ARIA landmarks (if possible \u2014 improvements have been in progress in newer versions). ([developer.atlassian.com](https://developer.atlassian.com/server/jira/platform/designing-for-the-jira-project-centric-view/?utm_source=openai))\n\n2. **Turn off unnecessary panes or menus:**  \n   If the sidebar or certain panels are collapsing or having extra options that aren\u2019t relevant to your job, collapsing them (if possible) or avoiding infrequently used parts might reduce clutter.\n\n3. **Work in \u201clist view\u201d where possible:**  \n   When you're dealing with many issues, switch to a list that you can tab through, use arrow keys, home/end, page up/down to move efficiently. The fewer columns and less visual clutter, the better. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/navigate-all-work-with-your-keyboard/?utm_source=openai))\n\n4. **Practice navigating with the keyboard only:**  \n   Try sessions where you intentionally don\u2019t use the mouse \u2014 force yourself to do everything via keyboard + screen reader. This builds muscle memory: you\u2019ll remember that after you hit \u201cg\u201d, \u201ci\u201d is issues, or \u201cc\u201d is create. Muscle memory *really* speeds things up.\n\n5. **Custom bookmarks / pinned pages:**  \n   If there are certain views you return to often (your team\u2019s board, your filters, your backlog), save links to those so you can open them directly \u2014 less navigation to recreate your path each time.\n\n---\n\n## \ud83d\udce3 What You or Your Team Could Ask or Push For\n\nSince some of the barriers are structural, it may require changes from your team or Atlassian to improve:\n\n- Request (from admins) **accessibility fixes** via Jira\u2019s support or accessibility team, especially for specific things that block you (e.g. tooltips, rich editors, modals). Atlassian tracks tickets for accessibility and often offers updates.  \n- Ask if \u201cUnstoppable for Jira\u201d or similar accessibility-enhancing plugins can be installed (if your instance supports it) to improve markup, labels, navigation.  \n- If your instance has configurable navigation like the \u201cproject-centric view\u201d (newer layout), see if that can help simplify context: fewer menus, more predictable sidebar links. ([developer.atlassian.com](https://developer.atlassian.com/server/jira/platform/designing-for-the-jira-project-centric-view/?utm_source=openai))\n\n---\n\nIf you like, I can build you a **custom Cheat Sheet** of the *most useful shortcuts in Jira for JAWS users* (the ones that give big improvement in orientation + speed), so you can start with maybe 5-10 keys that really help. Do you want me to put that together for you?"
    }
]