Certain elements have roles that imply their internal structure should be hidden from accessibility tools, meaning their child elements are treated as purely presentational. However, if a sub-element within such a role receives keyboard focus, it should be moved outside of the presentation role or the role should be adjusted.
To Reproduce
Steps to reproduce the behavior:
Open the web application.
Navigate to the "Confirm exchange set content" Page.
Use a web accessibility testing tool ( siteimprove ) to identify the error.
Expected Behavior
Focusable elements should not be placed inside parent elements that have roles suggesting their content should be hidden or presentational. Instead, such elements should be moved outside of these roles, or the parent role should be revised to allow interactive content.
Screenshots
Additional Context
In the application, there are instances where elements with implied presentational roles contain focusable child elements. This mismatch between the role and the focusable state can cause navigational and accessibility issues.
KatiePUX
commented
2 weeks ago
Describe the Bug
Certain elements have roles that imply their internal structure should be hidden from accessibility tools, meaning their child elements are treated as purely presentational. However, if a sub-element within such a role receives keyboard focus, it should be moved outside of the presentation role or the role should be adjusted.
To Reproduce
Steps to reproduce the behavior:
Open the web application.
Navigate to the "Confirm exchange set content" Page.
Use a web accessibility testing tool ( siteimprove ) to identify the error.
Expected Behavior
Focusable elements should not be placed inside parent elements that have roles suggesting their content should be hidden or presentational. Instead, such elements should be moved outside of these roles, or the parent role should be revised to allow interactive content.
Screenshots
Additional Context
In the application, there are instances where elements with implied presentational roles contain focusable child elements. This mismatch between the role and the focusable state can cause navigational and accessibility issues.