Screen reader is announcing incorrect role as link for 'Previous' and 'Next' button in windows.

Test Environment:
OS: Windows 11[Version 24H2(OS Build 24631.3593)]
Edge: Version 135.0.2535.51 (Official build) (64-bit)
Chrome: Version 135.0.6422.112 (Official Build) (64-bit)
Screen readers: NVDA (2024.4.2)
Test URL: https://jqueryui.com/datepicker/

User Impact:
Visually challenged users who rely on screen readers are facing difficulty if Screen reader is announcing incorrect role as link for 'Previous' and 'Next' button in windows.

Pre-Requisite:

1. Turn on Screen Readers:
   NVDA: Ctrl + Alt + N
2. Verbosity:
   NVDA: Default

Repro Steps:

1. Launch the application using URL: https://jqueryui.com/datepicker/ in windows.
2. Date Picker screen will appear.
3. Press tab key to move to the date control and activate it.
4. Press tab key to move to the 'Previous' and 'Next' control.
5. Verify whether screen reader is announcing incorrect role as link for 'Previous' and 'Next' button in windows or not.

Actual Result:
Screen reader is announcing incorrect role as link for 'Previous' and 'Next' button in windows.
Screen reader announces: Link Next / Link Prev

Refer Attachment:
1.Screen reader is announcing incorrect role as link for 'Previous' and 'Next' button in windows..png
2.Screen reader is announcing incorrect role as link for 'Previous' and 'Next' button in windows..mp4

https://github.com/user-attachments/assets/3349a1f0-ae98-4d14-9e0b-348fab23aa98

Expected Result:
Screen reader should announce correct role as "Button" for 'Previous' and 'Next' button in windows.
Screen reader should announce: Button Next / Button Prev

Reproduce the issue on the jQuery UI datepicker demo at https://jqueryui.com/datepicker/ using Windows with NVDA, then inspect the datepicker implementation behind the Previous and Next controls. Verify the controls' accessibility roles in Edge or Chrome. Done means NVDA announces both controls as buttons rather than links.