Screen Reader Accessibility Regression: Missing Labels and Unread Buttons in v4.2.1

[LanieOkorodudu]

UV version:
v4.2.1

I'm submitting a:

• bug report => please fork one of these codesandbox examples with a repro of your issue and include a link to it below
• feature request => please use the user stories repo
• support request => Please do not submit support requests here, use stackoverflow

I performed a screen reader accessibility test comparing v4.0.0 and v4.2.1, and noticed several regressions in the latest version:

Observed Issues

1. Collapse Content button

• v4.0.0: Screen reader correctly announced this as “Collapse Content”.
• v4.2.1: Only announces “clickable” -- there is no accessible label.

2. Collapse Information button

• v4.0.0: Correctly announced as “Collapse Information”.
• v4.2.1: Also only reads “clickable” — label is missing.

3. Top panel navigations

• v4.0.0: The First Image and Previous Image buttons were detected and announced.
• v4.2.1: These buttons are skipped entirely by the screen reader — they are not announced at all.

Current behavior:

• Buttons are announced generically as “clickable” or skipped entirely.
• Labels that were present in v4.0.0 are now missing in v4.2.1.

Expected behavior:
The screen reader should announce:

• “Collapse Content” and “Collapse Information” for the respective buttons.
• “First Image” and “Previous Image” for the image navigation controls.

Other information:
See attached screenshot for reference

[demiankatz]

This was automatically closed when I merged #1534, though that PR only directly addresses the collapse control.

@LlGC-jop indicated that the other problem highlighted here (skipped buttons) is no longer occurring. Hopefully that means it's fine to close this, but would @LanieOkorodudu be willing to confirm that button accessibility fixes are confirmed, and open a new issue if there are still any problems?

[LanieOkorodudu]

Absolutely, you’re right that #1534 addresses the collapse control.

Regarding the first (previous) image, I still need to confirm whether it’s been fully addressed/announced correctly. I’m in the office today and don’t currently have permission to install NVDA on my work machine. I’m off tomorrow, so I’ll plan to test on Monday. If I find any issues, I’ll open a separate ticket.

For now, I’m happy for this one to be closed. Thanks, @demiankatz

[demiankatz]

Sounds like a plan; thanks, @LanieOkorodudu!