Tabs: Missing accessibility features about cssui HOT 4 CLOSED

I created this PR to improve the accessibility without adding JS.

from cssui.

I was thinking to provide a separate package containing JS file for each component which provides accessibility improvements.

That could be an interesting solution. A sort of library's expanded version.

The point is: the scope of CSSUI is to provide CSS-only solutions. Introducing JS (even for accessibility) set the library as Bootstrap (or similar) competitor. Which is impossible.

I know, accessibility is a top priority for all. But we should make it different.

from cssui.

That's ok. I was thinking to provide it as an optional package, only if the developer wants to guarantee maximum accessibility. However, I'm thinking again about that. Working on the tabs component I realized that a fully accessible component would be created totally different compared to how we create it with CSS limitations.

For example, in the tabs component, we are forced to use the radio component to store the currently active tab. Instead of that, we should use a button. Providing a separate JavaScript package wouldn't solve these kinds of issues.

from cssui.

Resolved in 47b0e7b

from cssui.