Closed carolabes closed 2 days ago
@carolabes We need to discuss this in our weekly.
There are 3 cases for the tabs
Moreover, we get the feeling that we are confusing the end user with multiple solutions
Hi @hirsch88, the technical implementation is important for people who cannot see the design. Based on the implementation, they can identify the element and know how to access it. By definition, the tab changes parts of the page (see tab role definition). Technically we have only one use case here.
This means:
I understand your point that it can be confusing for the users, but still the technical implementation should be correct for the users who don't see the design.
If there are any questions, please do not hesitate to contact me.
/cib
Branch fix/issue-1425 created!
Description of this issue
How to fix it
Additional Information
Level A https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html
Keyboard interaction: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/tab_role#keyboard_interaction
Code of Conduct