Describe the bug

The Step component has some accessibility problems:

1. When navigated with a screen reader, this will read each step two times: one for the li element and one for the a inside, adding links information such as visited and so on. The correct behaviour is the same one as the TabView component, so the aria tags and role should be switched between the a (role tab and all the aria tags) and the li (role presentation and no aria tags).
2. Currently the steps will never receive focus when navigating with keyboard only. You have to select an element with the mouse to apply focus and then the arrows navigation is available. The correct behaviour is the same one as the TabView component, so when tabbing in the Stepper the focus should go to the active step (the only one with tabindex=0), a consequent tab should leave the Stepper and go to the next focusable element on the page. Shift-tabbing back to the stepper should return focus to the active step.
3. Currently if you move focus with the arrows il will correctly change the tabindex of the focused element and remove it from the previously focused one. When tabbing out and back again, the focus should go to the active tab, not the last focused tab with arrows.
4. Disabled or readonly steps don't have aria-disabled as they should.
5. Disabled or readonly steps still have aria-current='step', that makes the screen reader read them as they were interactable. The aria tag should be present only when not disabled or readonly.

Also, since the Stepper has role tablist and each step role tab, they should also have aria-controls with the id of the controlled element, that in turn should have aria-labelledby. This is more complicated to handle, since the current implementation of the Step component doesn't have a concept of step content.
This could be solved by adding a new optional property to the MenuItem: overrideAriaControls or something like that, that delegates to the user the responsibility to correctly link the MenuItem to the actual id of the controlled element. While this would be simple to handle on the Step level, it would be more complicated for all the other components that use a MenuItem, as they should be updated to use this property when present instead of the automatically set one (eg: see TabView that already correctly implements aria-controls etc.)

I will open two different PRs, one for all the 5 points above and one to showcase the implementation of the aria-controls property in the MenuItems for the Step component only. If accepted, it should be ported to all other components too.

Environment

Windows

Reproducer

https://primeng.org/steps/

Angular version

16.X

PrimeNG version

16.3.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.13

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response