accessible-html
accessible-html copied to clipboard
Require id and controls when setting up tabs and tabpanels
Fixes #28.
Thanks for the PRs! I'll take a look this week 🙏
@tesk9 Just added changes to attempt to autocorrect bad selected state input from users, in case you wondered what the pushes I just made were for. No more to come for this PR, just thought it could be a nice addition for review.
Oh, I see, so you would keep the Utilities like those for Aria but not the base elements?
Perhaps the package should be renamed if you do that though because accessible-html implies an accessible version of the html package in my view.
Either way, thanks for the heads up. Will you merge this and the other PRs before the next major release then before acting on such a decision?
@jamesrweb Yes I'll release a new major version with this code in it first!
Once #34 is merged, the conflicts with the latest master should be resolved.
I think I want to move this library toward just being attribute helpers after all, sorry! I highly encourage you to take the code you wrote and make a tab component package -- I think it'll be easier to manage as an isolated package than it would be as part of accessible-html and accessible-html-with-css.
Sorry again for the incredibly slow response here.