Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA not reading Jira Servivce Managament as expected #17311

Open
EneyeAttah opened this issue Oct 20, 2024 · 7 comments
Open

NVDA not reading Jira Servivce Managament as expected #17311

EneyeAttah opened this issue Oct 20, 2024 · 7 comments

Comments

@EneyeAttah
Copy link

Steps to reproduce:

1.Navigate to Jira Service Management using NVDA reader
2.While using the down and up arrow keys, NVDA reads multiple lines on the Jira Service Management as one word ( document link )

Actual behavior:

Nvda does not read each line one after the other on the Jira Console but reads multiple lines as one

Expected behavior:

NVDA should reach each line one after the other as it is read by Jawa

NVDA logs, crash dumps and other attachments:

None

System configuration

NVDA installed/portable/running from source:

NVDA Installed

NVDA version:

2024.3.1 (2024.3.1.33894)

Windows version:

Windows 11 Pro Version 22H2 dev ( build 22621.4317)

Name and version of other software in use when reproducing the issue:

Jira Service Management

Other information about your system:

Jira Service Management is used for team collaboration in tracking and resolving customer's request

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Same behavior with earlier version.

If NVDA add-ons are disabled, is your problem still occurring?

NA

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

NA

@Adriani90
Copy link
Collaborator

Is this a web based application? In which browser and which version did you encounter this issue? Have you tried to disable screen layout in NVDA? You can do that by pressing insert key or nvda key + v.

@EneyeAttah
Copy link
Author

EneyeAttah commented Oct 20, 2024 via email

@seanbudd
Copy link
Member

Welcome @EneyeAttah,

We are unable to process this issue as it stands.

  • This seems like intended behaviour where all the contents are accessible. Can you confirm that the issue is a difference in UX in reading this information, rather than the information being inaccessible?
  • To be able to reproduce this issue, we need a code sample. Provide a minimal HTML sample to reproduce this using codepen.
  • This is very likely a problem with the implementation of the application/website, as a starting point please submit feedback to the authors to let them know about the problem.

Kind Regards,
NV Access Software Developers

@Qchristensen
Copy link
Member

Follow up from user via Eneye - this issue has been reported to Jira as well and their issue is: https://jira.atlassian.com/browse/JSDSERVER-15632

There is also a note on THAT issue from another user that "This also prevents NVDA's search function from finding any values inside the custom field list." (which I thought was worthwhile recording here as well).

@Adriani90
Copy link
Collaborator

The referenced Jira issue talks about a different thing, namely that the custom fields are added with role=application to the website and therefore they are not navigable in browse mode. This is a different issue and NVDA cannot do anything about it, the JIRA developers could add role=document to them instead of role=application, then the user would see them in the virtual document as well ass far as I understand. This would also allow NVDA's find functionality to work as expected.

@Adriani90
Copy link
Collaborator

Regarding this particular issue, we will not be able to investigate without a minimal test case I guess. I created a Jira account and created a new project, but I don't know how to reproduce this exactly. The custom controls you can add as fields are basically same things like adaptive cards in Microsoft teams, but if they don't have the right HTML and aria attributes, NVDA will not be able to handle them in an accessible way. So this issue is probably related to web authoring rather than NVDA doing something wrong here.
@EneyeAttah please try to get a minimal test case from the custom field that shows this problem, in an isolated HTML snippet from the Atlassian developers, then we can investigate further within the community whether this is a NVDA issue or not.

Did the user try the screen layout setting turned off? Maybe it helped already.

@EneyeAttah
Copy link
Author

EneyeAttah commented Oct 23, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants