DT-2039: associated labels for accessibility compliance

[brack2891]

Addresses

---

https://broadworkbench.atlassian.net/browse/DT-2039

Summary

---

Adding proper clarity to speak to text option within: Research Console, Data Library, and Profile

---

Have you read Terra's Contributing Guide lately? If not, do that first.

• Label PR with a Jira ticket number and include a link to the ticket
• Label PR with a security risk modifier [no, low, medium, high]
• PR describes scope of changes
• Get a minimum of one thumbs worth of review, preferably two if enough team members are available
• Get PO sign-off for all non-trivial UI or workflow changes
• Verify all tests go green
• Test this change deployed correctly and works on dev environment after deployment

[eweitz]

Kudos on your first DUOS PR!

Code looks generally good, but the duplicate config.json and linting issues seem worth fixing. FWIW, I often run npx eslint before pushing to surface formatting issues locally.

[rushtong]

Nice work! Let us know if you need help addressing the lint warnings.

[rushtong]

Thank you for the updates. I do see that some of the original feedback has not been applied yet:

1. Changes to base_config.json should be reverted
2. PaginatorBar.jsx should be deleted

[rushtong]

See comment inline. It is preferable not to change the layout in any way.

[fboulnois]

See below:

[rushtong]

This PR seems to have been reduced in scope significantly to the point that removing PaginatorBar.jsx is pretty unrelated to the ticket and the PR. I would suggest moving this file deletion to a separate PR which will help us keep features and PRs tightly coupled.

[brack2891]

@rushtong just so I am clear, you'd like a separate PR for deleting PaginatorBar.jsx. Adding that file back in this PR so that it is only captured in the future PR? Am I following that correctly?

[eweitz]

@rushtong, Austin has a question on how to proceed.

Please re-request review when this is ready for another round -- happy to take a look!

[rushtong]

@rushtong, Austin has a question on how to proceed.

Please re-request review when this is ready for another round -- happy to take a look!

Thanks for the reminder, I'll take another look.

[rushtong]

@rushtong just so I am clear, you'd like a separate PR for deleting PaginatorBar.jsx. Adding that file back in this PR so that it is only captured in the future PR? Am I following that correctly?

@brack2891 - Yes, exactly. In general, the PR should be focused on the required changes and that file deletion is essentially unrelated. By tying PRs to tickets, we can better track why something happened.

[fboulnois]

See below:

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
13.2% Duplication on New Code

See analysis details on SonarQube Cloud

[fboulnois]

👍

[rushtong]

We don't yet have an e2e github action so these tests are not run on PRs. When I run this locally, there are a number of failing tests. How did you get these to succeed?

[brack2891]

fixing tests

[rushtong]

I'm seeing some failures in this test as well when running locally.

[brack2891]

fixing failing tests

[rushtong]

This file isn't used by any other components so it is essentially untestable. Changes here should be reverted and the file removed in a separate cleanup PR.