A collection of small personal tools and weekend builds. I use these to scratch a specific itch or test out an idea quickly, prioritizing functional utility over an over-engineered setup. You'll find a couple of exceptions here, like this portfolio, where the build is more deliberate and fully realized.
Creating tabs for your router is easy. Making them meet WAI-ARIA
accessibility standards is not.
Lots of tab libraries gave you accessible tabs. Connecting them to your
router, though, meant jumping through lots of hoops. React Routing Tabs gave you accessible tabs that connect to your router
with minimal effort.
Nowadays, modern frameworks and routers have simplified or eliminated the need for a library such as this. It is no longer actively maintained.
I designed and published react-routing-tabs as a standalone open-source package, including the accessibility model and the demo pages embedded on this site.
Challenges & Solutions
Most tab libraries assume the tab index lives in component state; wiring that same state through a router without breaking WAI-ARIA tab semantics (roving tabindex, aria-selected, arrow-key navigation) took more care than the tabs UI itself.
4.3.0Shipped a new internal refund platform, streamlining help desk process.
