3 ms·
We actually removed our CSS tabs recently because apparently modern screen readers had more issues with them than JavaScript tabs surprisingly enough.
by donatj 9y ago
We actually removed our CSS tabs recently because apparently modern screen readers had more issues with them than JavaScript tabs surprisingly enough.
- perilunar 8y agoNot really that surprising, since there is no way to apply the correct aria-selected and aria-expanded attributes using just CSS. (You can apply the correct ARIA roles in the HTML though, just not save the change of state.) It's a shame there is not a native HTML tab construction, since you really shouldn't need JS to make tabs. Using the radio buttons to set active state is a clever hack, but it's not what they were intended for. Ref: WAI-ARIA section on tabs: https://www.w3.org/TR/wai-aria-1.1/#tab https://www.w3.org/TR/wai-aria-1.1/#tab