Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-21725

'Comment hover-over' prevents screen reading applications used by visually impaired from identifying available operations

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      From the support request:

      We have several blind users who use screen reading software in order to use JIRA. The new JIRA 4.1.1 has an issue where the screen reading software cannot "see" the edit comment hover item. Do you know if you can disable the hover over and make the edit link stay....I assume if it stays as a link the screen reader will be able to read it.

            [JRASERVER-21725] 'Comment hover-over' prevents screen reading applications used by visually impaired from identifying available operations

            Matthew Brennan made changes -
            Labels Original: accessibility affects-server ax-qa New: accessibility affects-server
            Matthew Brennan made changes -
            Labels Original: accessibility affects-server New: accessibility affects-server ax-qa
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3050455 ] New: JAC Suggestion Workflow 3 [ 3681726 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2611900 ] New: JAC Suggestion Workflow [ 3050455 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2572786 ] New: Confluence Workflow - Public Facing v4 [ 2611900 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2354001 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2572786 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2121324 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2354001 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2082476 ] New: JIRA Bug Workflow w Kanban v6 [ 2121324 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 887974 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2082476 ]
            jonah (Inactive) made changes -
            Description Original: From the support request:
            {quote}
            We have several blind users who use screen reading software in order to use JIRA. The new JIRA 4.1.1 has an issue where the screen reading software cannot "see" the edit comment hover item. Do you know if you can disable the hover over and make the edit link stay....I assume if it stays as a link the screen reader will be able to read it.
            {quote}             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-21725].
              {panel}

            From the support request:
            {quote}
            We have several blind users who use screen reading software in order to use JIRA. The new JIRA 4.1.1 has an issue where the screen reading software cannot "see" the edit comment hover item. Do you know if you can disable the hover over and make the edit link stay....I assume if it stays as a link the screen reader will be able to read it.
            {quote}

              Unassigned Unassigned
              bdziedzic Bogdan Dziedzic [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: