[
    {
        "role": "user",
        "content": "Help%20me%20with%20efficient%20jira%20access%20using%20jaws%20screen%20reader"
    },
    {
        "role": "assistant",
        "content": "Here are some tips and techniques to help you use **Jira** more efficiently with **JAWS** screen reader. These are drawn both from Atlassian\u2019s docs and from first-hand user experience. If you tell me whether you use Jira Cloud, Server/Data Center, or Service Management, I can adjust for your version.\n\n---\n\n## \u2705 What Atlassian Supports\n\n- Jira Cloud supports JAWS + Chrome as a recommended setup for screen reader users. ([atlassian.com](https://www.atlassian.com/accessibility?utm_source=openai))  \n- Accessibility features include keyboard-navigable UI, screen reader support, color contrast control, and global preview panels for referenced content. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/view-content-in-a-side-panel/?utm_source=openai))  \n- Jira has a full list of keyboard shortcuts (for navigation, issue actions, etc.) you can pull up by pressing `?` (Shift + /) from anywhere in Jira. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai))  \n\n---\n\n## \ud83d\udd0d JAWS-Specific Shortcuts & Modes\n\nTo use Jira efficiently, you\u2019ll need to get comfortable with these JAWS basics:\n\n| Action | Shortcut | What it does |\n|---|---|---|\n| Say all content from current point (\u201ccontinuous reading\u201d) | JAWS key + Down arrow | Starts reading text continuously from where your cursor is. ([srt.csb-cde.ca.gov](https://srt.csb-cde.ca.gov/jaws/jaws-keyboard.html?utm_source=openai)) |\n| Read current line | JAWS key + Up arrow | Speaks the line of text you\u2019re on. ([unimelb.edu.au](https://www.unimelb.edu.au/accessibility/tools/testing-web-pages-with-jaws?utm_source=openai)) |\n| Navigate between headings | `H` for next heading, `Shift + H` for previous | Skips by headings, great for jumping to sections like \u201cActivity\u201d or \u201cComments\u201d in a Jira ticket. ([webaim.org](https://webaim.org/articles/jaws/?utm_source=openai)) |\n| Navigate through regions/landmarks / lists / forms / tables | `R`, `L`, `F`, `T` etc. with `Shift` combinations | Lets you focus on specific types of elements like forms or lists. Useful for finding issue fields, comments, labels. ([nlm.nih.gov](https://www.nlm.nih.gov/oet/ed/cidi/ScreenReader_Overview.pdf?utm_source=openai)) |\n\n> Note: \u201cJAWS key\u201d is Insert by default; on laptop layout or by user choice can be Caps Lock. ([unimelb.edu.au](https://www.unimelb.edu.au/accessibility/tools/testing-web-pages-with-jaws?utm_source=openai))\n\n---\n\n## \ud83d\udee0 Using Jira More Efficiently with JAWS\n\nHere are workflows and tips applied specifically to Jira:\n\n1. **Switch to List View for Issue Browsing**  \n   If you're scanning through many issues, list view (instead of boards) tends to be more compact and accessible. The layout is simpler, making it easier for screen readers. Many users report better performance and fewer distractions this way. ([knappstrategic.com](https://www.knappstrategic.com/accessiversity-blog/a-jaws-screen-reader-users-guide-to-jira?utm_source=openai))\n\n2. **Use Headings to Jump to Key Sections in a Ticket**  \n   Once an issue is open, use `H` until you hit the \u201cActivity\u201d heading to find comments, updates, status changes. If you miss it, `Shift + H` will go backwards. This helps jump past metadata, attachments, etc. ([knappstrategic.com](https://www.knappstrategic.com/accessiversity-blog/a-jaws-screen-reader-users-guide-to-jira?utm_source=openai))\n\n3. **Label Editing & Status Changes**  \n   To add or modify labels: find the label field via arrow or tab navigation (sometimes via heading + moving across tabs). The Knapp guide shows how to use the label field by issuing the JAWS pass-through (Insert + 3 by default), pressing `L` to edit, then typing and Enter. ([knappstrategic.com](https://www.knappstrategic.com/accessiversity-blog/a-jaws-screen-reader-users-guide-to-jira?utm_source=openai))  \n\n4. **Changing Issue Status**  \n   From \u201cActivity\u201d section, navigate down (arrow keys) to the status field (\u201cChange Status\u201d button), activate it (Enter), pick the status (arrow down, Enter). This avoids using mouse. ([knappstrategic.com](https://www.knappstrategic.com/accessiversity-blog/a-jaws-screen-reader-users-guide-to-jira?utm_source=openai))  \n\n5. **Use Jira Keyboard Shortcuts**  \n   - Press `C` to create a new issue.  \n   - `O` to open selected issue.  \n   - `A` to assign the issue.  \n   - `I` to assign to yourself.  \n   - `M` to add or open comment input.  \n   - `J` / `K` to move down / up in lists.  \n   - `N` / `P` to move between columns on boards or Kanban boards.\n\n   These are global or nearly-global in Jira Cloud and work well with JAWS once focus is in the Jira page. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai))  \n\n6. **Using Global Preview Panels (for linked content)**  \n   When Jira or Confluence references content or related items, global preview panels allow reading/editing without losing your place. These panels are keyboard-navigable and screen reader accessible. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/view-content-in-a-side-panel/?utm_source=openai))  \n\n---\n\n## \u2699\ufe0f Settings & Customization Tips\n\n- **JAWS Layout**: Set your JAWS modifier key to Caps Lock (if using desktop layout), which is more reachable. ([unimelb.edu.au](https://www.unimelb.edu.au/accessibility/tools/testing-web-pages-with-jaws?utm_source=openai))  \n- **Turn On Accessible View in Browsers**: Use Chrome with the latest version, as Atlassian has tested and recommends that with JAWS. ([atlassian.com](https://www.atlassian.com/accessibility?utm_source=openai))  \n- **Enable Keyboard Shortcuts Inside Jira**, and make sure they\u2019re not disabled in your profile. The keyboard shortcuts dialog allows toggling them. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai))  \n- **High Contrast**: If you struggle with color or contrast, Jira and Atlassian offer themes or modes (or apps) for high contrast which help in combination with screen readers. While a built-in high-contrast mode is rarely perfect, combining with browser extensions or Jira marketplace add-ons helps.  \n\n---\n\nIf you tell me which version of Jira you use (Cloud vs Server or Data Center, what interface you mostly use: boards, backlog, lists), I can give you some **custom workflows or scripts** to save you even more effort."
    },
    {
        "role": "user",
        "content": "We%20use%20jira%20cloud.%20I%20am%20using%20jaws%202026.%20Mostly%20use%20boards%2C%20lists%2C%20we%20track%20and%20report%20issues%20and%20I%20need%20to%20create%20and%20navigate%20tickets."
    },
    {
        "role": "assistant",
        "content": "Here are more targeted tips to help you work efficiently in **Jira Cloud** with **JAWS 2026**, especially since you often use boards, lists, and need to navigate tickets and create issues. I\u2019ll also include keyboard shortcuts that are helpful for your workflows, and point out some known and current accessibility gaps so you know what to expect.\n\n---\n\n## \ud83c\udfaf Essential Keyboard Shortcuts in Jira Cloud\n\nThese allow you to create, navigate, and edit issues, and move around boards and lists without leaving the keyboard. You can pull up the full list at any time by pressing `?` (Shift + /). ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai))\n\n| Action | Shortcut |\n|---|---|\n| View keyboard shortcuts help | `?` (Shift + /) ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Create a new issue / work item | `C` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Open selected issue | `O` or `Enter` when in focus on an issue ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Assign to someone | `A` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Assign to yourself | `I` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Add comment | `M` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Edit issue (fields etc.) | `E` ([standards.atlassian.net](https://standards.atlassian.net/secure/ViewKeyboardShortcuts%21default.jspa?utm_source=openai)) |\n| Comment on issue | `M` ([standards.atlassian.net](https://standards.atlassian.net/secure/ViewKeyboardShortcuts%21default.jspa?utm_source=openai)) |\n| Edit labels | `L` ([standards.atlassian.net](https://standards.atlassian.net/secure/ViewKeyboardShortcuts%21default.jspa?utm_source=openai)) |\n| Move down a list or backlog (next item) | `J` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Move up a list | `K` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Move to next column (on board) | `N` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Move to previous column | `P` ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/use-keyboard-shortcuts/?utm_source=openai)) |\n| Quick search (global) | `/` ([standards.atlassian.net](https://standards.atlassian.net/secure/ViewKeyboardShortcuts%21default.jspa?utm_source=openai)) |\n| Go to dashboard | `g` then `d` ([standards.atlassian.net](https://standards.atlassian.net/secure/ViewKeyboardShortcuts%21default.jspa?utm_source=openai)) |\n| Go to projects list | `g` then `p` ([standards.atlassian.net](https://standards.atlassian.net/secure/ViewKeyboardShortcuts%21default.jspa?utm_source=openai)) |\n| Find issues | `g` then `i` ([standards.atlassian.net](https://standards.atlassian.net/secure/ViewKeyboardShortcuts%21default.jspa?utm_source=openai)) |\n\n---\n\n## \ud83e\udded Navigating Boards and Lists with JAWS\n\nUsing boards and lists tends to be more screen reader-friendly than more graphical or heavily custom layouts, but some quirks remain. Here are workflows and navigation tips:\n\n- **Customize board view** to reduce clutter. Toggle off non-essential fields on cards, use quick filters, collapse or expand swimlanes. That way you have fewer items to scan through. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/customize-your-view-of-the-board-and-backlog/?utm_source=openai))  \n- **Use full screen mode** on boards and backlogs to hide sidebars and navigation menus. Focus stays more on the issue cards or backlog items. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/customize-your-view-of-the-board-and-backlog/?utm_source=openai))  \n- **Open work items in a sidebar** if possible (via \u201cView settings\u201d) rather than a full overlay dialog, so you don\u2019t lose keyboard focus away from the board/list. This setting helps you read issue details without losing where you were. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/customize-your-view-of-the-board-and-backlog/?utm_source=openai))  \n- **Use global preview panels**: when you have linked content like another issue or a Confluence page, open in a side panel so you don\u2019t need to navigate away. It is keyboard-navigable and works with screen readers. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/view-content-in-a-side-panel/?utm_source=openai))\n\n---\n\n## \ud83d\udee0 Creating and Working with Tickets (Issues)\n\nHere are steps mapped to keyboard + JAWS workflows:\n\n1. **Create a new issue**  \n   Press `C`. This opens the issue creation dialog. JAWS should read field labels\u2014double-check that \u201cIssue Type,\u201d \u201cSummary,\u201d \u201cDescription,\u201d \u201cAssignee,\u201d etc., are properly associated fields. You may need to use forms mode in JAWS when typing in fields.  \n\n2. **Fill required fields**  \n   Use tab to navigate fields. If a field lacks tooltips or labels, JAWS might skip some info\u2014slow down or arrow-through to ensure context.  \n\n3. **Submit issue**  \n   After filling the fields, tab to the \u201cCreate\u201d button and press Enter. Alternatively, some dialogs allow pressing Ctrl + Enter (or similar, depending on configuration).  \n\n4. **Open an issue from a board or list**  \n   Navigate via arrow/tab to the issue title, then press `O` or Enter to open. If using the sidebar setting, it will appear there. JAWS will read out the issue\u2019s content including metadata, description, comments.  \n\n5. **Edit issue fields**  \n   Once an issue is open, press `E` to edit. Then use tab to locate specific fields. Use JAWS forms mode in input fields.  \n\n6. **Change status / transition issue**  \n   After opening the issue, navigate to the \u201cStatus\u201d field (\u201cTransition\u201d or \u201cChange status\u201d button). Use Enter to open the status picker, arrow keys to select, Enter to confirm.  \n\n7. **Comment**  \n   Press `M` when focused on an issue to open comment field. Tab to comment area, type, then tab to submit.  \n\n---\n\n## \u26a0\ufe0f Known Accessibility Gaps & How to Mitigate\n\nIt helps to know what things may not work quite smoothly yet so you can plan accordingly and report issues when needed:\n\n- Some form fields or buttons don\u2019t have properly associated labels, so JAWS may not always announce what a field is for immediately. ([ucl.ac.uk](https://www.ucl.ac.uk/accessibility/digital-accessibility-statements/jira-accessibility-statement?utm_source=openai))  \n- Some elements show error messages only visually or on hover/focus but are **not** programmatically announced, so screen reader users sometimes miss validation or required field cues. ([ucl.ac.uk](https://www.ucl.ac.uk/accessibility/digital-accessibility-statements/jira-accessibility-statement?utm_source=openai))  \n- Rich Text Editors (for descriptions, comments) have elements/buttons that might not be fully accessible via keyboard or with screen reader cues. Toggling formatting etc. may be tricky. ([atlassian.com](https://www.atlassian.com/dam/jcr%3Acd90cf70-99d8-4d1c-ad8c-07b6748a8102/Atlassian%20Jira%20Software%20Cloud%20VPAT.pdf?utm_source=openai))  \n- Overly complex boards or large numbers of items can cause screen reader focus to shift unexpectedly (especially with virtualized rendering). Keeping boards simpler helps. ([kb.wisc.edu](https://kb.wisc.edu/accessibility//127136?utm_source=openai))  \n\n---\n\nLet me know if you want workflows or shortcut sets specific to your **board type** (Kanban vs Scrum), or **filtered lists** you use for reporting\u2014I can tailor shortcuts and navigation tips for those too."
    },
    {
        "role": "user",
        "content": "We%20use%20the%20canban%20board.%20Alos%20is%20there%20a%20faster%20way%20to%20change%20the%20status%20of%20an%20issue%2C%20it%20is%20har%20to%20find%20that%20by%20tabbingand%20arrowing%20through"
    },
    {
        "role": "assistant",
        "content": "Yes\u2014you *can* change the status of an issue more quickly in Jira Cloud using the **Command Palette**, which often works better than trying to tab and arrow through a bunch of fields, especially with JAWS. Here\u2019s how to use it effectively in your Kanban workflow, plus some suggestions to improve efficiency.\n\n---\n\n## \u26a1 Changing Issue Status with the Command Palette\n\nThe Command Palette is really useful to perform actions without navigating deeply by tabbing. Here\u2019s how to use it:\n\n1. Open the issue you want to change status for. It can be via a sidebar or in full view. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/change-the-status-of-an-issue-with-your-keyboard/?utm_source=openai))  \n2. Press **Ctrl + K** (Windows) to open the Command Palette. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/what-is-the-command-palette/?utm_source=openai))  \n3. Type **\u201cChange status\u201d** in the palette. You can also type parts of the status name (like \u201cIn progress,\u201d \u201cDone,\u201d etc.). ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/change-the-status-of-an-issue-with-your-keyboard/?utm_source=openai))  \n4. Select the new status from the results and confirm with Enter. If there are required fields or conditions (in your workflow) you\u2019ll be prompted to fill or approve them. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/transition-an-issue/?utm_source=openai))  \n\nThis bypasses having to find the \u201cStatus\u201d menu via multiple tabs/arrow keys, which can be difficult with a screen reader.\n\n---\n\n## \ud83c\udf9b Keyboard Shortcuts & Other Fast Paths\n\nHere are some direct keyboard or board-based options:\n\n- **Drag-and-drop columns**: On Kanban boards, you can also move a card between columns to change its status. For sighted users that requires mouse, but sometimes keyboard-accessible controls or app extensions might support similar behavior. ([support.atlassian.com](https://support.atlassian.com/jira-software-cloud/docs/transition-an-issue/?utm_source=openai))  \n- **Work item actions in the issue view**: Once an issue is open, some workflows include buttons or actions (especially in the header of the issue) for transitions like \u201cStart Progress,\u201d \u201cResolve,\u201d or \u201cClose.\u201d Using Shift + Tab to go back toward the top of the issue might get you there faster. But this still might require visual navigation, depending on how your Jira is set up.  \n\n---\n\n## \ud83d\udd27 Tips for Better Efficiency With JAWS\n\nHere are ways to make the above paths smoother and more reliable when using JAWS:\n\n- **Use the Command Palette often**: Since you can access many actions including status transitions from it, it\u2019s faster than navigating UI elements that aren\u2019t always accessible or in expected places.  \n- **Train on status names**: If you know your workflow status names (\u201cTo Do,\u201d \u201cIn Progress,\u201d \u201cReview,\u201d \u201cDone,\u201d etc.), you can type them directly in the Command Palette once you press Ctrl + K. That speeds selection.  \n- **Customize the workflow (if possible)**: If your Jira permissions allow, having fewer statuses per column or clearer labels can reduce confusion. Also, ensure mandatory fields for status transitions are clearly labeled so JAWS can announce them.  \n- **Use simpler board setups**: Fewer columns and less complexity help reduce the number of UI elements you need to skip through.  \n- **Feedback & tweaks**: If certain status buttons are hard to reach (missing labels, hard to tab into), file accessibility feedback with your Jira Admin or Atlassian Support. Sometimes UI items are not properly coded for screen readers.\n\n---\n\n## \ud83e\udde9 What to Do Next\n\nIf you want, I can walk you through setting up some custom keyboard mappings or browser userscripts / extensions that make status buttons immediately reachable (for example, putting a status changer at top of issue that\u2019s consistently accessible via keyboard and announced by JAWS). Would you like me to show you how to do that?"
    }
]