I love seeing raw JS solutions like this. Too much we get lost in frameworks and it's a good reminder.
I believe the weakness of this solution is its inaccessibility. For example there are no tabs on the clickable rows. Additionally, screen readers will not register that the divs are serving as buttons.
Scrolling through the page, it doesn't look like a button either. (I guess this is why I went straight to adding a hover effect).
Tabbable == fixable at least.
But I guess back to my original point: I tent to prototype the big idea in pure JS. And then move it to a framework or rewrite it as a reusable component where I can continue to work through enhancements like accessibility.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I love seeing raw JS solutions like this. Too much we get lost in frameworks and it's a good reminder.
I believe the weakness of this solution is its inaccessibility. For example there are no tabs on the clickable rows. Additionally, screen readers will not register that the divs are serving as buttons.
True, but I'd also say:
Scrolling through the page, it doesn't look like a button either. (I guess this is why I went straight to adding a hover effect).
Tabbable == fixable at least.
But I guess back to my original point: I tent to prototype the big idea in pure JS. And then move it to a framework or rewrite it as a reusable component where I can continue to work through enhancements like accessibility.