An element with tabindex="0" lacks a specific role attribute, making it a non-active element in the tab order. This disrupts keyboard navigation and violates WCAG 2.2 Success Criterion 4.1.2 (Name, Role, Value).
To Reproduce
Steps to reproduce the behavior:
Open the web application.
Navigate to the "Confirm exchange set content" page or "Selecting ENCs" page.
Use a web accessibility testing tool (e.g., ARC Toolkit).
Observe the error regarding an element with tabindex="0" lacking a specific role.
Expected behavior
Elements with tabindex="0" should have an appropriate role to ensure they are active and correctly part of the tab order.
Screenshots
Additional context
This issue affects interactive elements like anchor tags used for navigation, which have tabindex="0" but lack an appropriate role. Ensure these elements are correctly assigned roles to support accessibility and keyboard navigation.
Header needs tab index removed from title
File input doesn't look like a design system issue
Look at any other links with tab index = 0 and remove them
Describe the bug
An element with
tabindex="0"
lacks a specificrole
attribute, making it a non-active element in the tab order. This disrupts keyboard navigation and violates WCAG 2.2 Success Criterion 4.1.2 (Name, Role, Value).To Reproduce
Steps to reproduce the behavior:
Open the web application.
Navigate to the "Confirm exchange set content" page or "Selecting ENCs" page.
Use a web accessibility testing tool (e.g., ARC Toolkit).
Observe the error regarding an element with
tabindex="0"
lacking a specific role.Expected behavior
Elements with
tabindex="0"
should have an appropriaterole
to ensure they are active and correctly part of the tab order.Screenshots
Additional context
This issue affects interactive elements like anchor tags used for navigation, which have
tabindex="0"
but lack an appropriate role. Ensure these elements are correctly assigned roles to support accessibility and keyboard navigation.