You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The step nav bar is not currently operable via keyboard because the step a tags to not have href attributes.
Steps to reproduce
Set the steps to be clickable, and then try to use the tab key to navigate through the page.
Expected behavior
I would expect the clickable step nav links to have href attributes so that it's keyboard operable, and to be able to set those href attributes. I would also expect the nav to just be a regular ol with some aria markup and not use semantic nav and link elements when the step progress indicator is not interactive.
Actual behavior
The links are clickable when the steps are set to clickable, but the links cannot receive keyboard focus. A step nav with no clickable elements is a semantic nav element with links despite not being interactive at all, which is potentially misleading to screen reader users.
(Edited because I mixed up animated and clickable.)
The text was updated successfully, but these errors were encountered:
Overview of the problem
Oruga version: 0.5.9
Vuejs version: 3.2.41
OS/Browser: Pop!_OS/Chrome
Description
The step nav bar is not currently operable via keyboard because the step
a
tags to not havehref
attributes.Steps to reproduce
Set the steps to be clickable, and then try to use the tab key to navigate through the page.
Expected behavior
I would expect the clickable step
nav
links to havehref
attributes so that it's keyboard operable, and to be able to set thosehref
attributes. I would also expect thenav
to just be a regularol
with some aria markup and not use semanticnav
and link elements when the step progress indicator is not interactive.Actual behavior
The links are clickable when the steps are set to clickable, but the links cannot receive keyboard focus. A step nav with no clickable elements is a semantic nav element with links despite not being interactive at all, which is potentially misleading to screen reader users.
(Edited because I mixed up animated and clickable.)
The text was updated successfully, but these errors were encountered: