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 unordered list of links to navigate from one tour step to the next doesn't create an accessible name for each link.
Expected Behavior
An interactive component (i.e. hyperlinks, buttons) should have a role and name, according to WCAG 4.1.2.
Accessibility expectations:
A screen reader user should be presented with the purpose of this "button". Example: "Step 1" or {{ title of step }}
A voice control user should be able to say the name of this component to activate it. (if they knew what the name was, although no visible label is available to them - )
Actual Behavior
The links have been given the role of button. But no name (description of what this component does) isn't present (nor accessible). Testing with VoiceOver on macOS alerted me that the accessible name is missing.
Errors and Screenshots (optional)
Visual of tour steps from a project under development:
Example rendered code in a project under development:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description
The unordered list of links to navigate from one tour step to the next doesn't create an accessible name for each link.
Expected Behavior
An interactive component (i.e. hyperlinks, buttons) should have a role and name, according to WCAG 4.1.2.
Accessibility expectations:
Actual Behavior
The links have been given the role of button. But no name (description of what this component does) isn't present (nor accessible). Testing with VoiceOver on macOS alerted me that the accessible name is missing.
Errors and Screenshots (optional)
Visual of tour steps from a project under development:

Example rendered code in a project under development:
Example (recommended)
The project I'm working on is currently under development.
However, this can be tested even on intro.js docs example page
Environment (optional)
The text was updated successfully, but these errors were encountered: